Bitcoin developers have reversed a wallet-interface change that could stop an otherwise healthy hardware wallet from signing a transaction. On November 4, 2026, pull request Bitcoin Core #36539 was merged, restoring Partially Signed Bitcoin Transaction version 0 (PSBTv0) for common graphical-wallet exports. The goal is compatibility, not a rollback of Bitcoin’s consensus rules or a new way to generate keys.
Bitcoin Core 32.1, released in October, introduced PSBT version 2 as the default for several interfaces. Devices and applications that understood only the older PSBTv0 format could reject the resulting files even when every address, amount and signature requirement was otherwise valid. Bitcoin Optech’s November 6 technical newsletter documented the merged repair and the important exception for external signing.
Video context: Satoshi Radio Global’s May 2025 COLDCARD Q tutorial demonstrates PSBT-based offline signing, beginning at approximately 21:40. Historical education, not footage of Bitcoin Core’s November code change.
Why Bitcoin wallets exchange PSBT files
A PSBT is a container for an unfinished Bitcoin transaction and the information needed to sign it. One computer can prepare the destinations and mining fee, then an offline hardware wallet can inspect and sign without exposing its private key to the online computer. The signed data returns for finalization and broadcast. Multisignature wallets may circulate the same transaction among several signing devices.
The original BIP174 format stores a complete unsigned transaction in one global field. The newer BIP370 PSBTv2 format represents inputs, outputs and transaction metadata separately. That makes it easier for cooperating tools to build or modify a transaction in stages. Both formats are useful; a signer still needs to understand the version it receives.
What Bitcoin Core actually changed
The merge restores PSBTv0 exports for two ordinary graphical-wallet workflows: creating an unsigned payment and preparing a fee-bump transaction. Those are common paths for watch-only wallets whose keys live elsewhere. Before the repair, a PSBTv0-only signer could fail to process the file, interrupting payment preparation. The merge targets the development branch; users should not assume an already-installed 32.1 binary contains a patch merged afterward.
Important exception: Bitcoin Core’s external-signer workflow configured with -signer continues to use PSBTv2. Bitcoin Optech identifies Hardware Wallet Interface (HWI) version 2.1.0 or later as a compatible option. Bitcoin Core’s separate RPCs also defaulted to PSBTv2 in 32.1, so developers integrating those APIs need to check the expected PSBT version rather than assuming the graphical-wallet choice applies everywhere.
Video context: Right Shift’s February 2025 Sparrow Wallet demonstration covers constructing, signing and broadcasting a PSBT, including a walkthrough near 23:25. The video predates the compatibility repair.
Why compatibility matters for self-custody
A failed import is not evidence that a private key has been lost, and PSBTv2 is not inherently insecure. The risk is operational: a user may be unable to complete a time-sensitive payment or replace a stuck transaction until the signing software agrees on a format. Users should preserve wallet backups, verify destination addresses and transaction fees on the signer, and avoid improvising with recovery phrases merely to bypass a file-format error.
Recent BitcoinVersus.Tech coverage provides related context: Bitcoin Core 32.1’s broader upgrades, COLDCARD firmware and PSBTv2 handling, proposed anti-exfiltration signing, and Liana’s Taproot and backup update. Each improvement solves a different part of the self-custody workflow.
For Bitcoin Core developers, the lesson is that format upgrades require a transition plan across independently maintained wallets. PSBTv2 remains a supported, forward-looking standard; preserving PSBTv0 in familiar GUI paths can help users adopt newer tooling without disrupting existing signers.
Sources and editorial verification
- Bitcoin Core PR #36539, merged November 4, 2026; code review and scope of GUI changes.
- Bitcoin Optech Newsletter #430, November 6, 2026; compatible and incompatible signer workflows.
- Official Bitcoin Core 32.1 release notes, PSBTv2 defaults and release context.
- BIP174 and BIP370, specification documents.
Editorial note: The oil-painting cover is a conceptual illustration, not a photograph of Bitcoin Core’s interface or an actual signing session. Both embedded videos are older educational material. BitcoinVersus.Tech has not independently tested the patch on production wallet hardware.
We volunteer daily to ensure the credibility of the information on this platform is Verifiably True. If you would like to support to help further secure the integrity of our research initiative, please scan the QR code below.


Leave a Reply