Bitcoin Core speeds up AI-era security fixes as 43.6% of surveyed nodes run unsupported software, a share that could surpass 50% after its next major release.

Bitcoin Core merged a policy amendment on Oct. 22 that lets developers backport fixes for easily rediscovered vulnerabilities to every maintained release line and publish an advisory alongside them.

A network snapshot from Oct. 18 shows that 3,671 of 8,422 self-reported Bitcoin Core peers (43.6%) ran release lines that had already reached end of life.

The count comes from connected public peers in the Karlsruhe Institute of Technology's Bitcoin network monitor and reflects maintenance eligibility.

A node on an unsupported version can keep validating blocks correctly, and the figure doesn't measure compromise.

Under the old policy, medium- and high-severity vulnerabilities stayed under embargo until two weeks past the end of life of the last affected release.

That can mean about a year between a fix and the publication of its details. Long embargoes also discouraged openly backporting a fix, since the backport itself could reveal the flaw.

Antoine Poinsot argued in the Oct. 22 announcement that the arrangement fits badly with bugs that AI systems can rediscover:

“The embargo period achieves little but it delays the availability of a fixed release.”

Developers can now mark a flaw as easily discoverable during triage, a test based on how readily it can be found or rediscovered, including by large language models.

Those fixes go to all maintained major lines through point releases, with an advisory published alongside, and other vulnerabilities follow the standard severity schedule.

Source link