Request: Native SegWit Support for 2of2 and 2of3 Multisig Wallets

[PeterMcBTC]

Hey there! I’d love to see native SegWit (Bech32) added to the 2of2 and 2of3 multisig wallets in Blockstream Green. Right now, they’re using legacy SegWit (P2SH), which is fine, but I think native SegWit could really step things up.

Why I think it’d be cool:

• Cheaper fees: Native addresses (the "bc1" ones) make transactions smaller, which can save up to 37% on fees. That’s a big deal for multisig stuff since those transactions tend to get chunky with all the signatures.
• Safer: Bech32 has a better checksum, so there’s less chance of messing up an address.
• Keeping up: Loads of wallets and services are already on board with native SegWit, so it’d be awesome if Blockstream Green joined the party.

My idea
Maybe make it an option? That way, people who like the old style can stick with it, and those of us who want native SegWit can switch over.

I reckon this could make the wallet even handier and more appealing for folks like me who want to save a bit and stay on top of security. Happy to chat more if you’re curious—thanks for checking this out!

[jgriffiths]

Hi @PeterMcBTC

We've held back on native segwit v0 rather than ps2h-wrapped multisig on the basis that taproot with musig2 provides us better benefits once its more widely adopted. In particular, its cheaper for our users in both the normal and recovery spending paths, and cannot be identified as a multisig so its better for privacy. Additionally, we could potentially allow alternate script paths for spending for some more exotic use-cases.

Taproot is currently a very small fraction of the current txs though, and so at this stage the privacy benefits can't really be realized (there aren't enough normal/singlesig p2tr txs for ours to blend in with). We are rolling out p2tr bip86 wallets for singlesig in the next app releases which should help improve adoption.

Its likely that we will look at taproot multisig towards Q3-Q4 this year - I am adding the remaining support that's required into our underlying libraries libwally and gdk. In the meantime though we are unlikely to implement native segwit v0 for multisig as this would just make recovery even more cumbersome for users with another set of address types to recover from.

[PeterMcBTC]

Thanks for the info, it was really interesting to read all that. Honestly, it’s got me excited to try out Taproot multisig with MuSig2 on Green when it’s released. I’ll keep an eye out for those Q3-Q4 updates! In the meantime, I’ll stick with what’s available. Cheers!