Skip to content
EVENT / TOPICHistorical

Bitcoin Core 32 GUI Generates PSBT v2 Files Incompatible with Older Nodes

1 reports1 sources10/22/2026 updated

Current overview (not historical)

AI overview

Bitcoin Core 32’s graphical user interface now creates PSBT v2 files that are not compatible with older Core nodes, preventing multisignature nodes from importing them. The Core developers have added a fix to the 32.1 milestone, but the issue remains unresolved as of the latest reports. Meanwhile, the RPC interface still allows explicit creation of PSBT v0 files, giving users who need to mix versions a temporary workaround.

Written with AI from the reporting · updated 10/22/2026

Expand the detailed fact route and sources

Story route

A station-by-station route from the first public evidence onward; every station carries its own evidence and uncertainty.

  1. 1Unclassified fact stationOct 22, 00:00recorded Oct 23, 02:15single sourcerevised

    Bitcoin Core 32 GUI creates incompatible PSBT v2 files for o

    Read original source ↗ CryptoSlateReplay this moment in the explorer
    Evidence & revisions · 1 source records
    Subject:
    bitcoin
    Action:
    GUI creates PSBT v2 files that older Core nodes cannot import
    Object:
    PSBT v2 transaction files
    Occurred (fact side):
    Oct 22, 00:00
    CryptoSlate ↗Report pageRevision 2 · currently revised
    Published (valid side):
    Oct 23, 02:00
    First seen (known side):
    Oct 23, 02:15
    Fact stationSingle source · one-sided claimRevised

    Copy may have been revised later; time replay is bounded. Layer labels group reading only, not causation between layers.

Uncertainty marks flag where to check the sources; they are not proven causation.

Report timeline

Explore every side through dated source reports.

Oct 23
  1. CryptoSlateRelated fact: single sourceSource report revised
    Bitcoin Core 32 GUI PSBT v2 format may stall multisig signing on older nodes

    Report first recorded Oct 23, 02:15

    Bitcoin Core 32's graphical wallet creates PSBT v2 files that older Core co-signers reportedly cannot import, which can interrupt co-signing workflows. This compatibility issue has been moved to the 32.1 milestone, and a proposed GUI fix remains open. Users can bypass this format mismatch by explicitly creating PSBT v0 via Core 32's RPC interface using psbt_version=0.

    Read original source ↗

Event discussion

Reader opinions are hosted on GitHub Discussions; posting requires a GitHub account. Comments are not verified facts.

Open GitHub Discussions