{"type":"rich","version":"1.0","author_name":"ShiShi21m (npub1ug…r898l)","author_url":"https://nostr.ae/npub1ugnq57hn8va6xqr5zywy2eunem6c624583vkt0dmv40ep7tnnxkqrr898l","provider_name":"njump","provider_url":"https://nostr.ae","html":"Imagine you have 3 safes in 3 different locations.\n\nIn this example it's a safe at home and two separate safety deposit boxes.\n\nSafe Box 1, 2, 3 respectively.\n\nIn a 2of3, with a backup for each seed (6 seeds total) spread across all 3 if one box gets corrupted you lose your monies.\n\nIf you abstract the descriptor file away from those safes and keep it in an encrypted cloud or in a 4th box, that adds complexity and potential downside if your heirs need to recover.\n\nIn a 3of3, with backups for each - 6 seeds again.\n\nIf you spread them correctly:\n\nBox 1 -\u003e Seed A \u0026 B\n\nBox 2 -\u003e Seed B \u0026 C\n\nBox 3 -\u003e Seed A \u0026 C\n\nIf any one safe box gets corrupted you can still access your bitcoins, your descriptor file isn't as important if you use standard multisig settings which all the major wallets ascribe to (you should still have the descriptor /config backed up with each seed though)\n\nYou know you have done it correctly if you look at the descriptor file \u0026 each signer / seed shows a derivation path of: m/48'/0'/0'/2\n\nThat's how you know you have the standard settings for your multisig and can recover in the future with no descriptor/config file and also HWW agnostic. \n\nYour heirs will thank you and your security model will be bulletproof.  \n\n"}