Bitcoin Core 32.0 causes multisig signing issues on older nodes

Bitcoin Core 32.0's graphical wallet can disrupt co-signing with older Core wallets by generating transaction files that those versions cannot import. This compatibility issue has been moved to the 32.1 milestone, while a proposed GUI fix remains open. A user reported an unsupported-version decoding error when trying to load a file created by the new graphical wallet into pre-32 Core. The GUI lacks a version selector, which can halt workflows where a newer Core wallet prepares a transaction and an older wallet provides another signature. The problem involves the Partially Signed Bitcoin Transaction (PSBT) format, with the new GUI creating PSBT v2, which is incompatible with software that only supports v0. The report also noted that v2 outputs are rejected by joinpsbts, which only accepts v0 files. GitHub shows a verified source tag for v32.0 dated Oct. 21, but the official download page still listed version 31.1 as of Oct. 22. Maintainer fanquake moved the compatibility issue to 32.1 on Oct. 21, indicating that 32.0 was overdue and a fix was not ready. Users can avoid the PSBT format mismatch by selecting v0 when creating files through Core 32's RPC interface. BIP 370 allows converting an existing v2 PSBT to v0, but does not provide an operator command.

This content is provided for general informational purposes only and doesn't constitute financial, investment, legal, or tax advice. Any events, rewards, online promotions, or related information mentioned herein should not be considered a recommendation, solicitation, or invitation to purchase, sell, trade, or otherwise deal in any crypto assets. Crypto assets are highly volatile and may result in loss. The availability of WEEX services, products, and related events may vary by region. You are responsible for ensuring that your participation is in accordance with applicable local laws and regulations.