Offline and air-gapped setups
A hardware wallet separates signing keys from the ordinary apps on your computer. You can add another separation by keeping the computer used for signing disconnected from the network. These are different layers, and it helps to name which one you mean.
Start with the hardware-wallet basics and signing checks. A separate-computer workflow is an option for owners who can maintain the additional steps; it is not required to begin using KeepKey.
What does air-gapped mean?
An air gap separates systems without a direct physical connection between them, with transfers performed manually under human control. That is the distinction in the NIST glossary .
In a wallet setup, be specific about what is separated: the hardware device, the signing computer, or the online computer. Transaction data still has to reach the signer and the signed result must eventually reach a network-connected system.
| Term | What it describes | What it does not establish |
|---|---|---|
| Hardware key isolation | Keys are generated and used in a separate signing device during normal operation. | That the connected computer is offline or every request is safe. |
| Offline application mode | Software operates without requesting network data. | That the computer’s radios, cables and other programs are disconnected. |
| Disconnected signing computer | The computer used with the signer has no network connection. | That imported files, QR data or installed software are trustworthy. |
| Air-gapped transfer | Separated systems exchange data manually, such as through a file or optical transfer. | That the transferred data is harmless or review is unnecessary. |
Turning off Wi-Fi is only one check. A signing computer may also have Ethernet, cellular, Bluetooth or other network paths. Prepare the software and verification material before disconnecting, and deliberately check the connections used by that machine.
Where KeepKey fits
KeepKey is a USB signing device. It connects to the computer running the wallet software. It does not have a camera or a removable-media signing slot, and a normal USB connection to an online computer is not an air gap between that computer and KeepKey.
You can instead connect KeepKey to a disconnected signing computer. The online computer holds public wallet information and prepares transactions. A manually transferred file or compatible QR sequence carries data between the two computers; KeepKey’s own connection remains USB.
Follow one Bitcoin payment
A partially signed Bitcoin transaction, or PSBT , packages transaction information for software and signers to exchange. It is a request to inspect, not a promise that the payment is correct.
- Prepare online. A watch-only wallet uses public account information to build the unsigned transaction. It does not need your recovery words or private keys.
- Transfer the request. Move the complete unsigned file or compatible QR sequence to the disconnected signing computer.
- Inspect before signing. Check wallet/account information, destinations, amounts, every output and the fee in the signing app and on KeepKey.
- Approve on KeepKey. The device signs the supported request after your confirmation.
- Return the result. Transfer the signed transaction back to the online computer and inspect it again.
- Broadcast and confirm. Submit the intended transaction to the Bitcoin network. A saved signed file is not yet a network confirmation.
The separate-computer guide covers prerequisites, saved files and resuming interrupted work. PSBT review explains complete signing data and change checks.
What QR changes
QR is a way to transfer data between the computers. Both apps need compatible encoding and enough information to complete the signing process. The cameras in this workflow belong to the computers; KeepKey still connects by USB.
What isolation helps with—and what remains
Separating the signing computer can reduce direct exposure to online applications while you sign. It also adds a computer to maintain, a transfer process and more opportunities to lose or confuse files.
Both a QR image and a file contain data that software must parse. Malformed data, compromised software, misleading transactions and mistakes can still cross the workflow. An offline signer can authorize a payment to the wrong recipient just as an online signer can. A transport choice alone does not establish an overall security ranking.
Keep reviewing the actual payment. Protect backups and passphrases separately, verify software, and practice the complete recovery and transfer process before relying on it for significant funds.
Choose the next layer deliberately
- For privacy while checking balances, read watch-only wallets. Public account information cannot sign, but can reveal account history.
- For control over network queries, read using your own node. A node and an air gap solve different problems.
- For multiple independent signing devices, read multisig. It adds a signing policy and backup responsibilities; it does not replace transaction review.
Continue: Hardware and research covers secure elements, passphrases, firmware verification and vulnerability reports.