Sign in
Article On-chain

Bitcoin PSBT explained: how offline signing works

What a Bitcoin PSBT is, the six BIP 174 roles, offline signing steps, v0 vs. v2, and a Nov. 21, 2026 example: a 564-satoshi fee at a rate of 4 sat/vB.

Bitcoin PSBT explained: how offline signing works
Contents
  1. What a PSBT is and why Bitcoin needed it
  2. What is inside a PSBT file
  3. The six PSBT roles
  4. How offline PSBT signing works, step by step
  5. How a PSBT reaches the device: file, QR or cable
  6. A worked example for Nov. 21, 2026: what should add up on screen
  7. PSBT v0 vs. v2
  8. Common PSBT mistakes
  9. Limitations of the format
  10. FAQ

A Bitcoin PSBT (Partially Signed Bitcoin Transaction) is a standard file format for a transaction that is not finished yet. One file carries the unsigned transaction, the details of the coins it spends, and any signatures collected so far. That lets you build a transaction on an online computer, sign it on a device that never touches the internet, and broadcast it from somewhere else. Private keys never travel: a PSBT does not contain them.

This guide covers what is inside a PSBT, who does what at each step, how offline signing works in practice, how version 2 differs from version 0, and which checks you should never skip on the device screen.

What a PSBT is and why Bitcoin needed it

Before the standard existed, every wallet passed unsigned transactions around in its own way. BIP 174 names that as the motivation: people using different wallet software struggled to sign the same transaction. The second reason is offline devices. To sign a spend you need to know which coins are being spent and how much they are worth, and a hardware wallet has no copy of the blockchain. A PSBT carries that information along, so the signer, in the words of the spec, "can be offline."

BIP 174 was assigned on July 12, 2017, is authored by Ava Chow, and carries the status "Deployed." Bitcoin Core has had PSBT commands since version 0.17. The node documentation lists three typical uses: hardware wallets, multisig setups, and CoinJoin, where several participants build one transaction together.

You need a PSBT in three situations:

  • the key lives on a device that stays off the network (a cold wallet);
  • several signatures are required and different people or devices produce them (multisig);
  • the software that builds the transaction and the software that signs it come from different developers.

What is inside a PSBT file

Per the spec, a PSBT is a set of key-value maps: one global map, one per input, and one per output. The file starts with five magic bytes: the letters psbt followed by the separator 0xFF. There are two representations: a binary file with the .psbt extension and a Base64 string. The string is easy to spot because it begins with cHNidP8, which is how those first bytes encode.

A typical PSBT holds:

  • the unsigned transaction: which outputs are spent and where the coins go;
  • data about each input: the full previous transaction or just the output being spent, with its amount. Without the amount, nobody can compute the fee;
  • scripts and key derivation paths (BIP 32), which tell a device that an input or output belongs to its own wallet;
  • partial signatures, one added by each signer;
  • final scripts, which appear after finalization.

There are no private keys and no seed phrase in the file. A PSBT does reveal your addresses, amounts and the recipient, so it is not private. For background on inputs and outputs, see our guide to confirmations and UTXOs.

The six PSBT roles

BIP 174 describes the workflow through roles. One program can play several of them.

Role What it does Who it is in practice
Creator Creates a PSBT with the unsigned transaction and empty fields Coordinator wallet on a computer or phone
Updater Adds data about the coins being spent, scripts, key paths The same coordinator
Signer Checks the transaction and adds a partial signature Hardware wallet or offline computer
Combiner Merges several PSBTs of the same transaction into one Multisig coordinator
Finalizer Turns signatures into final scripts Coordinator
Extractor Outputs the finished transaction in network format Coordinator or node

The core rule for a signer in the spec: it uses only the coin data provided in the PSBT itself, it only adds data, and it adds no signature if it cannot sign. A combiner may merge only PSBTs of the same transaction; combining different ones is not allowed.

With a single signer there is no combiner. The coordinator creates and updates the file, the device signs, and the coordinator finalizes and broadcasts.

How offline PSBT signing works, step by step

The flow is the same for any pairing of coordinator software and signing device. The coordinator knows only public keys (a watch-only wallet), so it can see the balance but cannot spend.

  1. Build the transaction in the coordinator. Enter the recipient address, the amount and the fee rate. Our guide to mempool fees explains how to pick a rate.
  2. Save the unsigned PSBT as a file on a memory card or as a QR code on screen.
  3. Move the PSBT to the device. It is not connected to the internet and receives only this file.
  4. Check the device screen: recipient address, amount, change and fee. Compare them with what you meant to send, not with what the computer displays.
  5. Approve the signature. The device adds a partial signature to the PSBT and hands the file back.
  6. Move the signed PSBT back. If more signatures are needed, repeat steps 3 to 5 on the other devices, either in sequence or in parallel with a merge afterward.
  7. Finalize and broadcast. The coordinator assembles the finished transaction and sends it to the network.

In Bitcoin Core the same steps map to commands described in the node documentation: walletcreatefundedpsbt creates and updates a PSBT, walletprocesspsbt updates and signs, combinepsbt merges, finalizepsbt finalizes and extracts the transaction, and sendrawtransaction broadcasts it. decodepsbt prints the contents in readable form, and analyzepsbt reports the next step and computes the fee.

How a PSBT reaches the device: file, QR or cable

The format does not depend on the transport. The same content travels over any channel.

Channel What it looks like Trade-off
Memory card A .psbt file carried there and back The device never touches the computer directly, but you need a card and two trips
QR codes The coordinator shows a code, the device scans it with a camera, then the reverse A large transaction does not fit in one code and needs a sequence of frames
USB or NFC The coordinator hands the PSBT to the device directly Faster, but the device is linked to the computer

