WORLDTECH NEWS Global technology intelligence.Contact
Bitcoin & Crypto SINGLE SOURCE

Bitcoin Core 32 can stall multisig signing on older nodes as fix slips to next patch

Hands using smartphone and terminal for cashless payment, showcasing modern transaction methods.
Illustrative photo.Photo by Ivan S on Pexels

What happened

21, while the proposed GUI repair remains open. The compatibility issue has moved to the 32.1 milestone, while a proposed GUI fix remains open.

The mismatch concerns the Partially Signed Bitcoin Transaction, or PSBT, format used to exchange transaction data during signing. A reported PSBT v2 import failure affects mixed-version Core wallets, while an explicit RPC option still creates v0 files.

Read the full story on CryptoSlate Understand the crypto stories that matter and what to watch next. BTC 4.32% · 24h Bitcoin Core 32 can stall multisig signing on older nodes as fix slips to next patch Bitcoin Core 32’s graphical wallet creates PSBT v2 files that older Core co-signers reportedly cannot import; RPC users can select the older format.

22, 2026 2 min read Quick Take 01 Bitcoin Core 32’s GUI creates PSBT v2 files that older Core co-signers reportedly cannot import. 02 Maintainer fanquake moved the compatibility issue to 32.1 on Oct.

03 Core 32’s RPCs can explicitly create PSBT v0, offering mixed-version users a path around this specific format mismatch. Make CryptoSlate preferred on Share Share Bitcoin Core 32.0’s graphical wallet can interrupt co-signing with older Core wallets by creating transaction files those versions cannot import, according to a user report .

14 report, user mjdietzx described an unsupported-version decoding error when loading a file created by the new graphical wallet into pre-32 Core. That can stop a workflow in which a newer Core wallet prepares a transaction and an older Core wallet supplies another signature.

Sources & evidence