Running Wasabi Wallet Offline: Cold Storage Setup and Air-Gapped Transaction Signing

A Bitcoin holder with substantial positions faces a recurring security dilemma: maximize privacy through CoinJoin technology while minimizing exposure to online threats. Centralized exchanges hold custody and create regulatory vulnerability. Hot wallets on internet-connected devices invite malware and theft. The practical answer for advanced users is not to choose between privacy and security, but to combine them through an air-gapped architecture where key signing never touches a network.

Wasabi Wallet’s integration of CoinJoin provides strong transaction privacy, but that privacy is only meaningful if the wallet itself is not compromised. Running Wasabi in an offline environment, signing transactions on an isolated machine, and broadcasting only the final result to the network creates a setup where blockchain surveillance becomes difficult while direct key theft becomes much harder. This approach requires more operational discipline than a standard wasabi wallet download and everyday use, but the security improvement justifies the added complexity for users managing significant amounts.

Understanding air-gap architecture and why it matters

An air-gapped system operates on the principle of physical isolation. The signing machine (where private keys live) is never connected to any network. A separate broadcast machine, connected to the internet, handles communication with the Bitcoin network but never touches private keys. Information moves between them through deliberate, controlled channels—typically a USB drive formatted to prevent cross-contamination—rather than through a network connection.

The security benefit is substantial. Malware designed to steal private keys cannot reach them if they exist only on a machine with no network access. A compromised internet connection cannot directly steal keys or broadcast unauthorized transactions. Keyloggers, packet sniffers, and remote access trojans are rendered ineffective because the signing machine has no pathway for outbound communication. This does not make the setup impenetrable; physical access to the signing machine, a poorly managed recovery phrase, or social engineering can still create vulnerabilities. But it removes an entire category of remote attack vectors.

Wasabi Wallet’s architecture supports this model. The wallet can be run in watch-only mode on the broadcast machine, monitoring addresses and constructing unsigned transactions. The unsigned transaction data can then be transferred to the signing machine via USB, where Wasabi or a compatible signing tool approves it using the private key. The signed transaction returns to the broadcast machine and is transmitted to the Bitcoin network. The user retains full privacy benefits through CoinJoin while keeping keys isolated from any connected device.

The trade-off is operational friction. Creating, reviewing, and broadcasting a transaction takes several steps instead of one click. Recovery procedures become more involved. If the signing machine is lost or damaged, recovery depends entirely on a physical backup of the recovery phrase. The backup itself becomes a critical security object requiring careful storage and controlled access. These are acceptable costs for managing larger holdings or for users operating in high-threat environments.

Choosing hardware and preparing the offline machine

The signing machine should be a dedicated device used only for key storage and transaction approval. An old laptop, a Raspberry Pi with appropriate software, or even a desktop computer can work. The critical requirement is that it never connects to the internet. This means disabling all wireless capabilities if possible—removing or disabling the WiFi card, ensuring Bluetooth is off, and confirming that no network cable is attached.

Begin with a clean operating system installation from verified media. For Linux users, a minimal distribution or specialized air-gap-focused OS can reduce the attack surface. For Windows or macOS, download the installation media directly from the vendor’s official site on a different machine and verify cryptographic signatures before use. Do not use pre-installed systems that may contain manufacturer software, unwanted services, or pre-existing compromises.

Disable unnecessary services and features on the signing machine. Turn off automatic updates if the mechanism requires network access to check for updates; instead, update the operating system only through deliberate, controlled procedures using an offline method. Disable audio devices if they are not needed and could be repurposed by malware. Restrict user permissions; do not run Wasabi or signing operations with administrative privileges unless required. Remove or physically disconnect any removable media drives, card readers, or unused USB ports that could serve as covert channels.

Storage on the signing machine should be encrypted. Full-disk encryption using LUKS on Linux, BitLocker on Windows, or FileVault on macOS prevents physical access from yielding usable data if the machine is seized. The encryption key must be strong and different from any other password; write it down and store it offline in a secure location separate from the machine itself. Test decryption and boot procedures before considering the setup complete.

Installing Wasabi Wallet on the offline signing machine

Obtain Wasabi Wallet on the broadcast machine and verify the installation package before transferring it to the signing machine. Download from the official site and confirm the cryptographic signature of the binary. Wasabi publishes SHA-256 hashes and GPG signatures on its release page; compare the downloaded file to these values using command-line tools such as sha256sum on Linux or certUtil on Windows. Do not skip this step; a compromised binary undermines the entire security model.

