Six roles, one file
Who handles a bitcoin payment before it reaches the network? BIP 174, the specification behind the format, splits the work into roles. Bitcoin Core’s PSBT guide says the node software has offered a PSBT interface since version 0.17 and names the command that plays each part.
| Role | Job under BIP 174 | Bitcoin Core command |
|---|---|---|
| Creator | Puts an unsigned transaction into a new PSBT | createpsbt, converttopsbt |
| Updater | Adds the coins being spent, scripts and key paths | utxoupdatepsbt, walletprocesspsbt |
| Signer | Checks the data and adds a partial signature | walletprocesspsbt |
| Combiner | Merges copies of the same PSBT | combinepsbt |
| Input finalizer | Turns partial signatures into final scripts | finalizepsbt |
| Transaction extractor | Builds the transaction the network accepts | finalizepsbt |
One program usually plays several roles, and walletcreatefundedpsbt is creator and updater at once. Bitcoin Core’s guide says combinepsbt is useful for merging the output of several signers, which is what a multisig wallet needs when each co-signer returns a separate copy. BIP 174 adds that a combiner can do this without understanding the scripts inside.
Version 2 is now Bitcoin Core’s default
The first format froze the transaction at creation, so nobody could add an input or an output afterward. BIP 370, assigned on January 14, 2021 and now marked as deployed, removes that limit with a new constructor role. It skips the number 1 because people had already been calling the original format version 1.
Bitcoin Core 32.1, published on October 27, 2026, switched createpsbt, walletcreatefundedpsbt, converttopsbt and psbtbumpfee to version 2 by default. A new psbt_version argument picks the version. The notes add that 32.0, although tagged, was never fully released.
Where you see one
Sparrow’s Coldcard guide, written for a device kept offline, has you click “Save PSBT,” carry the .psbt file over on a microSD card, check the address and amount on the device, and load back a signed file with a name like “First Send-signed.psbt.”
Pasted as text, a PSBT is Base64 and begins with cHNidP8. Those characters encode the file’s first bytes, the letters psbt followed by the byte 0xFF. We checked the 95 test vectors in the two specifications on November 19, 2026, and 94 begin that way. The exception is a BIP 174 case built to fail because it is an ordinary network transaction.
What to watch for
The two versions don’t read each other. BIP 370 calls the incompatibility intentional and says a version 2 file can be converted back. If a signer that knows only version 0 rejects a file from Bitcoin Core 32.1, the psbt_version argument can ask for the older format.
The second trap is older. BIP 174 describes a flaw in the segwit signing algorithm, BIP 143, through which an attacker who gets a user to sign a malicious transaction more than once can send bitcoin to fees. Many wallets therefore demand the full previous transaction, which the specification calls the non-witness UTXO.
For a Trezor that answers “user refused” or stops responding to a PSBT, BTCPay Server’s wallet FAQ gives a matching fix, the setting “Always include non-witness UTXO if available.” Whatever the version, read the amount, the address and the fee on the hardware wallet screen before you approve.