sBTC Research - Callback on Deposit to Principle

[AshtonStephens]

This is a research discussion post meant to be edited with research notes. This research surrounds initiating a clarity contract when a certain principle receives sBTC or stacks.

This may not be relevant to sBTC but it would be good to do some preliminary research.

[AshtonStephens]

Currently under investigation by @radicleart

[friedger]

Transferring tokens into a contract is (currently) not recommended. Usually, depositing happens through a defined trait.
However, sbtc as of now does not provide anything to specify a trait.

Specifying a trait would cost more on the bitcoin side when making the request.

Could there be a default trait? What happens if the contract call fails? Would it be one mint tx and one callback tx? Who covers the tx fees for the second call?

Alternatively, is it possible to lookup the deposit/mint details in the sbtc contract?

[mijoco-btc]

there will always be an event generated by successful mint so maybe its safer to let the contract team listen for events and call contract more decoupled and no risk of the mint failing because of the third party contract.

…

On Tue, 24 Oct 2023 at 07:25, Friedger ***@***.***> wrote: Transferring tokens into a contract is (currently) not recommended. Usually, depositing happens through a defined trait. However, sbtc as of now does not provide anything to specify a trait. Specifying a trait would cost more on the bitcoin side when making the request. Could there be a default trait? What happens if the contract call fails? Would it be one mint tx and one callback tx? Who covers the tx fees for the second call? Alternatively, is it possible to lookup the deposit/mint details in the sbtc contract? — Reply to this email directly, view it on GitHub <https://github.com/stacks-network/sbtc/discussions/313#discussioncomment-7366055>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABBORIJBHAQZDYRJ5RZZXCTYA5NOHAVCNFSM6AAAAAA6MK5ZOWVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TGNRWGA2TK> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[AshtonStephens]

In conclusion, we've decided that this feature should be implemented eventually, but isn't going to be part of the sBTC release.