·
·
2 min read
Bitcoin Core developers merged a policy amendment on Oct. 22 that permits the backporting of fixes for easily rediscovered vulnerabilities to every maintained release line. The amendment also allows developers to publish an advisory alongside these backported fixes.
The policy change addresses a significant portion of the network running outdated software. A network snapshot taken on Oct. 18 indicated that 3,671 of 8,422 self-reported Bitcoin Core peers were operating release lines that had already reached end of life. This figure represents 43.6% of the surveyed peers.
Policy Amendment Details
The merged amendment specifically targets vulnerabilities that are easily rediscovered. By allowing fixes for these specific issues to be backported to all maintained release lines, the development team aims to reduce the security risk associated with nodes that have not upgraded to the latest version. The inclusion of a published advisory alongside the fixes provides a formal notification mechanism for users running older software.
The policy does not extend to all types of vulnerabilities or changes. It is limited to fixes for issues that meet the criterion of being easily rediscovered. This distinction ensures that the backporting process remains manageable and focused on immediate security threats rather than broader feature updates or complex architectural changes.
Network Snapshot Data
The data supporting the urgency of the policy change comes from a snapshot of the Bitcoin network taken on Oct. 18. The survey identified 8,422 self-reported Bitcoin Core peers. Of this total, 3,671 peers were found to be running release lines that had already reached end of life. The precise percentage of peers running unsupported versions was calculated at 43.6%.
Running end-of-life release lines means that these nodes are no longer receiving security updates or maintenance from the development team. Without the ability to backport specific fixes, these nodes remain exposed to known vulnerabilities that have been patched in newer versions. The new policy provides a pathway to address this exposure for a significant segment of the network without requiring a full upgrade to the latest release.
Frequently Asked Questions
What does the new Bitcoin Core policy allow developers to do?
The policy amendment merged on Oct. 22 allows developers to backport fixes for easily rediscovered vulnerabilities to every maintained release line. It also permits the publication of an advisory alongside these backported fixes.
How many Bitcoin Core peers were running unsupported versions in the Oct. 18 snapshot?
The snapshot showed that 3,671 of 8,422 self-reported Bitcoin Core peers, or 43.6%, were running release lines that had already reached end of life.
