sBTC Research - Create Deposit Procedure Diagram

[AshtonStephens]

Description

We need to create a deposit procedure diagrams to put in place of Figure 1 of the original sBTC SIP PR.

Context

During the SIP planning process we've identified a few key changes that we intend to make for the original deposit flow. The primary difference are:

1. OP_RETURN will be supported but not the primary deposit protocol
2. OP_DROPs will be collated into a single OP_RETURN along with any other UTXOs to the peg wallet such that at the end of every Bitcoin block there is only a single UTXO to the peg wallet.
3. A user using OP_DROP will provide the revealer data via a Revealer API in the happy path, and "challenge" or "force" the transaction to be noticed by signers via a call to the .sbtc contract.

All research discussions: research
All design discussions: design

Most relevant:

• feat: support contract principals in complete-deposit contract calls stacks-network/sbtc#345
• feat: adds costs test for completing withdrawals stacks-network/sbtc#314
• feat: transaction coordinator capable of computing and signing a valid bitcoin transaction stacks-network/sbtc#343

Expected Approach

Create one or more protocol flow diagram like the others in the SIP that will show the full flow of OP_DROP and OP_RETURN and include that in the SIP. It is expected that these are iterated upon within this ticket.

• Read relevant sBTC research discussions
• Discuss areas of ambiguity
• Create protocol diagram/s
• Iterate

Artifacts / Acceptance Criteria

• There are N protocol design diagrams that handle all variations of the 3 steps in the context description.
• Those diagrams have been confirmed by Jude and others.
• Those protocol design diagrams are linked to and included in the sBTC SIP in the initial sBTC SIP PR: SIP: Nakamoto sBTC stacksgov/sips#156

[FriendsFerdinand]

I think the steps are going to look like this for Commit-Reveal (largely unchanged compared to stacks-network/sbtc#345 (comment)):

And in the case of a Challenge, we'll have the following:

In both cases, the curve arithmetic is done by the Stacks Node and not in the Clarity contract