API support for sBTC

[zone117x]

Initial issue to track sBTC work related to the API. By default, sBTC will have have some support due to it being defined as an ft contract. We likely will be defining additional requirements as sBTC progress on the blockchain matures.

• [ ] Ingest and expose sBTC peg-in transactions
• [ ] Ingest and expose sBTC peg-out transactions
• [ ] Integration with the sBTC contract (first-class support as if it was a boot-contract)
• [ ] Open feature requests / blockers in the blockchain repo to support integration (likely requests for requisite event-emitter data / contract-logs).

This issue will wait until clarinet has support for interacting with sBTC: https://github.com/hirosystems/clarinet/issues/1083, which will indicate a level of readiness on the Nakamoto side.

[igorsyl]

Trying to add to the sBTC project board. @saralab @diwakergupta can you grant me contributor access?

[saralab]

You should have access now @igorsyl

[netrome]

For context: This is the RPC endpoint we have added in the next branch to get sBTC ops: https://github.com/stacks-network/stacks-blockchain/pull/3511

[zone117x]

For context: This is the RPC endpoint we have added in the next branch to get sBTC ops: stacks-network/stacks-blockchain#3511

Note that Hiro API does not use RPC endpoints. The burnchain op data needs to be added to the event-emitter payload. The issue tracking that work is here: https://github.com/stacks-network/stacks-blockchain/issues/3554

[netrome]

@zone117x it turns out the burnchain op data has already been added to the event-emitter payload. Let me know if you encounter any issues with the format. This issue is closed now https://github.com/stacks-network/stacks-blockchain/issues/3554

[zone117x]

Blocked on sBTC progress