If you have your multisig wallet set up in Sparrow you can export it in Sparrow's own format. It generates '.mv.db' file, it contains everything you need. You can test this with an empty test wallet.
You could save additional info to be more compatible with other wallets but why would you do that if Sparrow is free and open source?
You can backup Sparrow code and executable too if you want but since so many ppl use it there is a vanishingly low chance that you won't have access to a Sparrow version to use that backup.
Labels are precious too, and bare descriptor doesn't save that. It will also save gap limit I _think_ which helps Sparrow find your coins easier if you have many utxo-s.
Also, you are accustomed to Sparrow most probably. Using a different wallet is more risk, more things to verify etc. Stick with what has worked. So even though compatibility looks good on first look and experiments can be useful from time to time but you know...
Some time ago I made [this](https://v.nostr.build/GeeXk.mp4) video about multisig, check it out hope it helps.
When attempting to open the sparrow export file my computer opens DB Browser for SQLite and prompts for a passphrase.
I entered the password that I created for the wallet in sparrow and it fails to open.
Is that because I’m opening the file in general from my desktop and not in sparrow specifically? Will the file not open unless done so via sparrow?
Yes, you need to open with sparrow. It is its own format and will use your wallet encryption password.
You wouldn't use that file without sparrow wallet either way.
While you could in theory just manually decrypt(knowing the crypto algo from sparrow open-source code) and inspect the raw db file, you would never need to do that.
Save your wallet encryption psw in a safe place therefore too.
That’s what I figured.
Thanks again, truly.
Thread collapsed
Thread collapsed
Thread collapsed
