Bitcoin Core 29 · Version Status

Bitcoin Core 29 End of Life Date

Bitcoin Core 29 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Bitcoin Core 29 is actively supported. EOL date: Already EOL.
EOL Date
Already EOL
Supported
Latest Release
29.3
Standard release
Release Date
Apr 14, 2025
Bitcoin Core 29 series
← Bitcoin Core 28 All Bitcoin Core versions Bitcoin Core 30 →
All Bitcoin Core Versions
VersionLatestEOL DateStatus
0.8 0.8.6 Dec 31, 2015 EOL
0.9 0.9.5 Feb 28, 2016 EOL
0.10 0.10.5 Feb 28, 2017 EOL
0.11 0.11.3 Aug 1, 2017 EOL
0.12 0.12.1 Feb 28, 2018 EOL
0.13 0.13.2 Aug 1, 2018 EOL
0.14 0.14.3 Feb 1, 2019 EOL
0.15 0.15.2 Aug 1, 2019 EOL

What does Bitcoin Core 29 end of life mean?

When Bitcoin Core 29 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Bitcoin Core 29 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Bitcoin Core 31 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Bitcoin Core 29 reach end of life?
Bitcoin Core 29 has already reached end of life.
Is Bitcoin Core 29 still supported?
Yes, Bitcoin Core 29 is currently supported. The EOL date is Already EOL.
What should I upgrade to from Bitcoin Core 29?
The recommended upgrade from Bitcoin Core 29 is Bitcoin Core 31 — the latest actively supported version. Check the Bitcoin Core full timeline for all supported versions.
What are the security risks of running Bitcoin Core 29 past EOL?
When Bitcoin Core 29 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Bitcoin Core should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →