Bitcoin Core 32 Wallet Update Caused Multisig Signing Errors, Fix Planned for 32.1

Bitcoin Core 32 update stops some multi-signature transactions from completing

Bitcoin Core version 32 includes a new wallet feature that prevents some users from completing multi-signature transactions. When a user with the new software attempts to send a transaction to someone using an older version, the older software often rejects the file. This can stop the transaction from being signed and broadcast to the network. The issue specifically affects users who rely on multiple devices to approve a single payment.

A user named mjdietzx reported this problem on GitHub on October 14, 2026. The report noted that the new graphical interface creates a file format that older software cannot read. This prevents the co-signing workflow from finishing. The problem has been formally logged in the Bitcoin Core development tracker.

What is confirmed by the report

• The new version 32.0 creates Partially Signed Bitcoin Transaction (PSBT) files in version 2.
• Older software versions only accept PSBT version 0 files, causing an error when they try to import version 2.
• The specific command used to combine these signature files, joinpsbts, rejects the new version 2 files.
• The issue was moved to the next update, 32.1, on October 21 because 32.0 was already scheduled for release.
• A proposed fix to change the file format back to version 0 is currently open for review on GitHub.

The new file format explains the glitch

The technical issue involves a specific standard called BIP 370. This standard describes PSBT version 2, which allows for more flexible transaction data. While this new format offers advanced features for building complex transactions, it was designed to be incompatible with older version 0 files. This means software built before this update does not know how to process the new file structure.

However, users who interact with Bitcoin Core through command-line interfaces rather than the graphical screen have a workaround. They can use specific commands to force the software to create the older version 0 format. This path allows users running mixed software versions to continue working without waiting for the 32.1 update.

What happens next

Developers have indicated that the main fix for the graphical interface will be included in the 32.1 patch. This next version is not currently available for download. While the 32.0 source code has been tagged, the official download page still lists 31.1 as the latest version. The 32.1 update will restore the ability to use multi-signature workflows across different software versions without needing to use advanced command-line tools.

Sources

• CryptoSlate

Read also: Bitcoin Core updates security policy to speed up fixes for AI-found bugs