Bitcoin Core v31.1 released

The Bitcoin Core project announced on July 8, 2026 that version 31.1 of the reference Bitcoin implementation is out, posting download and release-notes links from its official account at 2:46 PM UTC.

That is the extent of what the announcement confirms. The announcement is a routine release notice: a .1 version number denotes a point release, which for Bitcoin Core historically means bug fixes and backported changes on top of the 31.0 series rather than new consensus rules or major features. The specific contents of the v31.1 release notes were not spelled out in the announcement itself, so what changed is not characterized here — the linked notes at bitcoincore.org/en/releases/31.1/ are the primary source for that, and readers should consult them directly.

Bitcoin Core is the most widely run node software on the Bitcoin network and is developed openly by a distributed set of contributors; it is not a company product and no party is paid to promote it. The announcement carries no marketing framing.

The replies under the announcement are the usual mix of node-runner enthusiasm and Bitcoin's long-running culture-war references — a question about whether the release blocks CSAM/arbitrary data, and handles tied to soft-fork activation campaigns (BIP-110, CTV+CSFS). None of that is part of the release itself, and there is no confirmation that v31.1 touches data-filtering or any consensus change. Treat those replies as user commentary, not release content.

Key facts

• Bitcoin Core v31.1 released, announced July 8, 2026 at 2:46 PM UTC. (Source: @bitcoincoreorg via Nitter)
• Download page: bitcoincore.org/en/download/; release notes: bitcoincore.org/en/releases/31.1/. (Source: @bitcoincoreorg)
• Version numbering (.1) indicates a point release; the notes' actual contents were not detailed in the announcement. (Based on Bitcoin Core's versioning convention — unverified against the notes.)

The real-world read

There is no story here beyond "a scheduled point release shipped" — and it is worth resisting the urge to inflate it into one. The announcement is a tweet, i.e. secondary; it announces the release but does not describe it. Anyone reporting what v31.1 fixes or changes without reading the actual release notes is guessing. The reply-thread demands about CSAM filtering and soft-fork activation are recurring Bitcoin political fights that get projected onto every release; nothing shows v31.1 addresses them, and we won't imply otherwise. If you run a node, the operative question is what the release notes say — verify the download against the project's signatures before updating, as always.

This is general information, not financial or security advice.