Dedicated Crypto Device: Air-Gapped Setup
The single most effective way to protect a cryptocurrency private key from remote attackers is to ensure it never touches an Internet-connected machine. An air-gapped device—physically isolated from any network—eliminates entire classes of attack, from phishing to remote code execution. While hardware wallets offer a convenient off-the-shelf solution, building your own dedicated signing device from a Raspberry Pi or an obsolete smartphone gives you complete control over the hardware, software, and update policy.
This guide is written for advanced users who understand transaction mechanics and want to construct a signing tool that is transparent, verifiable, and free of closed-source components. You will learn how to select suitable hardware, install a minimally secure operating system, configure signing software (Electrum, Bitcoin Core, or Armory), and execute a safe offline signing workflow. The emphasis is on durable principles—how the isolation works, what attack surfaces remain, and how to mitigate them—rather than ephemeral software versions or live prices.
By the end of this article you will possess a repeatable blueprint for a cold-storage signing device that can handle Bitcoin, Ethereum, or any UTXO-based chain, and you will understand the operational trade-offs involved. No network connection, no Bluetooth, no WiFi—just a machine that signs and nothing more.
- An air-gapped device physically isolates private keys from any network, eliminating remote attack vectors such as malware, phishing, and keyloggers.
- Choose a Raspberry Pi (preferably Zero without wireless) or an old phone with radios physically disabled; both allow a fully auditable signing environment.
- Install a minimal, verified OS (Raspberry Pi OS Lite or Alpine Linux) and blacklist all networking kernel modules to ensure true isolation.
- Use a watch-only wallet on an online machine to create unsigned PSBTs, transfer them to the air-gapped device via USB, QR, or SD card, sign, and transfer back.
- Always decode and verify the signed transaction on the online machine before broadcasting; one wrong character can send funds to an attacker.
- Operational security measures—physical access control, ephemeral storage, and regular re-imaging—are as important as the hardware and software choices.
Why an Air-Gapped Device? Understanding the Threat Model
A hardware wallet secures private keys inside a dedicated chip, but its security ultimately depends on the vendor’s firmware, supply chain, and the user’s trust that no hidden backdoors exist. Building your own air-gapped device removes that trust requirement: you audit the software, you control the update cycle, and you physically disconnect all networking components. The threat model you defend against includes remote exploits (phishing, malware, keyloggers), supply-chain attacks on commercial hardware wallets, and sophisticated physical attacks that require the device to be online.
However, air-gap is not a silver bullet. The device can still be compromised if you introduce malicious software via USB or SD card, or if an attacker gains physical access. The goal is to reduce the attack surface to the narrowest possible channel: only the transfer of unsigned and signed transactions. All other vectors—internet, Bluetooth, WiFi, NFC—are permanently disabled. This forces an attacker to either corrupt the signing process at the point of transaction creation or physically tamper with the device.
“The security of an air-gapped setup is proportional to the rigor of your operational security. No network is the easy part; the hard part is ensuring that every software component you install is genuine and that the data you transfer between devices is authentic.”
For an advanced user, this approach offers maximum transparence. You can compile the signing software from source, verify GPG signatures, and even run a minimal Linux kernel with only the drivers you need. The device becomes a dedicated signing appliance—nothing more, nothing less.
Selecting the Hardware: Raspberry Pi vs. Old Phone
For a dedicated signing device, you need hardware that can be permanently isolated from networks. Raspberry Pi boards are a popular choice, but you must account for onboard radios: the 3B+ and 4 have built-in WiFi and Bluetooth that must be disabled (via a config overlay or by blacklisting the kernel modules), whereas the original Pi Zero ships with no wireless chips at all. An old phone, on the other hand, usually has WiFi, Bluetooth, and cellular radios soldered to the board—these can be physically removed or disabled at the kernel level. Both options have trade-offs.
| Factor | Raspberry Pi | Old Phone |
|---|---|---|
| Network isolation | Easily permanent (remove antenna, disable via config) | Harder; radios often cannot be fully disabled without hardware mod |
| Power supply | USB-C, external battery possible | Built-in battery (degradation risk) |
| Display & input | External HDMI + USB keyboard | Touchscreen, built-in keyboard |
| Software maturity | Excellent (ARM Linux, Electrum, Bitcoin Core) | Depends; Android or postmarketOS possible |
| Physical tampering | Open board, easy to inspect | Enclosed, harder to verify |
| Cost | $35–$75 | Often free (spare device) |
For maximum security, choose a Raspberry Pi Zero (no wireless) and remove the GPIO headers if you won't use them. For an old phone, remove the back cover and detach the antenna flex cables. Whichever you choose, never connect it to WiFi or Ethernet—even once. The device should be provisioned via a dedicated offline SD card or USB drive that is created on a trusted, air-gapped computer.
Preparing the Operating System: Minimal and Verified
Your signing device must run an operating system that is auditable and contains no unnecessary services. For Raspberry Pi, use Raspberry Pi OS Lite (no desktop) or a hardened distribution like Alpine Linux. For old phones, consider postmarketOS or a minimal Android build with all radios disabled. Avoid any OS that phones home or auto-updates without your consent.
- Install from a verified image: Download the OS from the official source, verify the checksum against the published SHA256 hash, and ideally verify the GPG signature of that hash.
- Disable all networking at boot: Blacklist kernel modules for WiFi (brcmfmac, mac80211), Bluetooth (btusb), and Ethernet (if using a Pi with Ethernet chip). Add them to /etc/modprobe.d/blacklist.conf.
- Remove unnecessary packages: Uninstall avahi-daemon, cups, bluetooth, and any network management tools. The fewer binaries, the smaller the attack surface.
- Use a read-only root filesystem: Mount the root partition as read-only after initial configuration to prevent persistent malware.
- Enable full-disk encryption (optional but recommended): If the device is stolen, encryption prevents extraction of private keys. Use LUKS on Linux or equivalent on Android.
After setup, test that no network services are listening (run ss -tulpn) and confirm that the device has zero IP addresses assigned. The only communication channel should be physical media: USB drive or SD card.
Installing and Configuring the Signing Software
Choose a signing tool that supports offline transaction creation and has a proven security track record. For Bitcoin and other UTXO chains, Electrum is the most practical: it runs on low-power ARM devices, allows you to view addresses and balances (by importing a public key from a watch-only wallet on your online machine), and signs partially signed bitcoin transactions (PSBTs). For Ethereum, use MyEtherWallet or a standalone signing tool like ethsign. For maximum control, compile Bitcoin Core from source and use its `signrawtransactionwithkey` RPC.
Install the software on the air-gapped device using a USB drive that contains the binary and its signature. Verify the GPG signature (e.g., for Electrum, import ThomasV’s key and check the .asc file). Do not download anything over the internet on the device itself—always transfer files via physical media from a trusted offline computer.
Once installed, generate a new wallet directly on the air-gapped device. Write down the seed phrase on paper (never store it digitally). Optionally, add a passphrase for extra protection. Then derive the master public key (xpub or ypub) and transfer that to your online watch-only wallet. This online wallet will create unsigned transactions (PSBTs) that you can copy to the air-gapped device for signing.
Transferring Transactions: USB, QR Codes, or SD Cards
After the online watch-only wallet creates an unsigned transaction, it must be physically moved to the air-gapped device for signing. There are three main methods, each with distinct security trade-offs:
- USB drive: Write the unsigned transaction as a file (e.g., .psbt) to a USB drive, plug it into the air-gapped device, sign, and copy the signed file back. Risk: the USB drive can introduce malware if it was previously connected to an infected machine. Mitigation: use a dedicated USB drive that never touches any online computer; format it as FAT32 and only use it for transaction files.
- QR codes: Display the unsigned transaction as a QR code on the online machine, then scan it with the air-gapped device’s camera (if using an old phone with camera disabled otherwise). This eliminates the USB attack vector but introduces complexity: transaction data can be large (especially with many inputs) and may require multiple codes. Also, the camera module itself could be a vector—disable it after scanning.
- SD card: For a Raspberry Pi, you can swap the boot SD card to a second card containing the transaction. This is cumbersome but effectively air-tight if the second card is never used elsewhere.
Whichever method you choose, always verify the signed transaction on the online machine before broadcasting. Use `bitcoin-cli decodepsbt` or Electrum’s transaction preview to confirm the output addresses and amounts.
The Signing Process: Step-by-Step Workflow
The actual signing is straightforward but must be methodical to avoid mistakes. Here is the standard workflow for a Bitcoin PSBT-based setup:
1. Create unsigned transaction on online machine: In your watch-only wallet (e.g., Electrum with a public key only), construct the transaction: inputs (UTXOs), outputs (addresses and amounts), and fee. Export as a PSBT file.
2. Transfer PSBT to air-gapped device: Use one of the methods above. Ensure the file is intact—compare its hash on both devices if paranoid.
3. Sign on the air-gapped device: Open the signing software, load the PSBT, and use the private key to sign. For Electrum: File -> Load Transaction -> Open, then click Sign. The device will output a fully signed PSBT.
4. Transfer signed PSBT back to online machine: Same physical channel. Verify the signed transaction by checking that the final hex contains the witness data.
5. Broadcast on online machine: Use any Bitcoin node or block explorer to relay the signed transaction to the network. Wait for confirmations.
6. Optionally, wipe the unsigned PSBT from the air-gapped device: This prevents clutter and reduces forensic risk. Some users keep no transaction history on the signing device at all.
This workflow separates the duties: the online machine handles network communication and transaction construction; the air-gapped machine holds the keys and signs. Neither can do the other’s job in isolation.
Verifying and Broadcasting: Ensuring Integrity
Once the signed transaction arrives back on the online machine, do not broadcast it blindly. First, decode it to human-readable form with bitcoin-cli decodepsbt or Electrum’s “Preview” feature. Verify that:
- The outputs match exactly what you intended (same addresses, same amounts).
- The fee is acceptable.
- The inputs are correct UTXOs (not dust or miner coinbase outputs).
- The PSBT has all required signatures (look for "Finalized" status in Electrum).
If anything appears off, do not broadcast. Investigate whether the unsigned transaction was tampered with during transfer or if a bug exists in the signing software. A false step here could send funds to an attacker. Only after confirming full correctness should you broadcast the transaction via your own node or a trusted public service.
After broadcasting, monitor the transaction ID on a block explorer to ensure it is confirmed. Some users keep a record of the signed hex on the air-gapped device as a fallback for rebroadcasting—but this is optional and adds complexity.
Operational Security and Physical Safeguards
An air-gapped device is only as secure as the physical environment in which it operates. Consider the following operational security (OpSec) measures:
- Physical access control: Store the device in a locked drawer or safe when not in use. If it is a Raspberry Pi, consider epoxy-potted case to prevent tampering with the JTAG or GPIO pins.
- Ephemeral storage: Do not keep private keys on the device after signing. Some users generate new wallets for each signing session, but this is impractical for frequent use. Instead, use a passphrase-encrypted wallet that is decrypted only for the signing moment.
- Anti-glitch and anti-probing: If you are concerned about hardware attacks, consider conformal coating or disabling the USB port that is not needed.
- Seed phrase backup: Keep the paper backup in a fireproof safe, separate from the device. Never store the seed digitally—not even on the air-gapped device itself after initial generation.
- Regular updates: Every few months, re-image the SD card with a fresh, verified OS and software. This prevents any latent malware from persisting in unused blocks.
Remember that a motivated physical attacker with sufficient resources can bypass almost any software protection. The goal is to raise the cost of attack far above the value of the funds.
Limitations and Trade-Offs: Is This for You?
Building your own air-gapped signing device is not for everyone. It requires significant technical skill, time, and discipline. The convenience is low—every transaction involves at least four physical transfers (two for the unsigned transaction, two for the signed). Compare this to a hardware wallet that can sign with a single USB connection. The trade-off is that you own the entire stack: you can verify every byte of code and hardware.
Common failure points include: accidentally connecting the device to a network during provisioning, using compromised software because you skipped GPG verification, or losing the seed phrase because you stored it on the device. Additionally, signing large multisig transactions can be slow on a Raspberry Pi Zero. For Ethereum, the workflow is less mature; PSBT-like standards (EIP-712) exist but are not as universally supported as Bitcoin’s.
If you manage several high-value wallets and are willing to invest in the upfront setup, this approach is unmatched in transparency. For most users, a reputable hardware wallet from a vendor with a proven track record is a more practical choice. But for the advanced user who wants zero trust, the air-gapped device remains the gold standard.
Frequently asked questions
Can I use a Raspberry Pi with built-in WiFi if I never connect it?
Technically yes, but it's risky. The WiFi chip could be exploited via close-proximity attacks if powered. Physically removing the antenna or disabling the module via config.txt is safer.
How do I update the signing software on an air-gapped device?
Download the new version and its GPG signature on a trusted offline computer, verify, then transfer the binary to the air-gapped device via USB. Re-image the SD card entirely for major OS updates.
Does this work for Ethereum or other non-Bitcoin chains?
Yes, but the tooling is less mature. For Ethereum, use MyEtherWallet or ethsign with offline-created transactions. Standards like EIP-712 improve this but require more manual steps.
What if my air-gapped device is stolen?
If you used full-disk encryption and a strong passphrase, the thief cannot extract the private keys. The seed phrase backup (stored separately) allows you to recover the wallet on a new device.
Related reading
Track the entities behind the concepts
DeFi Intel maps 11,000+ protocols, tokens and companies to a typed knowledge graph — with live data, incidents and regulation.