Transfer the verified installer to the signing machine using a USB drive formatted with a clean filesystem. Copy only the installer and verification files; do not transfer any other applications or data that might introduce vulnerabilities. Insert the USB drive into the signing machine, authenticate with the encryption password if prompted, and proceed with installation.

During installation, choose a strong wallet password. This password encrypts the wallet file and confirms approval for transactions. Do not reuse this password from other systems. Do not write it on a piece of paper near your computer or store it in any digital form on the signing machine. Memorize it or store it in a physical safe in a separate location. A compromised password—discovered through shoulder surfing, photographing your desk, or social engineering—can bypass the entire security setup.

Create a new wallet rather than importing an existing recovery phrase into the signing machine. Write down the recovery phrase that Wasabi generates, store it in a safe separate from the signing machine, and verify that you can read it clearly. Test the recovery process on a non-critical wallet first: restore from the phrase to confirm it works, then delete that test wallet. This practice prevents discovering during an actual recovery that the phrase was written incorrectly or stored in an inaccessible location.

Setting up the broadcast machine and transaction flow

The broadcast machine connects to the internet normally and requires Bitcoin Wallet Wasabi Wallet software as well as a full Bitcoin node or connection to a reliable node. A full node provides maximum privacy by eliminating the need to rely on third-party servers for transaction broadcasting and balance information. Wasabi can integrate with a local Bitcoin Core node, though synchronization takes time and requires substantial storage space (approximately 500 GB for the blockchain and indexes).

Install Wasabi Wallet on the broadcast machine in watch-only mode if possible. The watch-only wallet contains public keys (addresses) but not private keys. It can display balances, receive funds, and construct unsigned transactions. Users should download Wasabi Wallet from the official repository and verify the checksum before installation on this machine as well, since the broadcast machine remains internet-connected and potentially vulnerable to man-in-the-middle attacks or malware.

Configure Wasabi to import addresses from the signing machine’s wallet. This can be done by exporting the extended public key (xpub) from Wasabi on the signing machine, transferring it via USB to the broadcast machine, and importing it into the watch-only wallet. Wasabi supports this workflow through its wallet information display. The xpub alone cannot sign transactions or spend funds; it serves only to derive addresses and monitor the blockchain.

When a payment is needed, construct the transaction on the broadcast machine and export it as an unsigned PSBT (Partially Signed Bitcoin Transaction) file. PSBT is a standard format that contains all transaction details—inputs, outputs, amounts, and fees—but no signatures. Transfer the PSBT file via USB to the signing machine, review it carefully in Wasabi (or another compatible signer), and approve it with the wallet password. The signed transaction (now with valid signatures and ready for broadcast) returns to the broadcast machine via another USB transfer, where it is transmitted to the Bitcoin network.

Privacy integration and CoinJoin in an air-gapped setup

CoinJoin transactions through Wasabi work differently in an air-gapped setup. The wallet cannot participate in CoinJoin rounds directly from an air-gapped signing machine because CoinJoin requires real-time coordination with other participants and requires spending coins immediately. Instead, the user may perform CoinJoin transactions on a different hot wallet, or they may use watch-only Wasabi on the broadcast machine to monitor a CoinJoin service and then construct payments that preserve privacy downstream.

One approach is to maintain a separate, smaller hot wallet (not air-gapped) for operational transactions and CoinJoin mixing. Store the majority of funds in the air-gapped cold storage wallet and move smaller amounts to the hot wallet as needed. Use the hot wallet for CoinJoin rounds, paying ordinary fees to the coordinating service. Once funds are mixed and CoinJoin rounds are complete, consolidate the mixed funds back to the air-gapped wallet in a single, carefully reviewed transaction.

This hybrid model trades some operational complexity for a strong security and privacy combination. The largest holdings remain in cold storage, protected from online theft. Regular transaction volume can use CoinJoin to obscure transaction trails. When consolidated back to cold storage, the transaction can be carefully examined to prevent unintended address linking.

Alternatively, users can perform CoinJoin consolidation through a standard non-air-gapped Wasabi Wallet installation, then later transfer the results to the cold storage wallet. This workflow means the CoinJoin service sees the consolidation transactions, but those transactions do not reveal amounts or recipient information to the general blockchain if CoinJoin succeeds in achieving practical untraceability. The air-gapped wallet remains dormant for most operations, activated only for final destination transfers or receiving new funds.

USB transfer protocols and preventing cross-contamination