Two open formats exist for QR sequences: UR from Blockchain Commons and BBQr from Coinkite. Both split a file into parts and cycle through them. The BBQr README says its compression option typically cuts file size by about 30%. Before buying a device, check which of the two formats both the device and your coordinator understand.

A worked example for Nov. 21, 2026: what should add up on screen

Take the simplest transaction: one input from a native SegWit address (bc1q…) and two outputs, one to the recipient and one back to yourself as change. The Bitcoin Optech size calculator puts it at 140.5 virtual bytes, which wallets round up to 141.

On Nov. 21, 2026, at about 1:06 PM ET, mempool.space recommended 4 sat/vB for next-block confirmation, and bitcoin traded near $60,073 as of 1:00 PM ET (our data, see the dashboard). That gives:

  • input: 0.08000000 BTC;
  • to the recipient: 0.05000000 BTC (about $3,004);
  • fee: 141 × 4 = 564 satoshis, or 0.00000564 BTC (about $0.34);
  • change: 0.08 − 0.05 − 0.00000564 = 0.02999436 BTC.

The device should display exactly those three numbers: the amount to the recipient, the change marked as your own address, and the fee. It computes the fee as inputs minus outputs. If the screen shows a fee many times larger, or lists the change as a second outside recipient, do not sign. For the live price and network state, see the Bitcoin page.

PSBT v0 vs. v2

Version 0 stores the unsigned transaction as one fixed blob. BIP 370, assigned on Jan. 14, 2021, calls that a limitation: new inputs and outputs cannot be added to such a transaction. Version 2 drops the global blob and stores each transaction field separately. There is no version 1, as Bitcoin Optech notes.

PSBT v0 (BIP 174) PSBT v2 (BIP 370)
Where the transaction lives One blob in the global map Separate fields per input and output
Adding inputs and outputs Not possible Possible while the modifiable flags allow it
Support Practically every PSBT-capable wallet Depends on software and firmware

Taproot fields were added to both versions by BIP 371.

Version compatibility is a practical issue. Bitcoin Core gained PSBT v2 support in May 2026 (Optech, May 8, 2026). Bitcoin Core 32.1 then began exporting unsigned transactions from the GUI as version 2, and tools that only knew version 0 could not sign them. The change was reverted: according to the Optech newsletter of Nov. 6, 2026, the GUI exports version 0 again, while the external-signer workflow configured with -signer stays on version 2 and needs HWI 2.1.0 or later. The takeaway: if a device refuses to read a file, check the PSBT version and your software updates first.

Common PSBT mistakes

  • Trusting the computer screen. The point of offline signing is that you decide based on the device screen. An infected computer can display anything.
  • Signing again "because of an error." In 2020 an attack on multi-input SegWit transactions was publicly dissected: compromised software understates the amount of one input, then of another, asks you to sign twice under the pretext of a glitch, and assembles a transaction with a huge fee. Bitcoin Optech described it on June 10, 2020 and noted that Greg Sanders had outlined the scheme back in 2017. Coinkite wrote that the attacker does not receive the coins directly; they go to miners. Since then many wallets require the full previous transaction in the PSBT even for SegWit inputs, and BIP 174 allows a signer to refuse if it is missing. Taproot closed the hole at the protocol level: under BIP 341 the signature commits to the amounts of all inputs.
  • Skipping the change check. A device recognizes its own change address from the key paths in the PSBT. If change shows up as an ordinary recipient, either the coordinator did not include that data or the address is not yours.
  • Treating the file as safe to share with anyone. It holds no keys, but it does hold your addresses, amounts and extended public keys.
  • Forgetting the fee during slow signing. The fee rate is fixed when the PSBT is created. If a multisig takes days to collect signatures, the rate may be too low by the time you broadcast.
  • Mixing versions. Software that only knows v0 will not read a v2 file.

Limitations of the format

A PSBT does not protect you from the signing device itself. The device picks the random number used in a signature, and compromised firmware could in theory use that to leak the key. In November 2026 the developer mailing list discussed a draft standard with three new PSBT fields for this kind of protection; its author, Connor Avila, specifically asked for review because the proposal's cryptography had not been audited (Optech, Nov. 13, 2026).

The format also cannot tell whether the recipient address is the right one. If you pasted a swapped address, the device will show it faithfully and the transaction will go through. And it does not replace a backup: losing your seed phrase still means losing access.

FAQ

Can someone steal my bitcoin by intercepting a PSBT? No. The file contains no private keys. An interceptor sees addresses and amounts, and can at most broadcast a signed transaction exactly as you signed it.

Do I need PSBTs if I use one hardware wallet over USB? You probably already do: many wallet apps talk to the device in this format, you just never see the file. Moving a PSBT by hand comes up when you work without a cable or use multisig.

How long does an unsigned PSBT stay valid? The file has no expiry date. It stops working once any coin it references is spent by another transaction. In practice the fee rate goes stale first.

How is a PSBT different from a raw hex transaction? A raw transaction contains only what goes to the network. A PSBT adds what is needed to verify and sign it offline: input amounts, scripts, key paths and intermediate signatures.

This is not investment advice.

Morning brief and news on TelegramEvery morning at 9:00 AM ET, before the US open: price, 24h scenario, squeeze risk. Key news around the clock.
Coins
Category
Tags
#PSBT#cold storage#multisig#hardware wallet#BIP 174
Ryan Mitchell
On-chain and mining

Breaks down blockchain and mining data: hashrate, difficulty, holder and whale behavior.

Comments

Read next