Bitcoin Core Releases v32.1, 31.2 and 30.4 Maintenance Updates

Bitcoin Core maintainers published three releases within minutes of each other on October 28, 2026: version 32.1 at 14:23 UTC, version 31.2 at 14:24 UTC, and version 30.4 at 14:26 UTC, according to the project's own GitHub release tags.

Three branches, one release window

Bitcoin Core maintains multiple active version lines simultaneously, so that node operators who have not upgraded to the newest major release still receive fixes. Version 32.1 sits on the newest branch, while 31.2 and 30.4 are maintenance updates for the two prior major releases. Each release page directs users to download binaries from bitcoincore.org rather than GitHub's own generated archives, noting that only the bitcoincore.org builds are "generated deterministically and signed," per the release notes posted to each of the three GitHub pages.

The release notes for each version point to a corresponding file in the project's repository at doc/release-notes/, following Bitcoin Core's standard documentation practice for point releases. The GitHub release pages themselves do not enumerate the specific bug fixes or behavioral changes bundled into 32.1, 31.2, or 30.4; that detail lives in the linked release-notes files rather than in the release announcement text itself. Bitcoin Core's repository is maintained by a distributed group of contributors operating under the bitcoin/bitcoin GitHub organization, with release tagging handled by designated maintainers as part of the project's established release process.

What node operators should check

For holders and node operators, the practical takeaway is procedural rather than urgent: Bitcoin Core's own instructions direct users to the signed, deterministically built binaries hosted at bitcoincore.org rather than GitHub's automatically generated source archives, a distinction the project repeats verbatim across all three release pages. This is a standard practice for the project, not a response to a specific incident disclosed in this release cycle.

No security advisory accompanies any of the three release tags as of this writing, based on a check of the GitHub release pages linked above. Whether 32.1, 31.2, and 30.4 are routine maintenance releases or address any specific defect is not stated in the release tags themselves; the detail would appear in the full release-notes documents, which were not independently reviewed for this article beyond the summary text published on each GitHub release page.

Operators running Bitcoin Core on supported branches can expect the normal update cadence: point releases arrive on the current major version and on prior branches still within their support window. Readers tracking the Bitcoin network's infrastructure updates should watch for whether the project publishes expanded release notes or any follow-up advisory tied to this release batch.