Bitcoin Core 32.0 has introduced a compatibility problem that may interrupt some multisignature signing workflows involving older Core wallets. According to CryptoSlate, the graphical wallet in the new release creates Partially Signed Bitcoin Transaction (PSBT) files in version 2, while pre-32 Core software reportedly cannot import that format.
What the compatibility problem affects
The issue was described in an Oct. 14 user report. When a PSBT produced by the Bitcoin Core 32 GUI was loaded into an older Core wallet, the software returned an unsupported-version decoding error. The graphical interface did not provide an option to select an older PSBT format.
PSBTs are transaction files used to pass unsigned or partly signed Bitcoin transactions between wallets and signing devices. In a multisignature setup, one wallet may prepare a transaction while other wallets or co-signers add their signatures. If those participants use different software versions, an incompatible file format can prevent the transaction from moving through the signing process.
The affected format is PSBT version 2, defined by Bitcoin Improvement Proposal 370. Version 2 allows inputs and outputs to be added after a transaction is created when the relevant modification permissions are enabled. However, software that supports only PSBT version 0 cannot read it.
Fix moved to a later patch
The compatibility concern has been shifted to the Bitcoin Core 32.1 milestone. Maintainer fanquake moved the issue on Oct. 21, noting that the 32.0 release was overdue and that a fix was not ready to be included in that version.
A pull request, numbered 36539, proposes changing the graphical wallet back to creating PSBT version 0 files. It remained open when checked on Oct. 22, so the proposed repair had not yet been incorporated into the release described in the report.
The problem may also affect other tools. The source material says Bitcoin Core’s joinpsbts RPC accepts only version 0 files, meaning a PSBT created by the new GUI can also be rejected there. External signing software could face similar difficulties if it does not support version 2.
Bitcoin Core’s RPC interfaces provide a workaround for mixed-version users. The walletcreatefundedpsbt and createpsbt commands can be instructed to create version 0 by setting psbt_version=0. Bitcoin Core 32.0’s functional tests cover both versions and verify that the decoded result matches the requested format.
BIP 370 also allows a version 2 PSBT to be converted to version 0 by reconstructing its unsigned transaction, although the specification does not provide a direct operator command for doing that.
Market picture
Moneyiar market data at 23:34 on Oct. 22, 2026, showed Bitcoin at $81,250.85, down 3.57% over 24 hours and 1.04% over seven days. Filecoin was $0.9763, down 7.55% in 24 hours and 16.29% over seven days. Plasma stood at $0.07536, down 8.12% and 12.03%, respectively. Nexus was $0.0000006019, down 10.62% over 24 hours and 19.28% over seven days.
