If you hold your own keys, you already understand something most people never will: sovereignty demands technical competence. Partially Signed Bitcoin Transactions (PSBTs) are one of the most powerful tools in the self-custody toolkit, and yet most Bitcoiners have never used one. That changes today.
PSBTs let you build, pass around, and sign Bitcoin transactions across multiple devices, wallets, and even air-gapped hardware, without ever exposing a single private key to the internet. They are the backbone of multi-signature setups, collaborative custody, CoinJoin privacy transactions, and hardware wallet workflows. If you run a home mining operation, manage cold storage for your stack, or simply refuse to trust a third party with your sats, PSBTs are essential knowledge.
This guide breaks down exactly how PSBTs work, why they exist, how to use them, and why every serious Bitcoiner should master them in 2026.
What Is a Partially Signed Bitcoin Transaction?
A Partially Signed Bitcoin Transaction (PSBT) is a standardized data format, defined in BIP 174, that allows a Bitcoin transaction to be constructed incrementally and signed by multiple parties or devices before being finalized and broadcast to the network.
In a standard Bitcoin transaction, you build the transaction and sign it in one step, usually on a single device. The problem? That device needs access to your private keys. If that device is connected to the internet, your keys are exposed, even if only briefly, to every piece of malware, keylogger, and remote exploit running on that machine.
PSBTs solve this by separating the transaction into stages:
- Creation — Build the unsigned transaction (inputs, outputs, amounts) on any device.
- Signing — Pass the PSBT to one or more signing devices (hardware wallets, air-gapped machines) where private keys live. Each signer adds their signature without seeing anyone else’s keys.
- Finalization — Once all required signatures are collected, combine them into a fully signed transaction.
- Broadcast — Push the complete transaction to the Bitcoin network from any connected device.
The private keys never leave the signing device. The unsigned transaction travels; the keys do not. This is how sovereignty-preserving Bitcoin infrastructure should work.
Why PSBTs Exist: The Problem They Solve
Before BIP 174, there was no universal format for passing around partially constructed transactions. Every wallet had its own proprietary method. If you wanted to use a Coldcard to sign a transaction initiated in Electrum, you were at the mercy of whatever custom format each tool supported. Multi-signature setups, where two or three keys must sign before a transaction is valid, were a nightmare of incompatibility.
Andrew Chow authored BIP 174 in 2017 to fix this. The proposal defined a single, standardized container format that any wallet, any hardware signer, and any software could understand. A PSBT file carries everything a signer needs to verify and sign a transaction:
- The unsigned transaction itself (inputs and outputs)
- UTXO data for each input (so the signer can verify amounts without querying the blockchain)
- Redeem scripts and witness scripts for complex spending conditions
- BIP 32 derivation paths (so hardware wallets know which key to use)
- Partial signatures from previous signers
This standardization was a breakthrough. It meant a Trezor, a Coldcard, a Ledger, a Specter Desktop instance, and Bitcoin Core could all participate in the same transaction workflow without any of them needing to know about the others’ internal implementations.
BIP 370: PSBT Version 2
The original PSBT format (version 0) required the full unsigned transaction to be included in the PSBT from the start. This worked, but it limited flexibility. You could not easily add inputs or outputs to a PSBT after creation, which was a problem for collaborative protocols like CoinJoin, where participants contribute inputs and outputs at different times.
BIP 370 introduced PSBT version 2, which decouples the inputs and outputs from a monolithic transaction structure. Each input and output is stored separately, making it possible to add or modify them independently. This is a significant improvement for privacy protocols, Lightning Network channel opens, and any workflow where the transaction is built collaboratively.
How PSBTs Work: A Technical Walkthrough
Let us walk through the entire PSBT lifecycle from creation to broadcast. We will use a multi-signature scenario because that is where PSBTs deliver the most value.
Scenario: 2-of-3 Multi-Sig Cold Storage
You have a 2-of-3 multi-signature wallet protecting your mining rewards. The three keys are held on: (1) a Coldcard stored in a safe, (2) a Trezor in your desk, and (3) a seed backup on steel plates in a separate location. Any two of three keys must sign to spend.
Step 1: Create the Unsigned Transaction
On your watch-only wallet (Sparrow, Electrum, or Specter Desktop), you create a transaction spending from the multi-sig address. This wallet has the public keys and can construct valid transaction templates, but it holds no private keys. The output is a .psbt file containing:
- The unsigned transaction with specified inputs and outputs
- UTXO information for each input
- The multi-sig redeem script
- BIP 32 derivation paths for all three keys
Step 2: First Signature (Coldcard)
You transfer the .psbt file to your Coldcard via microSD card. The Coldcard is air-gapped; it has never been connected to the internet. It reads the PSBT, displays the transaction details on its screen (destination address, amount, fee), and you verify everything looks correct. You approve, and the Coldcard adds its partial signature to the PSBT file. The file is saved back to the microSD card.
At this point, the PSBT contains one of the two required signatures.
Step 3: Second Signature (Trezor)
You plug in your Trezor and import the partially signed PSBT via Sparrow or Electrum. The Trezor verifies the transaction details on its own screen. You confirm, and the Trezor adds its signature. The PSBT now has both required signatures.
Step 4: Finalize and Broadcast
Your watch-only wallet detects that the PSBT has the required number of signatures (2 of 3). It finalizes the PSBT, converting it into a standard Bitcoin transaction, and broadcasts it to the network. The transaction enters the mempool and will be confirmed in a block.
At no point did any private key touch an internet-connected device. At no point did any single device have access to more than one key. That is the power of PSBTs.
PSBT Use Cases Every Bitcoiner Should Know
Multi-Signature Custody
Multi-sig is the gold standard for securing serious amounts of bitcoin. With the block reward at 3.125 BTC and network hashrate exceeding 800 EH/s, home miners accumulating sats from solo mining operations using Bitaxe devices need robust custody. A 2-of-3 or 3-of-5 multi-sig setup, powered by PSBTs, ensures no single device compromise can drain your wallet.
If you are stacking sats from your mining operation, even a modest setup with Bitcoin space heaters generating heat and hash, you should graduate to multi-sig custody as your stack grows.
CoinJoin and Collaborative Transactions
CoinJoin transactions combine inputs and outputs from multiple participants into a single transaction, breaking the chain of ownership visible on the blockchain. PSBTs make this possible by letting each participant sign their own inputs independently. Protocols like JoinMarket and collaborative Payjoin implementations rely on PSBTs to coordinate these privacy-enhancing transactions.
Privacy is not optional for cypherpunks. It is a fundamental property of sound money. PSBTs are the technical plumbing that makes on-chain privacy practical.
Air-Gapped Hardware Wallet Signing
Even if you run a simple single-signature wallet, PSBTs improve your security posture dramatically. Instead of signing transactions on a hot wallet or a hardware wallet connected via USB (where the host computer could theoretically manipulate the transaction before it reaches the device), you can:
- Build the transaction on your watch-only wallet
- Export the PSBT to a microSD card or QR code
- Sign on a completely air-gapped device (Coldcard, SeedSigner, Passport)
- Import the signed PSBT back and broadcast
No USB connection to the signing device means no USB-based attack vectors. Pure separation of concerns.
Inheritance and Estate Planning
PSBTs enable sophisticated inheritance setups. You can pre-create transactions that your heirs can complete with their keys after a time-locked condition is met. Combined with multi-sig and timelocks, PSBTs make it possible to create dead-man’s switch arrangements that protect your bitcoin across generations, without trusting any custodian or lawyer with your keys.
Collaborative Mining Pool Payouts
Some mining pool implementations use PSBTs for payout batching, where the pool operator creates a large payout transaction and participants can verify their outputs before the transaction is finalized. This adds a layer of transparency and verification that traditional pool payout methods lack.
Tools and Wallets That Support PSBTs
The PSBT ecosystem has matured significantly since BIP 174’s introduction. Here are the tools that every sovereign Bitcoiner should know about:
Hardware Wallets
| Device | PSBT Method | Air-Gap Capable | Notes |
|---|---|---|---|
| Coldcard Mk4 / Q | MicroSD, NFC | Yes (fully) | Gold standard for air-gapped signing. Multi-sig native. |
| SeedSigner | QR codes | Yes (fully) | Open-source, DIY, stateless. No persistent storage of keys. |
| Foundation Passport | QR codes, MicroSD | Yes (fully) | Open-source firmware. Excellent UX for PSBTs. |
| Trezor Model T / Safe | USB | No | Solid PSBT support via Sparrow/Electrum. USB-connected. |
| Ledger Nano S+ / X | USB, Bluetooth | No | PSBT support through companion software. Closed-source firmware. |
| Jade | QR codes, USB, Bluetooth | Yes (QR mode) | Open-source. Virtual air-gap via QR. Affordable entry point. |
Desktop Software
| Software | PSBT Features | Best For |
|---|---|---|
| Sparrow Wallet | Full PSBT lifecycle, multi-sig coordinator, UTXO management | Power users. The best all-around Bitcoin wallet for PSBT workflows. |
| Specter Desktop | Multi-sig coordinator, hardware wallet integration | Multi-sig setups with multiple hardware wallets. |
| Electrum | PSBT creation, signing, multi-sig | Experienced users comfortable with a feature-rich interface. |
| Bitcoin Core | Full PSBT RPC commands (createpsbt, walletprocesspsbt, finalizepsbt) | Node operators and developers who want direct RPC control. |
Command-Line PSBT with Bitcoin Core
For those who prefer the terminal (and if you are reading this on D-Central, there is a good chance you do), Bitcoin Core provides full PSBT support via RPC commands:
walletcreatefundedpsbt— Create a funded PSBT from wallet UTXOswalletprocesspsbt— Sign a PSBT with the wallet’s keyscombinepsbt— Merge multiple PSBTs with different signaturesfinalizepsbt— Complete a fully signed PSBT into a broadcastable transactionsendrawtransaction— Broadcast the final transactiondecodepsbt— Inspect a PSBT’s contents (inputs, outputs, signatures, scripts)
If you run your own Bitcoin node (and you should), these commands give you complete, sovereign control over your transaction workflow.
PSBTs and Home Mining: Why This Matters to You
If you mine bitcoin at home, whether with a Bitaxe solo miner on your desk or a full Bitcoin space heater warming your basement, you are accumulating sats. How you custody those sats matters just as much as how you mine them.
Consider the home miner’s workflow:
- Mining — Your ASIC or open-source miner generates hash. If you are solo mining, every hash is a ticket to a 3.125 BTC block reward. If you are pool mining, rewards trickle into your payout address.
- Accumulation — Sats build up in your hot wallet or pool account.
- Cold Storage — You periodically sweep accumulated sats into cold storage using a PSBT-enabled workflow: create the transaction on your watch-only wallet, sign with your air-gapped hardware wallet, broadcast.
- Long-Term Custody — Your stack sits in a multi-sig arrangement. If you ever need to spend, you use PSBTs to coordinate signatures across your distributed keys.
This workflow is the sovereign miner’s standard operating procedure. No exchange. No custodian. No third party. Just you, your hardware, and your keys.
Need help getting your mining operation dialed in? D-Central offers mining consulting to help home miners optimize their setups, from hardware selection to custody architecture. And if your ASIC is acting up, our ASIC repair service has fixed thousands of machines since 2016.
Security Best Practices for PSBT Workflows
PSBTs are only as secure as your operational discipline. Here are the practices that matter:
Always Verify on the Signing Device
Never trust the transaction details displayed on your computer screen. Always verify the destination address, amount, and fee on the hardware wallet’s own display. A compromised computer could display a legitimate-looking transaction while the actual PSBT sends your bitcoin to an attacker’s address. The hardware wallet’s screen is your last line of defense.
Use Air-Gapped Signing When Possible
USB connections introduce attack surface. QR code and microSD-based PSBT transfer methods eliminate the USB vector entirely. Devices like the Coldcard, SeedSigner, and Foundation Passport were designed for this workflow. Use them as intended.
Verify the PSBT Before Signing
Use decodepsbt in Bitcoin Core or the transaction inspector in Sparrow to examine the raw PSBT before loading it onto your signing device. Check that:
- The outputs match your intended destinations
- The fee is reasonable (not abnormally high, which could indicate a fee-siphoning attack)
- The change output returns to an address you control
- The input UTXOs are correct
Test with Small Amounts First
When setting up a new multi-sig wallet or trying a new PSBT workflow for the first time, always test with a small amount. Verify the entire round-trip: create, sign, finalize, broadcast, confirm. Only after confirming the workflow works correctly should you use it for significant amounts.
Maintain Redundant Backups
In a multi-sig setup, the loss of too many keys means loss of funds. Ensure your key backups (seed phrases on steel plates, for example) are distributed geographically. The PSBT workflow protects your keys during transaction signing, but it cannot protect against physical loss of backup material.
PSBTs and the Future of Bitcoin Sovereignty
As Bitcoin’s network hashrate pushes past 800 EH/s and difficulty climbs above 110T, the network is more secure and more competitive than ever. But network-level security means nothing if individual Bitcoiners do not practice self-custody with the same rigor.
PSBTs are not just a technical convenience. They are a sovereignty tool. They make it practical to:
- Eliminate single points of failure in custody (multi-sig)
- Keep private keys permanently offline (air-gapped signing)
- Coordinate complex transactions without trusting intermediaries
- Maintain on-chain privacy through collaborative protocols
- Build inheritance plans that do not depend on custodians
The cypherpunk ethos that Bitcoin was built on demands that we take personal responsibility for our security. PSBTs give us the tools to do it properly.
If you are building out your home mining operation and want to pair it with proper self-custody, start with the hardware. Check out D-Central’s full range of mining equipment, from open-source Bitaxe solo miners to industrial ASICs. If you want hands-on training to understand Bitcoin from the hardware level up, we offer mining training that covers everything from ASIC fundamentals to advanced operational security. And for miners who need reliable infrastructure, our Quebec hosting facility provides enterprise-grade power and cooling in one of the best mining jurisdictions on Earth.
Frequently Asked Questions
What exactly is a PSBT?
A Partially Signed Bitcoin Transaction (PSBT) is a standardized format defined in BIP 174 that allows Bitcoin transactions to be created, passed between devices, signed by multiple parties, and broadcast, all without exposing private keys to internet-connected devices. It separates transaction construction from transaction signing, which is fundamental to secure Bitcoin self-custody.
Why should I use PSBTs instead of regular transactions?
Regular transactions require your private keys to be on the same device that constructs and broadcasts the transaction. PSBTs eliminate this requirement. You can build the transaction on a hot machine, sign it on an air-gapped hardware wallet, and broadcast from any connected device. This dramatically reduces the attack surface for key theft, especially important as your bitcoin stack grows from mining.
Do I need PSBTs if I only have a single-signature wallet?
Yes. Even with a single-signature setup, PSBTs improve security by enabling air-gapped signing via QR codes or microSD cards. Instead of connecting your hardware wallet via USB to a potentially compromised computer, you transfer only the unsigned transaction data, sign offline, and return the signed PSBT. No USB attack vector.
Which hardware wallets support PSBTs?
Most modern hardware wallets support PSBTs. Coldcard, SeedSigner, Foundation Passport, and Blockstream Jade support full air-gapped PSBT workflows via microSD or QR codes. Trezor and Ledger support PSBTs through USB connections with compatible desktop wallets like Sparrow and Electrum.
What is the difference between PSBT version 0 and version 2?
PSBT version 0 (BIP 174) requires the full unsigned transaction to be present from the start. Version 2 (BIP 370) stores inputs and outputs separately, allowing them to be added or modified after creation. This makes version 2 better for collaborative protocols like CoinJoin and Lightning channel opens where the transaction is built incrementally by multiple parties.
Can PSBTs be used for CoinJoin privacy transactions?
Absolutely. CoinJoin protocols rely on PSBTs to let multiple participants contribute inputs and outputs to a joint transaction. Each participant signs only their own inputs, and the combined transaction obscures the link between senders and receivers. PSBT version 2 improves this workflow further by allowing inputs and outputs to be added incrementally.
How do PSBTs relate to Bitcoin mining and self-custody?
Home miners accumulate bitcoin through mining rewards. PSBTs enable those miners to move their rewards into secure cold storage using air-gapped signing, and to protect larger stacks with multi-signature wallets that require PSBTs for spending. The mining-to-custody pipeline, mine, accumulate, sweep to cold storage, spend via multi-sig, is built on PSBTs at every custody transition point.
Is it difficult to learn how to use PSBTs?
The basic workflow is straightforward: create a transaction in your wallet software, export the PSBT file, sign it on your hardware wallet, import the signed PSBT, and broadcast. Wallet software like Sparrow makes this process intuitive with guided interfaces. Start with small test transactions to build confidence before moving larger amounts.




