Bitcoin Core Posts Proposed 32.0 Schedule Ahead of September Branch-Off

WHO, WHAT, WHEN, WHERE

On April 20, 2026, Bitcoin Core maintainer fanquake opened GitHub issue #35122, titled “Release Schedule for 32.0.” The issue is a pinned tracking issue on the 32.0 milestone. It presents a proposed calendar that targets a major release in early October 2026. It is a process record, not a tagged release. [1]

As displayed on that issue, the August 6 translation step and the August 20 feature freeze are marked complete. The September 10 branch-off and release-candidate step, and the October 10 final-tag step, remain marked in progress. The issue asks contributors to comment if any specific dates are a problem. That language treats the calendar as a proposal. [1]

CONFIRMED EVIDENCE

The tracking issue lists these dates:

• 2026-08-06: open Transifex translations for v32.0, apply a soft translation string freeze, and finalize translations for v30.0. Marked complete on the issue.
• 2026-08-20: feature freeze, described as bug fixes only until release, plus a translation string freeze. Marked complete on the issue.
• 2026-09-10: remaining work before branch-off, split a 32.x branch from master, start the RC cycle and tag v32.0rc1, and start merging for 33.x on master. Marked in progress.
• 2026-10-10: tag v32.0, described as an aim. Marked in progress.

Those items are the issue’s own checklist. They are not independent proof that every later step has occurred. [1]

Pull request #35915, “Release: Prepare Open Transifex translations for v32.0 step,” was merged on August 7, 2026. The pull request says it follows Bitcoin Core’s release process and is required to open Transifex translations for v32.0 as scheduled in issue #35122. That confirms the translation-prep step. It does not confirm branch-off or an rc1 tag. [3] [2]

The official Bitcoin Core download page currently lists “Latest version: 31.1,” with binaries under the bitcoin-core-31.1 directory. It does not list a 32.0 or 32.0rc1 download. The 31.1 release notes remain published. No v32.0rc1 or v32.0 tag was found in the sources reviewed for this draft. [4] [7] [1]

Bitcoin Core’s Software Life Cycle page lists 32.x with a release date of TBA and an end-of-life of after v35.0. The same table lists 31.x as released 2026-04-19, 30.x as 2025-10-10, and 29.x as 2025-04-14. A footnote says the project aims to make a major release every 6-7 months. [5]

The 31.0 release notes state that, with that major version, 28.x and older are at End of Life and will no longer receive updates. The life-cycle page says the project maintains the latest three major versions. [6] [5]

CONTEXT AND TIMELINE

Bitcoin Core versions software as MAJOR.MINOR. The project aims for a major release about every six months. Maintenance releases fix bugs and, aside from the documented exception for consensus-rule changes, do not introduce major new features. [5]

The project’s release-process document describes work around a major branch-off, including translation updates, seed and asmap updates, chainparams updates, and later tagging of release candidates. Issue #35122 points to that document for the September 10 branch-off work. Completing those steps is process work. It is not the same as publishing 32.0 binaries on bitcoincore.org. [2] [1]

If 32.0 is later tagged and published, the life-cycle table currently says 29.x would reach end of life after v32.0. That is stated policy, not evidence that 29.x support has already ended. Operators running 29.x, 30.x, or 31.x should read the life-cycle page and the then-current release notes rather than treat this schedule as an upgrade instruction. [5]

WHAT REMAINS UNKNOWN OR DISPUTED

The tracking issue does not list the features that would ship in 32.0. This article does not infer them.

The September 10 and October 10 dates can move. The issue itself invites date comments. Branch-off, an rc1 tag, and a final 32.0 tag are separate events. None of those later events is confirmed in the sources reviewed here.

The merged Transifex preparation pull request does not prove that every later checklist item is complete.

WHAT READERS SHOULD WATCH NEXT

Watch issue #35122 for changes to the checkmarks, dates, or description. Watch the bitcoin/bitcoin repository for a 32.x branch and for a signed v32.0rc1 tag. Watch the Bitcoin Core download page and releases index for any 32.0 or 32.0rc1 listing. Until those records change, 31.1 remains the latest published Bitcoin Core version on the project’s download page. [1] [4] [7]

SOURCES AND DISCLOSURES

[1] Bitcoin Core GitHub tracking issue #35122, “Release Schedule for 32.0,” opened April 20, 2026:
https://github.com/bitcoin/bitcoin/issues/35122

[2] Bitcoin Core release-process document, including branch-off and release-candidate tagging steps:
https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.md

[3] Pull request #35915, merged August 7, 2026, preparing Transifex translations for v32.0:
https://github.com/bitcoin/bitcoin/pull/35915

[4] Bitcoin Core download page, listing 31.1 as the latest version:
https://bitcoincore.org/en/download

[5] Bitcoin Core Software Life Cycle, including the 32.x TBA row and the three-major maintenance policy:
https://bitcoincore.org/en/lifecycle/

[6] Bitcoin Core 31.0 release notes, including the End of Life statement for 28.x and older:
https://bitcoincore.org/en/releases/31.0/

[7] Bitcoin Core 31.1 release notes:
https://bitcoincore.org/en/releases/31.1/

Disclosure: This is a sourced report on Bitcoin Core’s published release-process records, not a recommendation to upgrade, delay an upgrade, or take any market position. The September 10 and October 10 dates are proposed targets on a public tracking issue, not confirmed release events. No paid placement, sponsorship, or affiliate relationship with Bitcoin Core or the cited sources was used. The featured illustration was generated for CryptoWorkPro and is not a documentary photograph of a Bitcoin Core event or a copy of project artwork.