A laptop, transaction receipt and hourglass for investigating a delayed payment, editorial illustration
BIP 370 / TRANSACTIONS

PSBT, version two.

PSBT v2 stores transaction pieces in input and output maps rather than a single global unsigned transaction.

Read the explanation
← All standards

Why it exists

BIP 370 defines PSBT version 2. It changes how a signing package represents the transaction so that construction can happen incrementally. This is useful when different participants contribute inputs or outputs, rather than receiving one complete unsigned transaction at the outset. The version describes the PSBT envelope, not the Bitcoin transaction version.

How it works

PSBT v0 places one unsigned transaction in a global field. Version 2 removes that field and distributes the pieces: global transaction version and counts, input outpoints and sequences, and output amounts and scripts. A constructor can add pieces while the package permits modification.

Modifiable flags describe whether inputs or outputs may still change and whether SIGHASH_SINGLE pairing needs attention. Signers update these flags according to their signatures. The format also defines how required input locktimes produce the final transaction locktime. Extraction assembles an ordinary Bitcoin transaction from the component fields.

PUT IT IN CONTEXT

A practical example

Two participants could begin with an empty version-2 package, add their agreed funding inputs and destination outputs, and then send it for approval. Once a signature commits to all inputs and outputs, the package must no longer advertise that those pieces can freely change. Adding a recipient afterwards is not a harmless metadata edit; it changes what was signed.

What to keep in mind

V0 and v2 are not interchangeable just because both are called PSBT. Conversion requires reconstructing or distributing transaction data. Every participant needs the appropriate format support, and modifiable flags do not grant permission to change someone else’s payment.

Status & implementation

The repository marks BIP 370 Deployed and links a reference implementation. That label does not establish support in every coordinator or signing device; check the precise exported PSBT version.

Specification status: Deployed · Sources checked 13 November 2026

Read the sources

Put the standard in context.

Explore the practical guide

Find your next answer.

Search the complete field guide · Esc to close