Bitcoin Core 32 GUI disrupts mixed-version multisig signing

Bitcoin Core 32.0’s graphical wallet creates PSBT v2 files that older Core versions cannot import, disrupting mixed-version signing. A proposed GUI fix has been deferred to 32.1.

Bitcoin Core 32.0’s graphical wallet can disrupt multisig signing by creating Partially Signed Bitcoin Transaction (PSBT) version 2 files that older Core releases cannot import. The compatibility issue has been moved to the Bitcoin Core 32.1 milestone, while a proposed graphical-wallet fix remains open.

The issue was reported on Oct. 14 by a user who received an “unsupported version” decoding error when loading a PSBT created by the new wallet interface into a pre-32 Core version. The graphical wallet did not offer a setting to choose another PSBT version.

The mismatch affects mixed-version signing workflows in which a newer Core wallet prepares a transaction and an older wallet adds another signature. It can also affect the `joinpsbts` RPC, which accepts only PSBT version 0, and external signing software without PSBT v2 support.

PSBT files carry transaction data between wallets and signing devices before a Bitcoin transaction is broadcast. Version 2, defined by Bitcoin Improvement Proposal 370, allows inputs and outputs to be added after a transaction is created when the relevant modification flags are enabled. Software that supports only version 0 cannot read the format.

Bitcoin Core maintainer fanquake moved the issue to the 32.1 milestone on Oct. 21, citing the overdue 32.0 release and the lack of a fix ready for backporting. Pull request 36539, which proposes restoring the graphical wallet’s output to PSBT version 0, remained open on Oct. 22.

Core 32.0 users can avoid this specific mismatch through the RPC interface by setting `psbt_version=0` when using `walletcreatefundedpsbt` or `createpsbt`. The version 32.0 functional tests cover both PSBT formats and check that decoded output matches the requested version.

BIP 370 also allows an existing PSBT v2 file to be converted to version 0 by reconstructing its unsigned transaction. The proposal does not provide a direct operator command for that conversion.

GitHub displayed a verified and signed v32.0 final source tag dated Oct. 21. The official download page still listed version 31.1 when checked on Oct. 22, so the tag alone did not confirm that Core 32.0 binaries were available for download.

Articles by this author