ACADEMY / From zero to privacy in Bitcoin.
L30 · M06

Finalizing, broadcasting and troubleshooting

55 minEssential

Objective

Complete the payment without duplicating it and diagnose failures by stage.

Understanding the topic

After importing a signature, Desk must verify it belongs to the draft and preserves the intended transaction. A multisignature threshold may still be unmet. Importing a single-signature authorization does not remove the need for review either. Once the conditions are met, finalizing produces the transaction ready to broadcast.

Broadcast only after the final review. A server response or txid gives a result for the request. Follow-up still needs to confirm acceptance and chain status. If the app received no response, check before retrying. Do not create another payment to solve a display problem.

For a pending payment, review the fee rate, validity, conflicts and actual support for RBF. A change of policy or recipient requires appropriate new signatures on the new proposal. Local cancellation neither destroys a signature or transaction already retained by another party nor revokes a confirmed transaction.

Diagnose preparation, transport, unlocking, review, signing, return, validation, finalization, broadcast and confirmation separately. Record system, version, model, stage, approximate time and error code. The app’s diagnostics are designed to exclude sensitive data, but review them before sharing. Do not attach backups, QR codes, your Chat Key or credentials.

Practice

  1. Order the states of a fictitious payment and identify where you could safely pause.
  2. Work through insufficient funds, a missing USB response and a disconnection during broadcast.
  3. Write a support ticket using synthetic data and a verifiable expected result.

Show what you know

Decide whether the student, device, coordinator or network still needs to act, and avoid making an unnecessary second payment.

Common question

Should I respond to FIRMWARE_CAPABILITY_REQUIRED by changing firmware blindly? No. In the documented Desk incident, recognition of the Final build required a correction to Desk’s catalog. Check version and profile before changing devices.

Pause point

Save the status and next action. If you broadcast a real transaction outside the lab, keep its record in your private documentation.

Which action can, on its own, revoke an already confirmed transaction?

Reading, self-assessment and physical practice are different. This result is not a certificate.