Air‑gapped signing — offline transaction signing explained
What is air‑gapped signing?
Air‑gapped signing is the practice of keeping the device that holds private keys completely offline while using a separate online computer or phone only to build and broadcast transactions. The hardware wallet (the thing that actually signs) never connects to the internet, so signing happens in an isolated environment. Why does that matter? Because an attacker on your online machine cannot directly extract private keys if they never exist on that machine.
Short sentence. Simple idea.
This article explains how an air‑gapped ledger or other hardware wallet performs offline signing, the common workflows (the "cold signing workflow"), and concrete steps you can follow. In my testing I found the method reliable, but it does increase operational complexity (and human error risk). But you’ll trade convenience for fewer remote attack surfaces.
Sources: the Partially Signed Bitcoin Transaction (PSBT) standard explains the signed-file approach used by many air‑gap workflows (BIP‑174). The recovery standards for seed phrases are in BIP‑39.
Why offline signing matters for long-term storage
Remote attackers commonly exploit compromised hosts (malware that reads memory, intercepts clipboard contents, or tampers with transaction data). An air gap removes the direct path from host to private key. That reduces the risk of remote theft during signing.
Think of it like signing a physical check in a locked room. The check can be altered before it leaves. So you verify the recipient, amount, and fee on the device screen before signing.
Real-world context: after high-profile exchange failures, many long‑term holders moved assets into offline custody. The principle is straightforward: reduce the places your private keys can be leaked from.
How air‑gapped signing works (technical overview)
At a high level the flow is:
- Build an unsigned transaction on an online machine (wallet software). This can be a PSBT file for Bitcoin or a JSON payload for some other chains.
- Transfer the unsigned payload to the offline hardware wallet using an air‑gap channel (QR, microSD, or an intermediary offline host).
- Review full transaction details on the hardware wallet's screen (destination address, amount, fee, change path). Confirm only after careful verification.
- The hardware wallet signs the transaction offline, producing a signed payload.
- Transfer the signed payload back to the online machine and broadcast to the network.
This pattern is the foundation of an offline signing ledger approach. The PSBT spec is the formal standard for step‑by‑step multisig and single‑sig signing in Bitcoin (BIP‑174).
Common air‑gap transfer methods (comparison)
| Method |
How data moves |
Typical security level |
Pros |
Cons |
| QR code (camera / display) |
Unsigned tx shown as QR on online machine, scanned by device camera (or vice versa) |
High (no removable media) |
Fast, visually verifiable |
Limited payload size; camera attack surface if compromised |
| microSD / removable file |
File copy between devices |
Medium–High |
Supports larger payloads; robust |
Risk if file copied from compromised host |
| USB stick via offline host |
File moved using an offline laptop as intermediary |
High if offline host is clean |
Works for large multisig PSBTs |
Requires dedicated offline host (administrative overhead) |
| Direct USB with cable (but offline host) |
Device physically connected to a closed, air‑gapped host |
High |
Reliable for power/signing |
Needs strictly offline host |
| Bluetooth / NFC |
Wireless channel |
Low (not air‑gapped) |
Convenient |
Increases attack surface; not true air gap |
I prefer QR or microSD in long tests because they minimize direct connections. And yes, each method has trade‑offs.
Sources: PSBT guidance (BIP‑174) and general air‑gap descriptions (see general air‑gap documentation).
Step‑by‑step: example cold signing workflow
How it looks in practice for a Bitcoin-like workflow (PSBT):
- On your online computer, open a wallet app and create a standard transaction. Choose fee and recipients. Export as PSBT. (This is the unsigned file.)
- Transfer the PSBT to the offline device using your chosen channel (QR or microSD).
- On the hardware wallet, inspect: destination address, amount, fee, and change output (if visible). The device should show the full address. Do not accept if the address is truncated or looks suspicious.
- Approve the transaction on the device. The device will produce a signed PSBT or raw signed transaction.
- Move the signed file back to the online computer and broadcast.
Review what you see on the device screen. Confirm the address is exact. Ask: does this match the intended recipient? (Check the last 4–6 characters if necessary.)
If you use passphrases (a '25th word'), remember the passphrase must be entered on the signing device or an air‑gapped host. If you lose it, recovery from the seed phrase alone will not restore funds (BIP‑39 explains the seed format).
Air‑gapped signing in multi-signature setups
Multisig increases resilience. Each cosigner can be an air‑gapped hardware wallet. PSBT is explicitly designed to collect multiple signatures without exposing keys (BIP‑174).
Workflow: create a multisig PSBT on an online coordinator, export it to each offline signer in turn, collect signatures, then finalize and broadcast. This is standard for vault-grade custody.
Compatibility matters. Ensure the wallet software you use supports PSBT and the multisig scheme you choose. See the multisig-compatibility and multisig pages for deeper setup notes.
Security trade‑offs and best practices
Air‑gapped security reduces remote attack vectors but increases human and operational risk. Complex procedures are mistakes waiting to happen. Follow these principles:
- Verify firmware signatures before use; don’t install unsigned firmware. See firmware-updates and verify-firmware.
- Use a trusted supply chain (avoid unofficial resellers). See where-to-buy.
- Back up your seed phrase with an appropriate backup method (metal backup plates or Shamir splits). See metal-backup-plates and shamir-backup-slip39.
- Treat passphrases like keys; store them separately and securely. See passphrase-25th-word.
- Prefer devices that use a certified secure element (FIPS/Common Criteria). Learn why on the secure-element page and read cryptographic guidance from NIST (FIPS 140‑3).
But remember: the best security is reproducible by you. If the workflow is so awkward you avoid practicing it, it fails.
Who should use air‑gapped signing (and who should look elsewhere)
Best for:
- Long‑term holders keeping large balances offline.
- Multisig vault builders and estate planning setups.
- People who can maintain a dedicated offline workflow and are comfortable with extra steps.
Not ideal for:
- Daily traders or users who need frequent quick transactions.
- New users uncomfortable with file transfers and manual verification.
If you’re unsure, try a non‑critical test with a small amount first. In my experience, that practice reveals workflow gaps quickly.
Common mistakes and quick checklist
Quick pre‑sign checklist:
- Is firmware verified? (verify-firmware)
- Is the unsigned tx exactly what I intended? (addresses, amounts, fees)
- Are all signers present for multisig? (multisig-setup)
FAQ
Q: Can I recover my crypto if the device breaks?
A: Yes, if you have a correct seed phrase or Shamir shares and you restore those on a compatible hardware wallet or recovery tool. Without the seed phrase (and passphrase if used), recovery is impossible. See backup-and-recovery and shamir-backup-slip39.
Q: Is Bluetooth safe for a hardware wallet?
A: Bluetooth increases convenience but is not an air gap. It adds a wireless attack surface. For the highest security (cold signing) use non‑wireless transfer methods and treat Bluetooth as a compromise if you require strict isolation. See connectivity-usb-bluetooth-nfc.
Q: What happens if the company behind my device goes bankrupt?
A: Your assets are tied to your seed phrase and passphrase, not the company. As long as standards (BIP‑39, BIP‑32/44 derivation) are followed, you can restore on other compatible wallets. Plan backups and document recovery procedures; see company-risk and backup-and-recovery.
Conclusion & next steps
Air‑gapped signing is one of the most effective ways to reduce remote attack surfaces for long‑term crypto storage, but it requires disciplined operational practice. I believe anyone storing meaningful balances should at least understand the cold signing workflow and practice it with small transfers first. Want to build a secure routine? Start with the getting-started and setup-initial guides, then review firmware-updates and multisig if you intend to scale security.
Check related guides: seed-phrase, passphrase-25th-word, and secure-element for more technical depth.
And finally: practice the workflow before trusting it with large amounts. Small tests catch mistakes early.
