There exists an RPC endpoint call (see Alpha Romeo code) for retrieving peg-ins/peg-outs on the next branch of the stacks-network/stacks-blockchain repo. We should port the sBTC ops work from next into develop, making sure that the dtaa is ONLY stored. They must not be treated as being officially part of the Bitcoin block snapshot, lest their presence influence the calculation of the ConsensusHash for that block (which itself is consensus-critical). I.e do not port consensus breaking changes.
There exists an RPC endpoint call (see Alpha Romeo code) for retrieving peg-ins/peg-outs on the
next
branch of the stacks-network/stacks-blockchain repo. We should port the sBTC ops work fromnext
intodevelop
, making sure that the dtaa is ONLY stored. They must not be treated as being officially part of the Bitcoin block snapshot, lest their presence influence the calculation of the ConsensusHash for that block (which itself is consensus-critical). I.e do not port consensus breaking changes.This endpoint will be temporarily used while waiting for https://github.com/stacks-network/stacks-blockchain/issues/3958 to be done.