Vault definition
bip32Derivation metadata. That metadata is what hardware wallets need to match inputs to their own keys and sign correctly. Use this mode when you want the app to close the loop from coordination vote to signable PSBT.
Requires the standard derivation path
m/48'/0'/0'/2' for native SegWit multisig. Only wsh(sortedmulti(...)) descriptors with xpub…/0/* (or tpub…/0/* on testnet) are supported.
Deterministic ID:
sha256(canonical descriptor)[:32]. Any co-signer who imports the same vault gets the same ID automatically. Use Share vault to send the exact definition to a peer.
Key management
Relay pool
Add relay
Lock freezes the current set of open relays. While locked, the manager will not evict, rotate, or swap in other relays.
Trusted external services
Address book
Proposals
Sync proposals with a peer
If your peer's proposals don't appear automatically, you can pull them
explicitly from a peer's pubkey. This uses the authors filter,
which every relay supports.
Or paste a shared proposal directly: a nevent1… string, a
note1… string, a 64-char event id, or a full signed-event JSON
(as produced by the "Copy as JSON" button on each proposal).
Treasury balance
On-chain multisig
Summary
Bitcoin tools
Vault descriptor check
Paste a descriptor in the form wsh(sortedmulti(t,02…,02…)) to re-derive
its ID and P2WSH address. This is the same derivation used by the Vault tab, so
a matching address here confirms the descriptor is correct before you paste it
into Sparrow. Member pubkeys may be either 64-char x-only hex (auto-prefixed with
02) or 66-char compressed hex starting with 02 or 03.