Why it exists
BIP 174 defines Partially Signed Bitcoin Transactions, or PSBTs: a portable package that lets a wallet prepare a payment while another device holds the signing keys. It also lets several signers contribute to the same transaction without sharing their private keys. The package is working material, not a transaction ready for the Bitcoin network.
How it works
A PSBT contains transaction details alongside information about its inputs and outputs. That can include previous outputs, scripts, key origins and partial signatures. These extra fields help a signer understand which keys are needed, identify its change and check the proposed payment.
The specification separates jobs: a creator prepares the package; an updater supplies missing information; signers add signatures; a combiner merges compatible contributions; a finalizer constructs the unlocking data; and an extractor produces the network transaction. One application may perform several jobs. Private keys are not a required part of the exchange.
A practical example
Imagine spending a 0.01000000 BTC output to pay 0.00300000 BTC. The wallet proposes 0.00699000 BTC in change, leaving 0.00001000 BTC, or 1,000 sats, as the fee. A signing device should independently show the recipient, payment and fee before approval. In a 2-of-3 wallet, two appropriate signatures satisfy the policy; the desktop wallet can then finalize and broadcast.
What to keep in mind
A PSBT may reveal balances, public keys and wallet structure. Treat an incoming package as untrusted, and verify recipient and change information. A valid signature does not prove that a payment matches your intention, and signing alone does not broadcast it.
Status & implementation
Bitcoin Core has provided PSBT RPCs since 0.17.0. This is an application format; signer compatibility still depends on script type and supported PSBT fields.
Specification status: Deployed · Sources checked 13 November 2026
