Bitcoin Core 32.0’s graphical pockets can interrupt co-signing with older Core wallets by creating transaction recordsdata these variations can’t import, in accordance with a person report. The compatibility subject has moved to the 32.1 milestone, whereas a proposed GUI repair stays open.
Within the Oct. 14 report, person mjdietzx described an unsupported-version decoding error when loading a file created by the brand new graphical pockets into pre-32 Core. The GUI supplied no model selector. That may cease a workflow during which a more moderen Core pockets prepares a transaction and an older Core pockets provides one other signature.
The mismatch considerations the Partially Signed Bitcoin Transaction, or PSBT, format used to change transaction knowledge throughout signing. The brand new GUI creates PSBT v2. BIP 370 permits v2 so as to add inputs and outputs after creation when its modification flags allow, however intentionally makes it incompatible with software program that solely handles v0.
The report additionally describes v2 output being rejected by joinpsbts, an RPC that accepts solely v0 recordsdata. Exterior signing software program could face related hassle if it lacks v2 assist.
GitHub exhibits a verified, signed v32.0 ultimate supply tag dated Oct. 21. The official obtain web page nonetheless marketed 31.1 when checked Oct. 22, so the tag alone shouldn’t be learn as affirmation that 32.0 binaries can be found.
Maintainer fanquake moved the compatibility subject to 32.1 on Oct. 21, saying 32.0 was overdue and there was not but a repair able to backport. Pull request 36539 proposes restoring GUI-created PSBTs to v0 and remained open on the Oct. 22 examine. yourcryptonewstoday’s September release-candidate protection had flagged the RPC format-default modifications; the GUI repair’s deferral is the later growth.
The way to keep away from the PSBT format mismatch
Blended-version co-signers can select v0 when creating the file by means of Core 32’s RPC interface, utilizing psbt_version=0 with walletcreatefundedpsbt or createpsbt. The v32.0 useful exams cowl each format variations and examine that the decoded output matches the requested model.
BIP 370 additionally permits changing an present v2 PSBT to v0 by reconstructing its unsigned transaction, however doesn’t itself present an operator command.
