The setup guide gives you a safe 2-of-3 with the fewest moving parts. These are the next steps people ask about. None of them are required, and each adds work.
Run your own node
In the basic setup, Sparrow asks a public server about your addresses. That server can see your whole balance and your IP address. It can’t steal anything, but it knows more than it needs to.
Running Bitcoin Core yourself fixes that: Sparrow asks your own node and nobody else learns anything. A pruned node, which throws away old blocks after checking them, needs about 20 GB of disk space and fits on an old laptop or a small home server. The first sync takes a day or more.
The article on running your own node for Sparrow walks through it, and the Sparrow documentation explains how to connect Sparrow to Bitcoin Core.
Connect over Tor
Tor hides your IP address from the server Sparrow talks to. Sparrow has Tor built in, and it can also use the Tor Browser as a proxy. On some networks Tor won’t connect at all; mine was one of them. If yours works, it’s a cheap privacy win.
A second vault from the same devices
You can keep two separate multisig wallets, for example business and personal, on the same three devices. The second one uses account 1 instead of 0 in the derivation path (m/48'/0'/1'/2'). Build and test one vault completely before you start the other. The details are in step 6.
3-of-5 and other quorums
A 3-of-5 survives the loss of two keys instead of one. It also means five seeds in five places, and in practice most losses come from people misplacing backups, not from devices failing. For most people 2-of-3 is the better balance. If the amount grows to the point where 3-of-5 feels right, you build a new vault and move the coins over.
A watch-only copy
To see your balance without unpacking the signing laptop, load your descriptor into a second Sparrow or Nunchuk as a watch-only wallet. It can’t sign anything, but anyone who opens it sees your whole balance, so treat it like a bank statement.
Timelocked inheritance
Liana adds a recovery key that only works after your coins have sat unmoved for a set time, so an heir needs one key instead of two. It needs regular refreshes and doesn’t work with the Trezor. See timelocked inheritance with Liana and, for the plain approach, inheritance with multisig.
Going deeper
- Wallet registration explained: why some devices check addresses against your setup and others don’t.
- P2SH vs P2WSH vs P2TR and taproot and MuSig2: the address types, and why the guide stays on P2WSH.
- Multisig with your partner or family: who holds which key.
- Multisig and the $5 wrench attack: what spreading keys does against physical threats.