In this follow-up to my first Casa video, I show how to take a Casa multi-signature Bitcoin wallet and rebuild it outside the Casa app. This is not just a technical exercise. It gives you a practical way to verify addresses independently, understand what would happen if Casa disappeared, and practice the sovereign recovery process without putting your funds at risk.
Why recreate a Casa wallet?
Casa is an excellent starting point for multi-sig, especially if you are new to it. The main reason I want to show this process is that Casa’s multi-sig setup can be recreated using common open-source Bitcoin wallet software. That matters for three reasons:
- Address verification. You do not have to rely only on the Casa app to confirm a receive address.
- Sovereign recovery practice. If Casa were unavailable, you would still need to know how to operate your keys and sign transactions.
- DIY multi-sig preparation. Understanding how the wallet is built helps if you later want to create your own multi-sig setup from scratch.
The goal is simple: use your own tools to confirm that Casa’s wallet behaves exactly as it should, and make sure you can still move funds even if access to the Casa platform becomes restricted.
Create a watch-only wallet in Electrum
The first step is to create a watch-only copy of the Casa multi-sig wallet in Electrum. This is useful because it lets you verify receive addresses without needing any private material from the Casa app.

In the video, I follow Casa’s documentation for creating a watch-only wallet in Electrum. The key idea is that instead of entering seeds, you enter master public keys, or xpubs, for each co-signer.
Steps to build the watch-only wallet
- Open Electrum and start a new multi-signature wallet.
- Set the wallet as 3 of 5, matching your Casa configuration.
- For each co-signer, choose the option to use an existing master key or xpub rather than creating a new seed.
- Enter the public key information for each signer: – Mobile key – Recovery key – Office key – Safe key – Any additional hardware keys in your Casa setup
- Complete the wizard and let Electrum synchronize.
Once that is done, you have a watch-only wallet that can display the same addresses as Casa. You can use it to double-check receive addresses before sending funds into the account.
This alone improves security. If someone were to tamper with your phone or compromise part of the Casa app experience, having a second independent wallet showing the correct address gives you another layer of protection.
Rebuild the full working wallet in Sparrow
A watch-only wallet is useful, but it cannot sign transactions by itself. For that, I rebuild the same Casa 3-of-5 wallet in Sparrow. Sparrow is a good fit here because it works well with PSBT files and supports many hardware wallets.

The important part is to match Casa’s script type and signer count exactly. In this example, the wallet is:
- Multi-signature
- Nested Segwit, also called P2SH-P2WSH
- 3 of 5 signers
Steps to recreate the wallet in Sparrow
- Open Sparrow and create a new wallet.
- Name it something clear, such as
Casa-3of5. - Choose multi-signature.
- Select Nested Segwit / P2SH-P2WSH.
- Set the policy to 3 of 5.
- Add each keystore one by one: – Mobile key – Recovery key – Office key, such as a Trezor – Safe key, such as a Coldcard or Keystone – Any remaining keys in your Casa setup
As you add each signer, you need the correct:
- Derivation path
- Master fingerprint
- Extended public key, or xpub
For some signers, this information is available directly from the Casa app. For others, especially hardware wallets like Coldcard and Keystone, it may take a little more work because Casa uses non-standard derivation paths for multi-sig.
Finding xpubs for Coldcard and Keystone
This is where things can get confusing if you are not used to multi-sig metadata. Casa does not always use the same derivation path that a hardware wallet would normally show in its standard multi-sig export. That means you may need to derive the correct account-level xpub manually.
In the video, I show two approaches:
- Use the public key information shown in the Casa app or recovery documents.
- Use an exported master public key with Ian Coleman’s BIP39 tool to derive the correct xpub for the Casa path.

