M06 · Edition 0.1
Signing with Original and BIT
Free · no registration
Objective
Complete the signing workflow for each model and receive a response linked to the correct transaction.
Understanding the topic
For Original, deliver the PSBT on the transport card using the supported Cuvex Mirror workflow. On the device, read the request, supply the cryptogram and unlock it privately. Review every output and amount, the change and the fee. The device writes its response to the card. It must then be read and validated in Desk. A successful card write does not replace that return step.
For BIT, select the correct volume and deliver the request over USB-C. Desk’s local service handles the expected exchange while you operate the device. Supply the cryptogram as directed and review the transaction on BIT. “Receive from BIT” imports the response. Desk validates and records it before confirming acknowledgment. After a disconnection, resume the same operation. Do not choose another because it looks similar.
For multisignature signing in the Final firmware, review the mandatory summary and outputs, applicable warnings and all three final “Sign PSBT” confirmations. The optional extended review lets you examine additional parameters. Choosing “No” does not remove the mandatory checks. Independent policy verification follows a different workflow and applies only to that particular review.
Signing requires a compatible cryptogram whose authenticity can be verified. An older copy may still recover the secret without being eligible for signing. If the device warns that an old copy lacks verified authenticity, recover and check the secret and create a new copy before signing. Never edit headers or bypass the rejection.
Cancel if an address differs, a fee is unexpected, information is missing, a different network appears or the device rejects the policy. Do not allow pressure to finish a call to become an approval. The AI does not press buttons, perform the final confirmation or declare something signed before you have verified it.
Practice
- Follow the workflow for your model with a wallet containing no funds or a lab that has passed physical acceptance testing.
- Simulate stopping before the final confirmations and explain why this does not constitute authorization.
- Check the returned response, its link to the draft and, on BIT, the receipt and acknowledgment status.
Show what you know
Describe the workflow without revealing credentials. Distinguish device approval, an imported response and a broadcast transaction.
Common question
Does an offline device know whether my inputs remain unspent? It cannot check current chain state on its own. The app must check the final transaction against its network source.
Pause point
If you interrupt signing, cancel or leave an identified pending transaction according to the workflow, with no secrets visible.
1. BIT signs but Desk does not confirm receipt. What status should you assume?
- The payment has definitely been broadcast.
- The response still needs to be received or validated. Resume the same operation.
- The wallet is lost.
Show answer
The response still needs to be received or validated. Resume the same operation.Signing, receiving and broadcasting are separate stages.
You can keep reading without an account. To share progress with TutorAI, activate a code.