Bitcoin Core has moved its next major software release into formal testing with the publication of v32.0rc1. The first release candidate marks the transition of Bitcoin Core 32.0 from active development into its final validation cycle, giving developers and node operators an opportunity to identify problems before a production release is tagged.
The official v32.0rc1 GitHub release was tagged on September 14 with a verified signature. Its publication does not activate a Bitcoin network upgrade or require nodes to adopt new consensus rules, but instead provides a candidate build that can be tested against real operating environments, configurations and software dependencies before Bitcoin Core 32.0 is finalized.
Bitcoin Core 32.0 Is Now Under Feature Freeze
The release candidate follows a feature freeze that began on August 20. Bitcoin Core’s published release schedule specifies that only bug fixes should enter the 32.0 release after that point, alongside a freeze on source-language translation changes. The project then separated the 32.x release branch from master on September 14, while new development for the eventual 33.x cycle resumed on master.
That structure means v32.0rc1 is primarily intended to test whether the planned release behaves as expected rather than introduce additional functionality. Release-candidate testing shifts the development focus toward stability, regression detection and compatibility, while any issues discovered can still result in fixes and subsequent RC builds before the final version is issued. Bitcoin Core’s documented process specifically calls for a dedicated testing issue during the RC phase.
For node operators, the candidate offers an early opportunity to examine changes before deciding whether and when to upgrade production systems. Running an RC is fundamentally different from installing a final stable release, because the software is being distributed specifically so that problems can be found before the production tag is completed.
Final Bitcoin Core 32.0 Targeted for October
Bitcoin Core’s current schedule targets October 10 for the v32.0 tag. That date remains an intended release target rather than a fixed commitment, leaving room for the RC cycle to continue if testing exposes defects that maintainers consider necessary to resolve.
The project’s release process also requires several steps before a final major release, including completing the release notes and performing the final release preparation work. A signed RC tag therefore represents a late development milestone, not the final production version itself, even though the scope of acceptable code changes has already narrowed substantially.
The immediate variable to watch is whether testing of v32.0rc1 produces issues significant enough to require another candidate. If the testing cycle proceeds without release-blocking problems, Bitcoin Core is currently positioned to move toward its planned v32.0 tag in early October, while any material regressions could extend the validation process before the final release.