How to Set Up a 2-of-3 Multisig with One SeedSigner: The Stateless Quorum Guide
Multisignature (multisig) custody is widely regarded as the ultimate architecture for protecting significant Bitcoin holdings. By requiring two or more independent keys to authorize any transaction, you eliminate single points of failure like physical theft, coerced disclosure, or accidental destruction of a single backup.
Traditionally, setting up a 2-of-3 multisig wallet requires buying two or three distinct hardware signing devices, managing distinct firmware updates, and coordinating separate cables or micro-SD cards. But did you know you can coordinate and execute a full 2-of-3 multisig quorum using just one single SeedSigner device?
Because SeedSigner is completely stateless, it can hold multiple seed phrases loaded temporarily in its volatile memory, sign individual parts of a PSBT, and wipe everything clean the instant power is disconnected. In this comprehensive guide, we examine the security trade-offs, walk step by step through creating a 2-of-3 multisig wallet in Sparrow, register key descriptor files, and test spend transactions end to end.
1. Why Use One Device for Multisig? Exploring the Trade-Offs
In a classic multisig setup, security purists often recommend a multi-vendor architecture (for example: a Coldcard, a Blockstream Jade, and a Passport). The reasoning is simple: if one vendor pushes a malicious firmware update or suffers a zero-day exploit, only one of your signing keys is compromised, leaving your funds safe.
However, multi-vendor multisig introduces significant operational complexity:
- Vendor UX Friction: Learning different menus, key layouts, desktop suites, and export conventions across three vendors.
- Firmware Maintenance Overhead: Continuously tracking firmware integrity and updates across disparate manufacturers.
- Cost: Buying 3 dedicated high-end signing devices can easily cost upwards of $400 to $800.
With a DIY SeedSigner built from off-the-shelf electronics (Raspberry Pi Zero, camera module, Waveshare screen), you gain access to an alternative paradigm:
The Stateless Advantage
Because SeedSigner does not have an onboard hard drive or secure element that stores persistent seed words, it treats seed phrases as ephemeral data. You can scan in Seed #1, Seed #2, and Seed #3 via optical SeedQR cards, keep all three in memory during a session, sign, and wipe them by unplugging the USB power cable.
The Honest Trade-Off Analysis
| Factor | Benefits of Single SeedSigner Multisig | Risks / Potential Downsides |
|---|---|---|
| Device Redundancy | Only need 1 inexpensive device. If the device breaks, you can assemble or borrow another SeedSigner immediately. | You must trust the SeedSigner firmware code not to leak or compromise keys during scanning. |
| Physical Security | The 3 seed cards can be stored in different geographic locations or secure safe deposit boxes. | If you scan all 3 seeds into the device at the exact same time, a hypothetical zero-day exploit could access all keys in RAM simultaneously. |
| Convenience | Instant scanning with Compact SeedQRs; identical UX and fast signing workflow. | Requires strict offline discipline: scanning from optical paper or steel plates. |
Key Takeaway: If your threat model prioritizes geographic redundancy and protection against physical device theft, having a 2-of-3 multisig with 3 Compact SeedQRs stored in different places, while using a single SeedSigner to sign, provides exceptional resilience and usability. If you want to eliminate device-level monoculture, you can still mix SeedSigner into a multi-vendor quorum.
2. Prerequisites for the Setup
Before starting, make sure you have the following ready:
- Assembled SeedSigner: Running the latest official SeedSigner firmware release.
- Three Seed Phrases (Compact SeedQRs): Inscribed or printed on paper or steel. You can create these offline using SeedSigner's dice-roll entropy and transcribe them onto standard or Compact SeedQR grids.
- Master Key Fingerprints Noted: Write down the 8-character master key fingerprint for each seed on its card to verify scans.
- Sparrow Wallet: Installed on your desktop computer, ideally connected to your own Bitcoin full node or an Electrum server.
- Computer Webcam: Required for Sparrow to scan animated QR codes displayed on the SeedSigner screen.
Reference Guides: If you have not created your SeedSigner or inscribed your Compact SeedQRs yet, check out our companion deep-dives: SeedSigner Build & Beginner's Guide and How to Make a SeedQR & Compact QR.
3. Step-by-Step: Building the 2-of-3 Quorum in Sparrow
Step 1: Scan All 3 Seeds into SeedSigner
Power up your SeedSigner via USB power. From the main menu:
- Navigate directly to Scan and click the directional stick/enter button.
- Present your first Compact SeedQR card to the camera. The SeedSigner will instantly decode it and display the master fingerprint (e.g.,
D8D...). - Confirm the fingerprint matches the one written on your card, then press Done.
- Repeat the scan process for Seed #2 and Seed #3.
- Navigate to Seeds on the main menu: all three seeds will be visible and listed cleanly by their unique fingerprints.
Step 2: Create a New Multisig Wallet in Sparrow
Open Sparrow Wallet on your computer:
- Go to File → New Wallet and enter a wallet name (e.g., "SeedSigner Multisig 2of3").
- Under Policy Type, change the dropdown from Single Signature to Multi-Signature HD.
- Keep Quorum set to
2 of 3. - Select Native Segwit (P2WSH), which uses modern
bc1q...addresses with low transaction fees and standard derivation pathm/48'/0'/0'/2'.
Step 3: Export the XPUBs from SeedSigner to Sparrow
Now import each key store into Sparrow:
-
Export Key 1: On SeedSigner, go to Seeds → Select Seed 1 → Export XPUB. Choose Multisig → Native Segwit → Animated (Default). SeedSigner will show an animated QR code containing your extended public key (
Zpub) and fingerprint. - Import into Sparrow: Under Keystore 1 in Sparrow, select Airgapped Hardware Wallet → SeedSigner → Scan. Hold your SeedSigner up to your computer webcam. Sparrow will immediately register the XPUB and label it Keystore 1.
- Export Key 2: Repeat on SeedSigner for Seed 2. Export XPUB as Multisig Native Segwit Animated QR, and scan it into Keystore 2 in Sparrow.
- Export Key 3: Repeat for Seed 3, scanning the animated XPUB into Keystore 3 in Sparrow.
Step 4: Finalize and Apply Wallet Settings
Review the fingerprints in Sparrow against the physical cards. Click Apply on the bottom right. You can choose to protect the wallet configuration file with a password. Sparrow will save your wallet file and display the complete multisig descriptor.
4. The Critical Role of Output Descriptors & Backups
In a single-signature wallet, having your 12 or 24-word seed phrase is sufficient to recover your funds anywhere. In multisig, your seed phrases alone are NOT enough!
To recreate a multisig wallet, you must know:
- All public keys (XPUBs) of all participants in the quorum.
- The derivation paths used by each key.
- The threshold policy (e.g., 2-of-3).
- The specific lexicographical ordering of keys (BIP67).
This complete blueprint is called the Output Descriptor. If you lose one seed phrase in a 2-of-3, you can recover using the remaining 2 seed phrases only if you have this descriptor. If you lose the descriptor and only hold 2 of the 3 seed phrases, your Bitcoin is permanently locked because you cannot derive the coordinated multisig addresses.
Backing Up the Descriptor PDF
When Sparrow creates the wallet, it prompts you to save the wallet configuration as a PDF backup. This PDF contains:
- All 3 XPUBs, fingerprints, and derivation paths.
- A high-density QR code encoding the exact descriptor text.
Best Practice: Print multiple physical copies of this descriptor sheet. Store them in encrypted vaults (e.g., Cryptomator, password managers, self-hosted Vaultwarden on Start9 or Umbrel), on secure USB drives, and alongside your seed phrase backups. The descriptor contains public keys, not private keys, so while it compromises privacy if leaked, an attacker cannot steal funds with the descriptor alone.
5. Registering the Multisig Descriptor with SeedSigner
Why does SeedSigner need your descriptor? When you send Bitcoin from a multisig wallet, any unspent change is sent back to a newly generated change address belonging to your wallet.
A stateless signer needs to confirm that this change address actually belongs to the 2-of-3 quorum, rather than a malicious address substituted by malware on your computer.
How to Register the Descriptor:
- In Sparrow, go to Settings → Export (bottom left).
- Scroll down to Spectre Desktop format and click Show. This renders the wallet descriptor as a QR code on your monitor.
- On SeedSigner, select Scan from the main menu and point the camera at your computer screen.
- SeedSigner parses the descriptor, displaying
Policy: 2 of 3and listing all 3 signing key fingerprints. - Click OK. SeedSigner now knows that any change addresses derived from this descriptor belong to your legitimate wallet!
6. Live Test Transaction: Spending from a 2-of-3 Multisig
Always fund a new multisig setup with a small test deposit first (e.g., 15,000 sats) and execute an end-to-end outbound test spend before committing your primary stack.
Signing with Key 1 and Key 3
- Construct Spend in Sparrow: In Sparrow's Send tab, enter an external recipient address, set the spend amount (e.g., 10,000 sats, leaving ~5,000 sats for change and fees), and click Create Transaction → Finalize Transaction for Signing.
- Show PSBT QR: Click Show QR in Sparrow. This displays the Partially Signed Bitcoin Transaction as an animated QR.
- Scan on SeedSigner: On SeedSigner, click Scan and point at Sparrow. Once decoded to 100%, SeedSigner prompts: Select Signer.
- Apply First Signature (Key 1): Select Keystore 1. Review the destination address, amount (10,000 sats), and change address. Approve the transaction. SeedSigner displays the signed PSBT QR.
- Import Signature to Sparrow: In Sparrow, click Scan QR and hold SeedSigner up to your webcam. Keystore 1 will show a green checkmark as signed.
- Apply Second Signature (Key 3): Display the QR code again in Sparrow. On SeedSigner, scan the PSBT again, select Key 3, review transaction details, and approve. Scan SeedSigner's QR back into Sparrow.
- Broadcast: Sparrow confirms both Key 1 and Key 3 have signed. The Broadcast Transaction button turns blue. Click Broadcast, and your transaction enters the mempool!
7. The Ultimate Stateless Test: Powering Off and Sweeping
To prove true stateless security and ensure you are never stranded in the real world:
- Unplug the SeedSigner: Remove power completely. All keys in volatile memory are immediately wiped.
- Reboot and Verify: Plug power back in. Check the Seeds menu: it will be 100% empty.
- Scan Only 2 Seeds: In a real disaster or remote scenario, you might only have physical access to two of your three seed cards. Scan in Seed 1 and Seed 2 only. Leave Seed 3 in its secure location.
- Spend Full Balance (Sweeping): In Sparrow, draft a transaction using Send Max. Notice that because there is no change output, SeedSigner explicitly warns you with a full-spend caution notice.
- Sign and Broadcast: Sign with Key 1, then sign with Key 2. Sparrow registers both signatures and broadcasts successfully. All sats are moved, proving that any combination of 2 keys can execute a full recovery without ever storing data on the device.
Key Takeaways for Your Multisig Journey
- ✓ One device can execute multisig: SeedSigner's stateless architecture allows you to sign multi-key quorums without buying multiple hardware units.
- ✓ Descriptor backups are mandatory: Always print and securely archive the Sparrow output descriptor PDF alongside your seed phrases.
- ✓ Verify change addresses: Load the Spectre descriptor QR into SeedSigner when transacting with return change outputs to guarantee peace of mind.
- ✓ Test before funding: Always perform live receive, partial spend, and full sweep tests before migrating significant Bitcoin.
Need Guidance Architecting Your Multisig Setup?
Setting up multisignature self-custody is one of the highest leverage steps you can take for your Bitcoin security, but eliminating setup mistakes is critical. Book a 1-on-1 private coaching session to audit your architecture, verify descriptors, and practice dry runs safely.
Book a 1:1 Coaching SessionWatch the Full Video Walkthrough
Follow along step-by-step with Forrest HODL as he scans three Compact SeedQRs, configures Sparrow Wallet, registers descriptors, and executes live transactions.