Bitcoin Core Has Entered Version 32 Testing
The release candidate addresses memory growth and improves block check performance.
Updated on Sept. 21, 2026 in Software
Live Poll
Do you prefer to install software updates immediately or wait until they are proven stable?
Bitcoin Core developers have moved the software to version 32.0 release-candidate testing. This update introduces parallel database reads and patches for known memory management issues.
Why it matters
The development branch allows contributors to isolate and test stability improvements without disrupting ongoing work on future code. These refinements are designed to enhance node efficiency and security performance.
Version 32.0 reduces memory consumption from 3.2 gigabytes to 3 megabytes in stress tests by patching unauthenticated HTTP activity. It also enables parallel database reads for faster block verification.
The players
Bitcoin Core
An open-source project maintaining the primary software client used by nodes to validate transactions and blocks on the Bitcoin network.
The details
The update creates a separate release branch that allows maintainers to conduct bug hunting on stable code while development continues elsewhere. One key architectural change mandates that four wallet commands use PSBT version 2—a standard for Partially Signed Bitcoin Transactions that simplifies multi-signature workflows—by default. Additionally, the software now supports parallelized database reads, enabling nodes to verify multiple blocks simultaneously rather than sequentially.
Timeline
August 6, 2026: Developers opened translations and froze translation changes.
August 20, 2026: Developers introduced a feature freeze for version 32.
September 14, 2026: Developers created the version 32 branch and started the candidate cycle.
October 10, 2026: The target date for the stable version 32 release.
The Tech Race
This release follows the standard development trajectory for maintaining the integrity of the Bitcoin network. It aligns with the ongoing cycle of quarterly feature freezes designed to balance innovation with node stability.
Node operators running current versions will eventually need to update to version 32.0 to access improved memory efficiency and parallel processing. The change will particularly benefit operators managing nodes on hardware with lower memory overheads.
The takeaway
This update emphasizes optimization by significantly reducing memory overhead for node operations. Node operators should monitor the project repository for the official stable release announcement currently targeted for October 10.
What happens next
The stable release of version 32.0 is scheduled for October 10, 2026, pending successful resolution of issues identified during candidate testing.
Further reading
For more on how infrastructure updates shape network performance, visit our Software coverage.
Live Poll
Do you prefer to install software updates immediately or wait until they are proven stable?
