Check, stop and recover a Bitcoin workflow
Stop at the first mismatch and preserve the original request or file. A retry that silently changes the wallet, recipient, fee or signing policy is a new transaction decision and needs a fresh review.
Watch the overview: Check, stop, recover.
Before you start
Record the application, network, account path, script type, passphrase choice, transfer method and exact error. Exclude secrets. Start with general connection troubleshooting if the application cannot reach KeepKey.
Check the wallet and account
- Keep the existing public wallet file and record the exact error. Do not wipe KeepKey, restore a seed or enable new settings merely to fix an empty view.
- Reconnect the intended KeepKey and unlock the intended wallet. If you already use a passphrase, reproduce its exact case, spacing and punctuation.
- Check Bitcoin network, account number, script type and account path. For an address comparison, choose the same receive branch and index.
- Open Receive and choose Verify on Device. Compare the complete address with your trusted record for that derivation.
- If Desktop says Not this wallet, resolve the account or passphrase mismatch before proceeding.
Stop a changed recipient
- Obtain the recipient address through a trusted channel and confirm the Bitcoin network and amount.
- In Desktop’s PSBT review, inspect every TO output, including change. Check the amounts, fee and expected device total.
- Choose Cancel in the review when anything differs. If device prompts are already open, reject the request instead of approving it.
- Correct the recipient or amount there, build a fresh transaction and export a fresh unsigned PSBT.
- Signing alone does not broadcast. A signed file can still authorize the payment, so do not share an unwanted result.
Recover a PSBT transfer
- Keep the unsigned file and Desktop’s exact error. Keep signed results separately.
- For an invalid or truncated PSBT, return to the creating wallet and save a fresh PSBT. Copy that file again, then drop it into Desktop.
- If previous transaction data is missing, re-export with full previous transactions and key paths needed by the signer.
- For Not this wallet, check the intended account and passphrase. For an expired review, drop the file again after unlocking the intended wallet.
- Never repair by guessing amounts, addresses or key paths. Return to the creating wallet for corrections.
Check signing compatibility
- First identify the handoff: USB device connection, transaction file import or QR decoding.
- For the Sparrow USB route, close competing device applications and scan again for the intended hardware wallet.
- For this single-signature file route, export a complete PSBT for the intended account.
- For QR, confirm the sender and receiver support the same encoding. Complete the scan, then inspect the decoded transaction.
- Native SegWit, Taproot and multisig have different signing requirements. Use the lesson for the exact account and policy.
Verify the result
Repeat account/address comparison and review the recovered original PSBT before device approval. After signing, verify the signed result and check broadcast/confirmation separately. Use a fresh snapshot or file review rather than relying on the screen that preceded the error.
If something fails
If you cannot establish the account, intended outputs or fee, leave the request unsigned. Share only a redacted diagnostic through official support. Never wipe a funded device or enter recovery words into a coordinator as a troubleshooting shortcut.