THE CRYPTO FIELD GUIDEEDITION 001 / 07 OCT 2026Search the atlas ↗
MARKETSBTC——ETH——SOL——Indicative USD · Loading source
Bitcoin / Guide

A PSBT is a proposal: review it like one

Understand the separation between preparing, signing and broadcasting a Bitcoin transaction.

Bitcoin conceptual editorial illustration for A PSBT is a proposal: review it like one
Conceptual editorial illustration, not a photograph or measurement of an event.
THE TAKEAWAY

Offline signing protects key handling, but the signer still needs to verify the payment it authorises.

What the package contains

A partially signed Bitcoin transaction, or PSBT, packages a proposed transaction with information that participating wallets need to inspect and sign it. Different devices can prepare the proposal, add signatures and assemble the final transaction. The format supports that coordination; it is not an approval certificate. Receiving a file from a familiar coordinator does not establish that every output matches the payment you intended to make.

Reconcile a simple example

Imagine selected inputs total 0.030 BTC. The proposal pays a supplier 0.020 BTC, returns 0.0098 BTC as change and leaves 0.0002 BTC as the fee. Those amounts reconcile, but arithmetic alone is insufficient. The supplier address must match the independently confirmed destination, and the change output must belong to your wallet under the expected policy. A malicious destination can fit perfectly into a balanced transaction.

Keep the roles separate

An offline signing device can reduce exposure of secret keys to a networked computer. It cannot understand a business invoice unless someone verifies the displayed details against that invoice. For a shared treasury, one person might prepare a proposal while another checks the destination and a third reconciles the fee. This is an example workflow, not a required signature arrangement. The useful feature is independent review rather than several people repeating the same unchecked assumption.

Finish the evidence trail

After signing, distinguish a completed proposal from a broadcast transaction and from a confirmed payment. Keep an internal reference joining the invoice, approved proposal and resulting transaction identifier without publishing sensitive wallet metadata. Ask what your device can display, how it recognises change, which signature policy is being used and whether unexpected fields cause it to stop. If the display cannot explain the transaction, pause; the presence of an offline device does not make blind approval a sound process.

READ THE ORIGINAL EVIDENCE

Sources & context

  1. BIP 174: Partially Signed Bitcoin Transaction Format ↗

Sources checked 7 October 2026. This is explanatory coverage, not personalised investment advice. Our corrections policy.

CONTINUE EXPLORING

The next layer of context.

More Bitcoin