The second method is useful when you do not have easy access to the Casa app, but you still have your hardware device or an exported public key file.
How to derive the correct xpub
- Take the master extended public key from your Keystone or Coldcard export.
- Paste it into the BIP32 root key field in Ian Coleman’s BIP39 tool.
- Open the derivation section.
- Enter the Casa multi-sig derivation path shown in your recovery information. In this example, the relevant path is
m/49/0'/2'. - Select the script type that matches nested Segwit / P2SH-P2WSH.
- Copy the resulting account-level xpub into Sparrow.
You should then compare the result with what Casa shows for that signer. If everything was entered correctly, the derived xpub will match.
This is a very useful skill to know. It helps you understand that a multi-sig wallet is not just “the app” or “the device.” It is a set of public keys, fingerprints, derivation paths, and script rules that can be reconstructed outside any single product.
Sign transactions from the recovered Sparrow wallet
Once the wallet is rebuilt in Sparrow, you can use it to create and sign transactions independently of Casa’s app. This is where the real security benefit shows up: if you hold a quorum of your keys, you should still be able to spend even if Casa’s platform is unavailable or access has been revoked.
In the demo, I send a transaction using Sparrow and sign it with hardware wallets connected through QR codes or USB. The point is not the specific devices themselves, but that the same multi-sig policy can be operated from your own software.

Steps to sign a transaction from the recreated wallet
- Open the rebuilt Casa wallet in Sparrow.
- Create a send transaction.
- Export or display the unsigned PSBT for signing.
- Sign with one hardware device, such as Keystone.
- Combine that signature back into Sparrow.
- Sign with a second device, such as Trezor.
- Sign with a third device to complete the required quorum.
- Broadcast the transaction.
In the video, I also show signing with a KeepKey even though it is not one of the devices originally shown in the Casa setup. This works because the underlying keys and multi-sig policy are what matter, not the specific brand of hardware wallet used to hold them.
After broadcasting, the transaction appears in both Sparrow and the Casa app. That confirms the recreated wallet is tracking the same account state.
Get missing fingerprints from an unsigned PSBT
There is one detail that can trip you up: some signer metadata may not be fully available inside the Casa app. In particular, the recovery key fingerprint was left as zeros in my Sparrow setup at first because it was not directly visible there.
That becomes a problem if you want to import the wallet into Coldcard or otherwise verify that every signer is correctly identified. The good news is that Casa’s unsigned PSBT files contain enough information to recover those missing fingerprints.

Steps to recover the missing fingerprint
- Download an unsigned PSBT file for a Coldcard or Keystone from Casa.
- Open that PSBT in Sparrow.
- Inspect the input details, especially the witness script for the multi-sig output.
- Look at the public key entries and their associated fingerprints.
- Match each fingerprint to the corresponding keystore in your recreated wallet.
- Enter any missing fingerprint into the correct keystore settings.
- Apply the changes and let Sparrow resynchronize.
This is a small step, but it matters. If the fingerprints are wrong or incomplete, hardware wallets may reject the transaction or fail to recognize the account correctly.
Save the multi-sig wallet to Keystone and Coldcard
After the wallet is fully reconstructed in Sparrow, you can export it so that hardware devices like Keystone and Coldcard can store it locally. This lets you verify receive addresses directly on the device screen instead of trusting a phone or desktop app alone.

This is especially valuable for Coldcard because it can be used to verify addresses without putting the device into a less secure “trust PSBT” mode. If you are receiving a large amount of Bitcoin, verifying the address on more than one independent tool is worth doing.
Steps to save the wallet to hardware devices
- Export the multi-sig wallet from Sparrow in a format suitable for your device.
- On Keystone, import the multi-sig wallet using its QR or file import process.
- On Coldcard, import the wallet onto the microSD card and then load it into the device.
- Open the address explorer on the hardware wallet.
- Compare the receive address shown on the device with the address in Casa and Sparrow.
If all three match, you have a much stronger assurance that you are sending funds to the correct place.
Coldcard import issues and how to fix them safely
This is the part I would pay the most attention to if you are using Coldcard with Casa. There are two quirks worth understanding.
Issue 1: Direct PSBT imports can create a legacy script type
If you import a Casa PSBT directly into Coldcard, the device may interpret it as a legacy account type rather than the nested Segwit type used by Casa. That creates a completely different set of addresses.

