More context from the ๐Ÿ
thepurpose's avatar thepurpose
๐Ÿšจ Observing a lot of oversimplification around multisig lately. ๐Ÿšจ People confidently explaining setups they've clearly never actually configured _or_ recovered from. If you've never done a dry-run recovery of your multisig, you haven't tested your backup. Seeds, xpubs, descriptor, derivation paths, key ordering. Add all that to your backup _and test it_ or stay single-sig. So that's it: multisig isn't hard to understand, it's hard to execute. More moving parts mean more ways your backup fails when you need it.
View quoted note →

Replies (2)

A nuance is that there is no need to store the public keys secretly like the private keys; for example the public keys (xpub, descriptor) can be shared among the participants, so each signer has its own secret private key and the descriptor that contains _all_ public keys.
โ†‘