Bitcoin
Bitcoin Core fixes repeated transaction announcements in two releases
Versions 31.3 and 30.5 were released on November 20. They bring the same networking fix to two Bitcoin Core branches, with different changes to their build and test tools.

The same fix on two branches
The Bitcoin Core project released versions 31.3 and 30.5 less than a minute apart on November 20, 2026. Both sets of release notes cite the same change to network message processing. The software processes only distinct announcements when it encounters repeated transaction announcements. The two versions have their own notes and distribution files. They are intended for node operators running different branches of the same software.
A transaction announcement tells another node that a transaction is known. It is part of the way peers relay transactions. A repeated announcement repeats the network signal without creating a new transaction. Reducing redundant work affects how the software receives and processes these messages. The release notes describe no changes to the rules that determine whether transactions or blocks are valid. They also give no figures for any performance gains operators might see.
Compatibility differs by branch
For version 31.3, the project lists testing on Linux kernel 3.17 or later, macOS 14 or later, and Windows 10 version 1903 or later. The version 30.5 notes list the same Linux kernel threshold, macOS 13 or later, and Windows 10 or later. The project says the software may run on other Unix-like systems, which it tests less frequently.
Both releases also change the continuous integration setup. The notes mention changes to the selection of test runners and to the cache used to build Docker images. The 30.5 branch also lists a cache change for test runners and a move to pycapnp 2.2.1. These changes concern the project's build and test environment. The shared networking change is the part that directly concerns how a node processes announcements.
Files distributed by the project
The release announcements direct users to version-specific download directories at bitcoincore.org. The project says the files distributed there are built reproducibly and signed. The notes recommend waiting for a node to shut down completely before replacing its software. They say upgrades from a version that has reached end of support can take time if the data directory needs to be migrated.
Branch choice depends on the version and operating system already in use. The two November 20 releases make the same network change available in the 30 and 31 series. They document the tested systems, build tools, and distribution files separately. The notes give neither a measure of additional Bitcoin network throughput nor a schedule for retiring either branch.
