Sixteen. That’s all it took, sixteen open connections to a Bitcoin node, to spike its memory use from 46 megabytes to nearly 3 gigabytes in under a minute. Testers caught that bug before it shipped in Bitcoin Core 32, the next version of the software that lets ordinary computers verify Bitcoin transactions without trusting a bank, an exchange, or anyone else to do it for you.
The update entered final testing on September 14, with a stable release targeted for October 10, CoinDesk reports. It doesn’t touch Bitcoin’s rules. It changes how fast your node runs, what you pay in fees, and how safe that node stays from someone trying to knock it offline.
What Bitcoin Core 32 Actually Fixes
Bitcoin Core isn’t flashy. It’s the quiet software running behind exchanges, wallets, and home setups everywhere, and this release focuses on things regular people actually feel.
- A dual fee estimator that watches both confirmed blocks and pending transactions, so fee recommendations drop faster once network traffic clears
- Multi-threaded block validation, using eight threads by default, that speeds up how quickly a new node catches up to the blockchain
- A patched wallet-naming flaw, open since version 24.0, that could have let an authenticated user run commands on the host machine
- The memory bug above, closed months before most users ever touch the new version
- A shift to PSBT version 2 as the default format for hardware wallet transactions
The Bug That Could Have Crashed Nodes in a Minute
That memory issue lived in Core’s new lightweight web server, built to replace an aging library. Sixteen unauthenticated connections were enough to overwhelm it. After the fix, the same attack barely nudges memory use past 3 megabytes.
Picture a hardware store owner in rural Ohio who runs her own Bitcoin node so she isn’t relying on someone else’s server to confirm the payments customers send her. She’s not a programmer. Left unpatched, this bug could have knocked her offline with almost no effort from an attacker. Testers caught it first.
Fees That Drop Faster, Syncing That Takes Less of Your Day
The fee change sounds small, but it isn’t. Wallets often keep recommending yesterday’s high fee even after the network calms down, because they only look at confirmed blocks. Core 32 also checks what’s sitting in the mempool, so recommended fees fall sooner. For someone paying $3 to $8 a transaction during a busy week, catching that drop even a few hours earlier adds up over a year of regular payments.
The sync speedup matters just as much. Setting up a full node used to mean leaving a computer running for days. Multi-threaded validation cuts that wait, so more people, including a father working night shifts who wants his first node running by Saturday, can actually finish the job.
Why This Matters Even If You’ve Never Touched Core
Most Bitcoin users never install Core directly. They use an exchange, an app, or a hardware wallet, and those services often run Core themselves. A fix here protects millions of people who have never heard of it. It’s the same quiet-infrastructure logic behind the recent security fix in LDK, the library powering many Bitcoin Lightning apps: the software nobody sees is still the software everyone depends on.
Decrypt’s coverage has more on how the update reached this stage, and node operators can find the technical detail in the Bitcoin Core release schedule on GitHub.
October 10 is the date to watch. If you run a node, plan the upgrade. If you don’t, ask your wallet provider whether they will run it, because that answer is your security too.