Bitcoin Core 32.0 due October 10 with faster node validation

Bitcoin Core 32.0, the next version of the software that runs most Bitcoin nodes, is due on October 10, 2026. It adds faster block validation, a new way to estimate fees, and two security fixes. Consensus rules do not change.

That schedule comes from the Bitcoin Core project itself. Developers tagged the first release candidate, v32.0rc1, on September 14 and set October 10 as the target for the stable version. The project calls that a target, not a fixed deadline, so the date could still move. As of early October 10, the official download page still listed version 31.1.

What Bitcoin Core 32.0 changes

Bitcoin Core is the reference software for the Bitcoin network. Most of the computers that check and relay transactions, called nodes, run some version of it. Version 32.0 is a maintenance and performance release. It makes a node work faster and patches security holes rather than changing how Bitcoin itself works.

The headline change is speed. During a step called initial block download, a new node must download and verify the whole chain from the start. Version 32.0 fetches transaction inputs in parallel across several worker threads instead of one at a time. The default is 8 threads, up to a maximum of 16, and an operator can switch it off. In the project's own testing, that cut initial block download time by as much as three times.

Fees get a second change. The command wallets use to estimate a fee, estimatesmartfee, now blends the older method with a new one that reads the mempool, the pool of unconfirmed transactions waiting to be mined. The node returns the lower of the two numbers. In plain terms, when a backlog clears, the software can suggest a cheaper fee sooner than before.

A quieter change could trip up some wallets. Four commands that build partly signed transactions now default to a newer format, PSBT version 2. Older software that expects the previous format may need an update. Wallet makers and exchanges have been told to test before they move.

Other changes are smaller. The release adds new node commands, including one that exports the network address map built into the node and one that returns a machine readable list of every command the node offers. A few old fields and settings are being retired after long notice. None of this is forced on people running an older version, who can stay put until they choose to move.

The two security fixes

Version 32.0 closes two security holes. The first has been in the code since version 24.0. On systems other than Windows, a logged-in user allowed to create wallets could run commands on the host machine by giving a wallet a crafted name, but only when a feature called walletnotify was switched on. The fix makes the software treat wallet names as plain text.

The second fix stands out for how it came to light. Contributor Matthew Zipkin, who posts under the handle pinheadmz, found a memory exhaustion bug while auditing the node's new web server with help from an AI model called Kimi K3. Zipkin first thought only logged-in users could set it off. A reviewer using the name jeanpablojp then showed that 16 unauthenticated connections could do it too, as long as the REST interface was turned on.

Those numbers matter. Before the patch, 16 such connections could push a node's memory use to about 3.2 gigabytes. After the fix, the same test added roughly 3 megabytes over 90 seconds. The patch was merged on September 5.

Faster validation, but not faster payments

A faster node does not mean faster Bitcoin payments. The speed gains in version 32.0 help someone setting up or resyncing a node, not someone sending money. Blocks still arrive about every 10 minutes on average, and the network sets that pace, not the software a single user runs.

Nothing here touches the rules that decide which blocks are valid. No new coins. No fork. Because the release is about running a node rather than the price of the asset, it does not move the market on its own.

What to watch

Watch first for whether the stable release lands on October 10 as planned or slips by a few days. Release candidates often turn up late bugs. People who run their own nodes will want to read the full notes before upgrading, mostly for the PSBT version 2 default, which is the change most likely to break a connected wallet or service.

Bitcoin is not alone in shipping steady upgrades. Ethereum's Glamsterdam upgrade reached a test network in early October, part of the same pattern of planned, regular changes to major networks. For Bitcoin, the question after 32.0 is which performance and privacy ideas, some still being debated, make it into version 33.