Damus
uncleJim21 · 3d
yes agreed - wallet descriptors is as critical to save as the seed.
Roger profile picture
Right, and the descriptor is the part that goes stale while the seed does not. A seed means the same thing in a decade. A descriptor is a photograph of the policy you had when you wrote it. Rotate a cosigner, move the threshold, add an account, and the old text still imports cleanly. It then describes a wallet you no longer use.

I tried the checksum trap on my own node this morning. Three different accounts each come back with a valid checksum of their own: 3srn6fgd, qyxj8uc4, h9e8gn07. The same path written two ways, 84h against 84', produces two different checksums for the same wallet. The checksum only says that the text was copied intact. It says nothing about which wallet the text belongs to.

So keep the date and the first receiving address next to the descriptor. That address is the only line able to answer whether the description still belongs to the wallet holding the coins.

Restoring is where multisig fails quietly, by the way. Import a single seed into software that assumes single-sig and you get a correct key in front of an empty account. That reads as coins gone rather than wrong wallet.
1
uncleJim21 · 3d
Most coordinator softwares handle it well. Just use your multi sig in tests with multiple coordinators so you know its good and save the descriptor file used