Bitcoin workflows
Watch: Choose your Bitcoin path.
Start with account and address types, fees and change and device review. Choose the simplest workflow you can verify and recover. Added computers, applications or signers add operational responsibilities as well as capabilities.
| Goal | Written walkthrough |
|---|---|
| Sign on one computer | Desktop, Sparrow and Electrum |
| Watch and prepare without signing | Public account exports and comparison |
| Keep the signing computer disconnected | Files, QR and interrupted transfers |
| Use different wallet applications | Metadata, complete PSBTs and signed results |
| Control the wallet data source | Core, Electrum servers and Blockbook |
| Understand server privacy and transaction state | Server checks and update phishing |
| Authenticate or reproduce firmware | Firmware verification workflow |
| Require independent signing keys | Multisig setup, signing and recovery |
| Resolve a mismatch | Check, stop and recover |
Prerequisites and compatibility
Download KeepKey Desktop through the official page. The videos cover specific capabilities: public wallet export, PSBT import, QR, self-host nodes and multisig controls must exist in the build you use. Check the live controls and applicable release notes. If a feature is absent, stop at its prerequisite rather than substituting a recovery-phrase import or weakening transaction checks.
Use each third-party wallet’s official installation and verification instructions. Never enter KeepKey recovery words into a coordinator to connect hardware or import a public wallet. Select the intended network, account, script type and passphrase before comparing addresses or signing.
Know which state you reached
Prepared means a proposed payment exists. Signed means the signer produced its approval. Submitted means a network broadcast was attempted and has an identifier/result. Confirmed means inclusion has been checked. Read a block explorer and reconcile the result before retrying a payment.