The USB drive used to transfer files between the broadcast and signing machines should be dedicated to that purpose alone. Format it with a straightforward filesystem such as FAT32 or ext4, not NTFS, to minimize complexity and avoid unnecessary functionality that could be exploited. Some users prefer to use separate USB drives for one-way transfers: one drive always moves data from the signing machine to the broadcast machine, another always moves from broadcast to signing, preventing accidental reverse transfers or confusion about data direction.

Before each transfer, delete the previous contents of the USB drive. Plug the USB drive into the signing machine only when transferring files; disconnect it immediately afterward. Repeat this cycle on the broadcast machine. This practice prevents the USB drive from accumulating old files, prevents cross-contamination if either machine becomes compromised, and ensures that only current, intentional data moves between systems.

Verify file integrity on both ends of each transfer. Export a file with a known hash on the signing machine, transfer it, and verify the hash on the broadcast machine using the same cryptographic tools employed for binary verification. If hashes do not match, something has corrupted or modified the file; repeat the transfer or investigate the USB drive’s health. Trust is not assumed; it is verified through repeatable technical checks.

Consider using a hardware write-blocker if available. A write-blocker prevents the signing machine from modifying the USB drive, allowing only reads. This adds a layer of assurance that malware on the signing machine cannot secretly alter files on the drive or replace unsigned transactions with malicious versions. Write-blockers are inexpensive USB adapters that physically enforce one-way data transfer.

Key recovery, backup verification, and operational discipline

The recovery phrase generated during wallet creation is the single point of recovery for the entire setup. If the signing machine fails, becomes inaccessible, or is damaged, the recovery phrase is the only way to regain access to the funds. Store it with extreme care. Do not photograph it, do not type it into any digital system, do not share it, and do not store it in any cloud service or online backup. Memorize a few critical words to verify you have the correct backup during recovery, but rely on the physical written copy.

Divide the recovery phrase into multiple parts and store them in separate secure locations if the risk of theft or loss is high. A 24-word phrase can be split so that no single location contains all words. This requires careful planning and documented recovery procedures; if recovery procedures fail, funds become irretrievable. Test recovery procedures on a non-critical wallet first, using a copy of the recovery phrase in a controlled environment, before relying on this setup for significant amounts.

Periodically verify that the recovery phrase is still readable and stored correctly. Every 6 to 12 months, access the physical backup, confirm that words are legible, that the sequence is correct, and that you remember any code or location system used. Disasters such as water damage, fire, or decay occur slowly; catching them early prevents loss.

Additionally, maintain a written or encrypted record of the wallet’s extended public key (xpub) in a secure location. The xpub is not secret; it cannot be used to spend funds. But if the signing machine becomes inaccessible and you need to monitor the wallet’s addresses and balance while working on recovery, an xpub allows you to import the wallet into watch-only mode elsewhere. Store this record separate from the recovery phrase in case one location becomes inaccessible.

Testing the setup and operational best practices

Before relying on an air-gapped Wasabi Wallet setup with significant funds, conduct thorough testing with small amounts. Create a test wallet, fund it with a small amount, and perform several complete transaction cycles: construct an unsigned transaction on the broadcast machine, transfer it to the signing machine, review and approve it, transfer the signed transaction back, and broadcast it. Verify that the transaction appears on the blockchain with the expected amount and destination.

Verify the privacy score dashboard in Wasabi to understand how the wallet categorizes address privacy. Ensure that your transaction patterns produce the privacy outcomes you expect. Test sending to multiple addresses and monitor whether the blockchain activity aligns with your assumptions. This testing phase reveals operational gaps, misunderstandings, or technical issues before real funds are at risk.

Establish operational protocols for the setup. Document the step-by-step process for creating, signing, and broadcasting a transaction. Write down security checkpoints: questions to answer before approving any transaction, such as “Does the destination address match my verified list?” and “Does the amount and fee align with my intent?” A documented procedure followed consistently prevents mistakes far better than relying on memory or assumption.

Treat both machines with physical security discipline. The signing machine should be stored in a secure location, powered off when not in use, and accessed only by authorized personnel. The broadcast machine should have strong authentication (passphrase, multifactor authentication to sensitive accounts). If either machine is accessed by others or left unattended in public spaces, assume it may be compromised; run full antivirus scans and consider regenerating wallet keys if the risk is substantial.

Plan for inheritance or emergency access. Ensure that a trusted individual knows how to access the recovery phrase and the broadcast machine in the event of your incapacity. Provide written instructions on the complete setup and recovery procedure, stored separately from the recovery phrase itself. An air-gapped setup is secure only if it remains accessible to the rightful owner; make sure the recovery path is known to someone who can execute it.