Bitcoin Core’s official GitHub repository tagged v32.0 on 21 October 2026 at 13:27 UTC. GitHub marks the tag’s commit signature as verified and identifies the release as “Bitcoin Core 32.0 final.” That establishes a final source-code tag; it does not by itself establish that every operating-system binary is ready for general download.

When NetNapz checked the project’s official download directory on 22 October, the 32.0 folder listed only the rc2, rc3 and rc4 release-candidate directories. Stable binary packages and a corresponding stable-release page were not visible there. Operators should therefore distinguish the final source tag from packaged binaries, signature files and platform-specific installation readiness.

What version 32 changes

Materials published during release-candidate testing describe operational changes rather than a change to Bitcoin’s consensus rules. The update adds a mempool-aware fee estimator alongside the historical estimator, introduces parallel database reads for some block-validation work and makes PSBT version 2 the default for several wallet commands.

The release also brings a rewritten HTTP server used by RPC and REST clients, new machine-readable RPC information and a watch-only wallet export command. Downstream services should test their own clients and workflows against the final build rather than assume release-candidate compatibility guarantees production compatibility.

Security fixes require careful scope

Release-candidate reporting documented a command-execution flaw involving walletnotify on non-Windows systems under specific conditions, including authenticated wallet-creation access and a crafted wallet name. It also described a memory-exhaustion issue found in the rewritten web server before the final release.

NetNapz assessment: these are software-level reasons for affected operators to review the final notes and upgrade path. They are not evidence of a Bitcoin consensus failure, lost private keys or a requirement for ordinary holders to move coins. A node update never requires sending bitcoin to a migration address.

Operator checklist

Operators should wait for the project’s stable packages and published verification material for their platform, then compare checksums and signatures through official Bitcoin Core channels. Backups, configuration review and staged testing are especially important for services that depend on wallet notifications, custom RPC or REST clients, PSBT workflows, transaction indexing or Tor and I2P networking.

Assessment: the gap between a final Git tag and the stable binary directory may simply reflect normal release packaging and publication work. NetNapz found no official statement attributing that gap to a defect or withdrawal, so this report does not infer one.

Sources and timing

Bitcoin Core GitHub: v32.0 final tag, tagged 21 October 2026. Bitcoin Core GitHub: version 32.0 release schedule, updated 21 October. Bitcoin Core official 32.0 download directory, checked 22 October. Bitcoin Optech release-candidate testing discussion, published 29 September.