CuvexACADEMY

M09 · Edition 0.1

Coordinating signatures and broadcasting a multisignature transaction

Free · no registration

Objective

Bring a proposal to its signing threshold without losing sight of intent or control.

Understanding the topic

A multisignature operation specifies inputs, recipients, amounts, fee rate, replacement behavior and operational notes. The creator can request signatures from compatible participants. Each signer independently reviews network, policy, inputs, every output and the fee before authorizing on their own device.

A partial signature alone does not move funds if the threshold is unmet. Once it is met, the coordinator can combine signatures and finalize according to the workflow. Reports from other participants or the coordinator are coordination information. They are distinct from checks you carried out locally, and the app should identify their sources.

The reviewed implementation supports retrying, receiving and acknowledging signatures, rejection and handover of coordination. Handover changes neither the keys nor the on-chain threshold. Correlate a saved response with its request and the actual profile used. Never choose a different policy because it looks similar or appears first in the catalog.

If someone changes recipients or other relevant conditions, review a new proposal and obtain the appropriate signatures. Never manually delete security data from a PSBT to make it fit on NFC. The firmware requires supported profiles and validations and sets limits on inputs, outputs and size.

Before broadcasting, verify that this is the agreed transaction and that no version has already been broadcast. Then track confirmations through your chosen source. Rejecting in your app does not automatically revoke signatures others retained or prevent every action still allowed by the remaining threshold.

Practice

  1. Act out a 2-of-3 scenario with three fictitious roles. One signs, another rejects and the third asks for clarification.
  2. Change the test payment’s address and explain why an earlier verbal approval cannot be reused.
  3. Simulate a failed acknowledgment after saving a signature. Resume the same job without duplicating the payment or switching profiles.

Show what you know

Identify who coordinates, signs and finalizes, and the evidence for each stage.

Common question

Do two “OK” messages in chat count as two signatures? No. The threshold requires valid cryptographic authorizations under the policy.

Pause point

Record the status, pending signatures and next responsible person, excluding private contents.

1. A 2-of-3 transaction has one valid signature and two messages saying “I agree.” Has it met the threshold?

  1. Yes, because three people participated.
  2. No. It still needs another valid cryptographic signature.
  3. Yes, if the coordinator announces it.
Show answerNo. It still needs another valid cryptographic signature.

Agreement in conversation and a valid signature are different kinds of evidence.

Download PDF ↗

You can keep reading without an account. To share progress with TutorAI, activate a code.