Skip to the content
nullroute
Browse the docs

Signing a transaction

The review shows where the money goes, which outputs leave the wallet and which are change, the fee in three forms, and a multisig transaction's signatures so far.

A blocking warning refuses the signature, with the reason beside the button. Signing past one takes an explicit tick for that signature alone, which is not remembered.

Signatures are deterministic: RFC 6979 for ECDSA, BIP-340 with aux_rand fixed to 32 zero bytes for Schnorr. Anyone with the seed can recompute the identical bytes and confirm nothing was hidden in them.

After signing, the screen says where it goes next: the next cosigner, or whatever will broadcast a complete transaction. Nothing is broadcast here; the device has no network.

Rendered from docs/USING.md, the same bytes that ship with the code. SHA-256 b735aa55a6ae5cc7682c2b90fe2c551b3a396a02240f45936d50e6540d65a989