Bitcoin Core 32 Enters Final Testing Ahead of October 10 Release: Faster Nodes, Safer Wallets and No Hard Fork Needed

Bitcoin’s core software is entering the home stretch of its next major upgrade. Bitcoin Core 32.0 has moved into release-candidate testing, with developers targeting an October 10 release — and while it won’t change Bitcoin’s rules or make blocks arrive faster, it should make the machines that power the network noticeably quicker and safer at their jobs.

By Keisha Williams | September 21, 2026

The Hook: A Big Software Update, Not a Bitcoin Rule Change

If you own Bitcoin, nothing about your coins changes when version 32.0 ships. Your balance stays the same, your private keys stay the same, and the rules that decide which transactions are valid stay the same. What is changing is the software that thousands of computers — called nodes — run to check every transaction and keep the network honest. Think of it as upgrading the operating system at a bank branch without changing any of the accounts inside.

According to the project’s official release schedule, developers created the version 32 branch and started the release-candidate cycle on September 14, with the first candidate — v32.0rc1 — now available for public testing. October 10 is the intended date for the stable release, though the schedule describes it as a target rather than a guaranteed deadline. Problems found during testing could still require additional candidates and push the date back.

The groundwork was laid months ago. Developers opened translations and imposed a soft freeze on translation changes on August 6, followed by a full feature freeze on August 20. From that date onward, the version 32 branch accepted only bug fixes — no new features. When the branch separated from the main codebase on September 14, work on Bitcoin Core 33 also began in parallel, so the next version is already in motion.

On the Code: Parallel Database Reads and a Memory Bug Fix

The headline technical improvement allows Bitcoin Core to read data from its database in parallel while checking blocks. Until now, those database reads happened one after another — like a single cashier working through a line of customers. The new approach is closer to opening several checkout lanes at once, shortening the time a node needs to validate each block without altering anything about the network itself.

That distinction matters, and it is where a lot of confusion creeps in. Faster validation does not mean Bitcoin will produce blocks more quickly. Miners still compete under Bitcoin’s proof-of-work rules, which target an average block interval of roughly ten minutes. Version 32 changes how a node processes information, not the network’s issuance schedule or block timing. And because Bitcoin Core is node software rather than a centrally managed update, operators decide for themselves whether and when to install it.

The release also ships two security fixes worth knowing about. The first patches a problem where specially constructed custom wallet names could cause commands to run on non-Windows nodes — an issue involving command execution, not Bitcoin’s underlying cryptography. The second addresses runaway memory growth triggered by unauthenticated HTTP requests. In one test cited by Bitcoin News, memory use climbed to roughly 3.2 gigabytes before the patch, versus about 3 megabytes after it — a dramatic difference for anyone running a node that other applications connect to.

Wallets: PSBT Version 2 Becomes the Default

For wallet users, the most visible change is subtler but real. Four wallet commands will now create partially signed Bitcoin transactions — known as PSBTs — using version 2 of the format by default. A PSBT lets separate wallets, devices, or participants exchange the information needed to build and sign a transaction without ever exposing private keys. It is the standard plumbing behind hardware wallets, offline signing setups, and multi-signature arrangements.

Version 2 of the format reorganizes how transaction information is stored and lets participants update parts of a transaction without first constructing a complete unsigned one. Crucially, the older format remains available for applications that still expect it, which reduces the risk of abruptly breaking wallets and services that have not yet made the switch. For individual holders, the practical effect is essentially zero — but for wallet developers and exchanges, it is a workflow change they will need to test against.

The Core Conflict: Why This Isn’t a Soft Fork

Bitcoin’s most heated debates usually center on consensus rule changes, which require coordination among miners, node operators, and the wider community. Version 32 deliberately sidesteps that battleground: it introduces no new consensus rule and requires no soft fork. That makes it a pure software improvement — faster, safer, more modern — that anyone can adopt, ignore, or defer without splitting the network.

The contrast with actual protocol proposals is stark. As previously reported by crypto.news, LayerTwo Labs CEO Paul Sztorc noted that every proposed Bitcoin soft fork since Taproot has failed to activate. BIP-110, a disputed proposal linked to transaction-relay policy, drew just 2.53% miner support before its enforcing branch stalled after two blocks. Against that backdrop, a performance release that needs no one’s permission to roll out is a reminder that meaningful Bitcoin progress does not always require a political fight.

Market Implications: Boring Upgrades Are Good for Your Portfolio

Nothing in version 32 moves the price of Bitcoin today, and that is precisely the point. Bitcoin was trading around $86,036 at the time of writing, up roughly 5.8% on the day, with Ethereum near $2,757 and Solana around $117. A network whose core software gets steadily faster, leaner, and more secure — without drama, forks, or downtime — is the kind of infrastructure that institutional buyers say they want underneath their positions.

There is tangible money behind that idea now. In July, Anchorage Digital, ARK Invest, BlackRock, Block, Blockstream, Coinbase, Fidelity Digital Assets, Galaxy, and Strategy formed the Bitcoin Security Consortium with $15 million in pledges over three years. Each member directs its own funding rather than pooling it, and the group says it will not control Bitcoin development or take positions on protocol proposals. Mike Schmidt, executive director of the developer-funding nonprofit Brink, coordinates the consortium’s daily work as a volunteer, with an initial focus on long-term security research — including defenses against future quantum-computing risks.

The Verdict: Update When It’s Stable, Not Before

For regular investors, the right move is simple: nothing, for now. If you run a node, test the release candidate if you are curious, or wait for the stable version expected around October 10 — and treat that date as a target, not a promise. If you use a hardware wallet or an exchange, the PSBT change will be handled behind the scenes by the companies building those products.

The bigger takeaway is qualitative. Bitcoin’s development pipeline is functioning: features were frozen in August, candidates are being tested in September, and a stable release is targeted for October — while work on version 33 has already started. In a market where headlines swing on lawsuits and liquidations, quiet, disciplined software maintenance is one of the strongest signals that the asset beneath your portfolio is being taken seriously by the people who build and fund it.

The cryptocurrency market remains highly volatile. This article is for informational purposes only and does not constitute financial advice.