SIP-03X: BTC addresses for Stacks transactions #219

[larry]

I made a prototype wallet app that allows you to use sBTC with native segwit bitcoin addresses instead of Stacks addresses. I posted a video demonstrating its usage on X:

https://x.com/larrysalibra/status/1895787738877841638 (or alternatively on youtube)

Source code is available on github
You can try out the app here (desktop chrome with xverse or leather extensions only): https://sbtc-with-btc-addresses.vercel.app/

@yukan

I think this would require some changes to the Clarity side of things. The principal type will need to support Bitcoin addresses as well. Maybe one of the core devs can chime in on this.

One way to approach this in the short term is to make stacks addresses an implementation detail. Show users native segwit bitcoin addresses and convert them to stacks addresses “under the hood” when making layer 2 transactions.

@marvin.id

If I send someone sBTC and it does not show up in their pure Bitcoin wallet app, all they would need to do is connect their hardware device to an “sBTC-aware” wallet app.

Exactly. The world we want to end up in is that every bitcoin wallet checks addresses in its wallet for assets on both layer 1 and layer 2.

@raphasierra.id.block

This removes friction, “merges” ecosystems, and potentially equips Bitcoin addresses with BNS?

Yes! The bitcoin ecosystem is one of layers.

@Resh

I personally really like this idea very much, but what happens to Stacks in that case? Can the asset be used for gas fees? Or only sBTC be used?

There’s a more detailed thread about this. Personally I think fees will need to be paid in sBTC to make the user experience ideal. There are a number of ways to do this. One way is to transparently convert the sBTC to STX “under the hood” in some form seems to be the way to do it.