Bitcoin Core 32 has entered release-candidate testing ahead of a planned stable release on October 10, 2026. A release candidate is a near-final build that developers and node operators test to surface bugs before the software is declared ready for widespread use.

The code at this stage is considered feature-complete, but it goes through one last round of real-world testing to make sure nothing was missed — comparable to a final dress rehearsal before opening night.

What Release-Candidate Testing Means for Bitcoin Core Users

Bitcoin Core is the primary software that runs a Bitcoin full node, the program that independently verifies every transaction on the network. That independent verification is what lets node operators check Bitcoin's rules themselves rather than trusting a third party, which is why the condition of this software matters to the whole ecosystem, not just to those running it. When a new version enters release-candidate testing, it signals that developers believe the code is ready but want community feedback before declaring it stable. Because Bitcoin Core is developed as open-source software in public view, the candidate stage works as a community-wide review of the code before a stable version ships.

During this phase, technically experienced users and node operators are encouraged to run the candidate build and report any issues. Feedback gathered in the testing window directly shapes whether the Oct. 10 release date holds or needs to slip.

The release-candidate build is pre-release software and is not equivalent to a stable version. Anyone operating a Bitcoin node at home or through a service should not install this build yet, as running pre-release software on a production node carries risk if undiscovered bugs are present. The stable release expected on Oct. 10 remains the appropriate upgrade for most users.

What to Watch Before the Oct. 10 Bitcoin Core 32 Release

The stretch between now and Oct. 10 is when the release-candidate process does its most important work. If testers surface significant bugs, the development team may issue a second release candidate, which would push back the final release date.

Release dates in open-source software are targets, not guarantees. The priority is always a stable, correct release over meeting a calendar deadline. That said, the report notes that entering the release-candidate stage at this point suggests the team is on track.

For anyone who holds or uses Bitcoin, the practical step is simple: follow the official Bitcoin Core project's release communications — published through the project's website and its public GitHub repository — to know when version 32 is declared stable and ready for upgrade. Release-candidate builds should not be installed on any node relied upon for real transactions.

Bitcoin's underlying network continues operating regardless of which version individual nodes run. The upgrade cycle for Bitcoin Core does not affect the coins holders own; it affects the software that verifies the network's rules. Keeping node software current and secure remains a priority for the broader ecosystem as Bitcoin continues to attract mainstream attention.

Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.