Bitcoin Core 32.0 Enters Final Testing Ahead of October 10 Release

Bitcoin Core, the reference software that runs the large majority of the network's full nodes, has entered its final release-candidate testing phase ahead of a planned stable release on October 10, 2026. Developers tagged the first release candidate, v32.0rc1, on September 14 following an August feature freeze, and testing has continued through late September with no reported showstopper bugs so far.

Crucially, version 32.0 is a software maintenance release, not a protocol upgrade — it changes none of Bitcoin's consensus rules, so there is no fork, no signaling period, and no risk of chain splits. Node operators who skip it keep running exactly the same rules as everyone else; they simply miss out on the performance and tooling improvements bundled into this release.

Faster Validation, Not Faster Blocks

The headline technical change is a move to parallel database reads during block validation. By letting the node read multiple pieces of chainstate data from disk simultaneously instead of sequentially, Core 32.0 can meaningfully cut the time it takes a node to verify and accept a new block. Developers have been careful to stress that this does not touch Bitcoin's roughly ten-minute block production rate — it only speeds up how quickly an individual node can catch up and verify what the network has already produced, which matters most during initial block downloads and reorg handling.

Wallet and Fee Estimation Changes

On the wallet side, four RPC commands switch to using PSBT version 2 (Partially Signed Bitcoin Transaction) by default, while still retaining compatibility with the older PSBTv0 format for software that hasn't caught up yet. PSBTv2 is the more flexible, actively maintained standard used by modern multisig and hardware-wallet coordination tools, so the shift nudges the ecosystem further away from the legacy format. Fee estimation logic also receives tuning aimed at producing more reliable fee suggestions during periods of mempool congestion.

Security Patches and the Upgrade Gap

Alongside the performance work, 32.0 bundles several security-hardening fixes accumulated since the last major release. Researchers monitoring node software note that a significant share of reachable Bitcoin nodes — some estimates put it above 40% — are still running versions old enough to lack recent security backports, a gap that matters for a decentralized network whose safety depends on many independently-run, up-to-date nodes rather than a central operator.

Bitcoin Core maintainers are urging operators, especially those running older 2x or early-2025-era releases, to plan their upgrade once 32.0 leaves release-candidate status. As with every Core release, the update is optional, non-controversial from a consensus standpoint, and can be verified against developers' signed release hashes before installing.