Offline transaction signing

Separate preparation from authorization

The online side needs enough wallet information to discover outputs and prepare a transaction. The offline side stores the secret required to authorize spending. A watch-only wallet cannot simply manufacture that authorization itself.

Wallets provide export and import steps to move the required information between the two sides. Output and key-image synchronization can matter for accurate spent status. Follow one supported wallet workflow rather than mixing file formats from unrelated applications.

References: Feather: offline transaction signing · Wallet RPC reference

A signed transaction can be broadcast

Once a valid transaction has been signed, an online party can submit that transaction without receiving the private spend key. Signing authorizes that payment even if the offline device never connects to a node.

Back up recovery material outside the signing device in case of hardware failure or theft, and verify that you recorded it correctly.

References: Feather: offline transaction signing · Wallet RPC reference

Example

In Feather, an online view-only wallet prepares a payment. The offline wallet reviews and signs it, and the online wallet receives the signed data for submission. The workflow can use supported QR transfers or files.

References: Feather: offline transaction signing · Wallet RPC reference

Limits and cautions

Offline signing does not make the online wallet trustworthy. Verify the destination, amount and fee on the signing side. Transfer media and QR data remain untrusted inputs, and an offline spend key does not hide the online device's network activity.

References: Feather: offline transaction signing · Wallet RPC reference