If that happens, do not panic. The fix is usually straightforward: recreate the wallet in Sparrow using the matching legacy script type and confirm that the addresses line up with what Coldcard generated from the PSBT import. That tells you exactly which address set was being used by mistake.
Issue 2: Casa’s recovery key path may differ from expectations
There is also a mismatch between how Casa presents some recovery information and how it appears in unsigned transactions. In particular, the derivation path for the recovery key inside Casa PSBTs can be different from what you might expect after a key rotation.
This matters because if you import the wallet into Coldcard based only on standard assumptions, Coldcard may not recognize the transaction unless you use trust PSBT mode. Trust PSBT is less secure because it reduces the device’s ability to verify that the transaction belongs to the intended account.
The safer path is to correct the imported file so Coldcard has the right script format and signer metadata. In practical terms:
- Export the multi-sig setup from Coldcard as a text file.
- Open the file in a plain-text editor.
- Add or correct the missing format line so it matches the proper Casa nested Segwit structure.
- Save the corrected file.
- Import that corrected file into Coldcard again.
Once done correctly, you can verify addresses on Coldcard and sign transactions without downgrading your security by enabling trust PSBT mode.
What this means for your Casa security
Recreating your Casa wallet outside the app is not just a “nice to have.” It changes how much confidence you can place in the system.
You get:
- Independent address verification
- A working backup method for signing transactions
- A clearer understanding of sovereign recovery
- Better protection against UI or platform mistakes
- More familiarity with multi-sig tools if you later move to a DIY setup
If Casa were ever compromised, unavailable, or if your access were revoked, having a quorum of keys and the ability to reconstruct the wallet in Sparrow gives you real operational control.
My recommendation is simple: do not just trust that everything works because the app says so. Rebuild it. Verify addresses on more than one device. Practice signing without Casa’s platform. Understand where the fingerprints, xpubs, derivation paths, and script types come from. That is what turns a hosted multi-sig service into something you can actually reason about as a security system.
If you are new to multi-sig, starting with a guided setup like Casa is sensible. But I would not stop there. Learn how the wallet works underneath the interface. That knowledge is the difference between using a product and truly securing your Bitcoin.
Questions from viewers
Common questions from the comments on this video, with my answers.
How does the network verify that a transaction doesn't exceed my account balance if I have multiple addresses?
In Bitcoin, there is no single 'account' with a total balance that nodes check against. Instead, a transaction is made up of multiple inputs and outputs. Each input is validated individually to ensure it is unspent and valid; they don't even need to come from the same logical account. As long as all individual inputs are valid, the transaction is accepted. Your wallet handles the complexity of selecting which specific addresses (inputs) to use to cover the amount you want to send.
Why do I pay more in fees when sending from a wallet with many small balances?
Transaction fees are based on the data size used for the transaction, not just the amount sent. If your funds are spread across multiple addresses, your wallet needs to include multiple inputs in the transaction to gather enough coins. More inputs mean more data, which results in higher fees.
What is the purpose of the master fingerprint in a multisig wallet setup?
The master fingerprint is simply a quick way to identify that you have the correct wallet configuration. It acts as a short, simple identifier that helps you verify you are working with the right set of keys, rather than having to manually verify longer details like the first address in the wallet.
I can't find my Trezor or Ledger address in MetaMask after importing the seed phrase. How do I fix this?
When you import your hardware wallet into MetaMask, it will ask you to choose a derivation path. For most standard setups, try selecting the BIP44 standard path. This is usually the correct one for finding your existing assets. If you are using a hidden wallet with a passphrase, make sure you enter that passphrase correctly in any tool you are using to derive keys.
My Sparrow wallet 'Apply' button is greyed out when trying to recreate my multisig. What should I check?
Ensure you have populated all fields in Sparrow, including the fingerprints. If the button remains disabled, look closely at the text entry boxes and keystores; one of them will likely have a pink outline around it. This indicates that specific piece of information is invalid or incorrect. Double-check your xpubs, fingerprints, and derivation paths for typos or mismatches.
Can I recover my seed phrase if I only have my wallet address?
No, this is not possible. If you only have an address, you have nothing to work with. Recovery is only feasible if you are missing a very small number of seed words (typically between one and three). Anyone claiming they can recover a full seed phrase from just an address is a scammer.
Stuck with a wallet recovery?
I maintain BTCRecover and have helped people recover seed phrases, passphrases and wallet passwords since 2019. Book a one-hour video session and I’ll walk you through doing the recovery yourself, without sharing your seed. Or, if you’d rather I run it, a trusted recovery is charged only if it succeeds.
Private sessions: US$100 per hour. Trusted recovery: 10% of recovered funds. I never contact people first and will never ask for your seed phrase over chat or email.
Found this useful?
These guides are free and ad-free. You can support them by sharing them, subscribing on YouTube, or sending a tip.







