Bitcoin Core 32.0 Gets Its Final Tag as Release Verification Comes Into Focus

Bitcoin Core’s final v32.0 tag appeared on October 21, 2026, marking a concrete milestone for the project’s next major version. The [GitHub tag page](https://github.com/bitcoin/bitcoin/releases/tag/v32.0) identifies the final revision as 465dde2 and displays a verified signature. That gives developers and independent builders a specific source revision to examine and reproduce.
The timing changed during the release cycle. The project’s [32.0 tracking issue](https://github.com/bitcoin/bitcoin/issues/35122) originally targeted October 10 for the final tag, then recorded October 21 as the completed date. Maintainer fanquake also posted confirmation that the 32.0 tag was available. The issue does not establish a single explanation for the revised date, so attributing it to a particular bug would go beyond the evidence.
Preparation had been visible for months. The schedule records an August 20 feature freeze, followed by the September 14 branch split and first release candidate. Updates then announced third-candidate binaries on October 6 and fourth-candidate binaries on October 14. Those checkpoints show the progression from a development branch through successive test versions to a final source tag.
For readers following Bitcoin infrastructure, the useful distinction is between identifying final source code and verifying the software actually installed on a machine. A signed tag anchors a particular repository revision. Downloaded executables require their own checks, because a tag signature alone does not authenticate every file presented as a release download.
Bitcoin Core’s [documented release process](https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.md) describes consistency checks before creating a signed tag, followed by building and attesting to build outputs. Its workflow uses Guix and collects builders’ attestations in a separate repository. These steps make the path from reviewed source to distributed software inspectable.
The project’s [download instructions](https://bitcoincore.org/en/download/) explain the user-facing side: compare a downloaded file’s checksum with the published checksum list, then verify signatures from trusted signing keys. They also describe reproducible builds, through which independent contributors can generate identical binaries and publish signed checksums.
At the time checked for this article, that download page still identified 31.1 as its latest version, while GitHub already showed the final 32.0 tag. The evidence therefore supports a precise headline about the tag milestone. For node operators, the next practical checkpoint is the corresponding official distribution and its verification materials. For developers, today’s tag already supplies the fixed reference needed to inspect the final source.