The incident record
Bitcoin under stress
Every time Bitcoin broke, split by accident or came close to it, and how it held. Block by block, from primary sources, with no simulations: only what happened.
Swipe the chart for 2018–2026 →
Stale blocks per month: valid blocks that lost a race or belonged to a chain that split off. The longer the stroke, the more were recorded (square-root scale). Coloured dots mark the incidents below. Busy early years reflect slow block propagation; after 2016 the line goes quiet. 358 of 4,194 records have no timestamp and are not drawn.
The incidents
Each dossier gives the block height, a timeline in UTC, what broke, how it was fixed and the price on Bitstamp at that minute. Contested splits, where people chose to leave, are told on the Bitcoin forks page and only linked here.
The value overflow: 184 billion bitcoin out of nothing
A transaction in block 74,638 created more than 184 billion bitcoin. A fix was out the same evening, and within a day the chain without the bad block had overtaken it.
Read the dossier →Accidental chain splitMarch 2013: the accidental chain split
A block that Bitcoin 0.8 accepted and older versions could not process split the network for about six hours, until large pools switched back to the older software.
Read the dossier →Mining failureJuly 2015: pools mining on an invalid block
When the BIP66 soft fork took effect, a small miner produced an invalid block, and large pools that did not check blocks before building on them extended it. Two short invalid chains followed.
Read the dossier →Software vulnerabilityCVE-2018-17144: the inflation bug that was never used
A bug in Bitcoin Core would have let a miner spend the same coins twice in one block, creating new bitcoin. It was reported, patched and released within about 30 hours; no exploitation is known.
Read the dossier →Contested splitBitcoin Cash splits off
A planned hard fork by the big-block camp; the stale-block data records 18 blocks from 18:12 UTC that day.
The full story on Bitcoin forks →Contested splitBIP-110 nodes split off
Nodes enforcing a soft fork that almost no miner followed; the stale-block data records 8 blocks of that chain.
The full story on Bitcoin forks →Every disclosed Bitcoin Core vulnerability
As published by the Bitcoin Core project, newest first. Most were fixed quietly and disclosed later, under the project’s security disclosure policy; severity is the project’s own rating. Updated weekly; last check 2026-11-13.
| Disclosed | Advisory | Severity | Summary (the advisory’s own) |
|---|---|---|---|
| Nov 10, 2026 | CVE-2025-62859 - Block processing stall via witness malleation | Medium | Block processing may be stalled by a peer announcing a compact block with a malleated witness |
| Nov 10, 2026 | CVE-2025-62860 - Inbound Tor connections wrongly receive -whitelist permissions | Medium | Various DoS and privacy protections were lifted for incoming Tor connections on affected nodes. |
| Nov 10, 2026 | CVE-2025-62861 - Block template creation halted by TRUC sibling eviction during reorg | High | A chain reorganization could trigger erroneous "sibling eviction" of TRUC (v3) transactions, corrupting the mempool so an affected node can no longer create block templates until it is restarted. A fix was released on October 10th 2025 in Bitcoin Core v30.0. |
| Oct 28, 2026 | CVE-2026-117349 - Slow unbounded memory growth on paused pre-BIP31 peers | Medium | Bitcoin Core queues announcements for all peers, including paused ones. Pre-BIP31 peers could stay paused forever and let the queue grow unboundedly. |
| Oct 28, 2026 | CVE-2026-117350 - Unbounded memory growth through TCP urgent data on non-Linux systems | Medium | On platforms other than Linux, a malicious peer could cause a node to run out of memory by sending TCP urgent (out-of-band) data. |
| Oct 28, 2026 | CVE-2026-117346 - Undo file overflow under extreme conditions | Low | After filling thousands of blocks in preparation, a miner able to trigger a precisely timed short reorg following a specific sequence of blocks could crash some nodes by corrupting their undo data. A fix for 64-bit systems was released in Bitcoin Core versions 29.5, 30.4, 31.2 and 32.1; 32-bit systems and nodes storing blocks on FAT32 remain affected. |
| May 5, 2026 | CVE-2024-52911 - Script Interpreter Remote Crash | High | A specially-crafted block can be used to remotely crash a Bitcoin Core node by exploiting a use-after-free in its script interpreter. |
| Oct 24, 2025 | CVE-2025-46597 - Highly unlikely remote crash on 32-bit systems | Low | An attacker could produce a block that crashes nodes running on 32-bit systems in a rare edge case. A fix was released on October 10th 2025 in Bitcoin Core v30.0. |
| Oct 24, 2025 | CVE-2025-46598 - CPU DoS from unconfirmed transaction processing | Low | Specially crafted invalid unconfirmed transactions could cause unnecessary resource usage. A fix was released on October 10th 2025 in Bitcoin Core v30.0. |
| Oct 24, 2025 | CVE-2025-54604 - Disk filling from spoofed self connections | Low | An attacker could cause a victim node to fill up its disk space by repeatedly faking self-connections over a long time. A fix was released on October 10th 2025 in Bitcoin Core v30.0. |
| Oct 24, 2025 | CVE-2025-54605 - Disk filling from invalid blocks | Low | An attacker could cause a victim node to fill up its disk space by repeatedly sending invalid blocks. A fix was released on October 10th 2025 in Bitcoin Core v30.0. |
| Apr 28, 2025 | CVE-2024-52919 - Remote crash due to addr message spam (part 2) | Low | An attacker could crash a node by spamming it with `addr` messages for a very long time. A fix was released on April 14th 2025 in Bitcoin Core v29.0. |
| Nov 5, 2024 | CVE-2024-52922 - Hindered block propagation due to stalling peers | Medium | A peer could hinder block propagation by announcing blocks first and then simply withholding the block. |
| Oct 8, 2024 | Disclosure of CVE-2024-35202 | High | An attacker could remotely crash a Bitcoin Core node by triggering an assertion in the blocktxn message handling logic. |
| Oct 8, 2024 | Disclosure of DoS due to inv-to-send sets growing too large | Medium | The inv-to-send sets could grow too large to a point where the time spent sorting the sets would affect the node's ability to communicate with its peers. |
| Oct 8, 2024 | CVE-2024-52921 - Hindered block propagation due to mutated blocks | Medium | A peer could hinder block propagation by sending mutated blocks. |
| Sep 18, 2024 | CVE-2019-25220 - Memory DoS due to headers spam | High | An attacker could spam a Bitcoin Core node with low-difficulty headers chains, which could be used to remotely crash it. |
| Jul 31, 2024 | CVE-2024-52919 - Remote crash due to addr message spam | High | Nodes could be spammed with addr messsages, which could be used to crash them. A fix was released on September 14th, 2021 in Bitcoin Core v22.0. |
| Jul 31, 2024 | CVE-2024-52917 - Infinite loop bug in the miniupnp dependency | Low | Nodes could be crashed by a malicious UPnP device on the local network. A fix was released on September 14th, 2021 in Bitcoin Core v22.0. |
| Jul 3, 2024 | CVE-2024-52918 - Crash using malicious BIP72 URI | Medium | The BIP70 implementation in Bitcoin-Qt could silently crash when opening a BIP72 URI. A fix was released on June 3rd, 2020 in Bitcoin Core 0.20.0. |
| Jul 3, 2024 | CVE-2024-52920 - DoS using huge GETDATA messages | Low | A malformed `GETDATA` message could trigger 100% CPU usage on the receiving node. A fix was released on June 3rd, 2020 in Bitcoin Core 0.20.0. |
| Jul 3, 2024 | CVE-2024-52916 - Memory DoS using low-difficulty headers | Medium | Nodes could be spammed with low-difficulty headers, which could be used to crash it. A fix was released on September 14th, 2017 in Bitcoin Core 0.15.0. |
| Jul 3, 2024 | CVE-2024-52915 - Memory DoS using huge INV messages | Medium | Nodes would allocate up to 50 MB of memory per attacker sending a malicious `INV` message. A fix was released on June 3rd, 2020 in Bitcoin Core 0.20.0. |
| Jul 3, 2024 | CVE-2024-52914 - Significant DoS due to orphan handling | High | A node could be stalled for hours when receiving a specially crafted unconfirmed transaction. A fix was released on May 18th, 2019 in Bitcoin Core 0.18.0. |
| Jul 3, 2024 | CVE-2024-52912 - Netsplit due to timestamp adjustment | Medium | A node could be split from the network when attacked by its first 200 peers. A fix was released on January 15th, 2021 in Bitcoin Core version 0.21.0. |
| Jul 3, 2024 | Disclosure of CVE-2020-14198 | High | Nodes could be subject to CPU and memory DoS when attacked by lots of distinct IPs. A fix was released on August 1st, 2020 in Bitcoin Core 0.20.1. |
| Jul 3, 2024 | CVE-2024-52913 - Censorship due to transaction re-request handling | Medium | Nodes could be prevented from seeing specific unconfirmed transactions by a malicious peer. A fix was released on January 14th, 2021 in Bitcoin Core 0.21.0. |
| Jul 3, 2024 | Disclosure of CVE-2015-3641 | Medium | Attackers sending large incomplete messages would cause high memory usage. A fix was released on April 27th, 2015 in Bitcoin Core 0.10.1. |
| Jul 3, 2024 | CVE-2015-20111 - Remote code execution due to bug in miniupnpc | Medium | A bug in the miniupnpc library could have led to a remote code execution in Bitcoin Core. A fix was released on October 15th, 2015 in Bitcoin Core 0.11.1. |
| Nov 8, 2019 | Disclosure of CVE-2017-18350 | not stated | Nodes were potentially vulnerable to a buffer overflow by malicious SOCKS servers. A fix was released on November 6th, 2017 in Bitcoin Core version 0.15.1. |
| Sep 20, 2018 | Disclosure of CVE-2018-17144 | not stated | Bitcoin Core was vulnerable to a DoS and inflation attack. A fix was released on September 18th, 2018 in Bitcoin Core versions 0.16.3 and 0.17.0rc4. |
The longest runs of stale blocks
Heights where competing blocks were recorded several blocks in a row. A long run means two chains grew side by side for a while.
| Heights | Blocks | First block | What it was |
|---|---|---|---|
| 225,430–225,461 | 32 | Mar 11, 2013, 22:39 UTC | The March 2013 chain split 24 blocks were orphaned before the chains rejoined at 225,454; the data also holds stale blocks at the heights just after |
| 478,559–478,576 | 18 | Aug 1, 2017, 18:12 UTC | Bitcoin Cash splits off |
| 222,562–222,572 | 11 | time unknown | Not explained in our sources |
| 961,632–961,639 | 8 | Aug 8, 2026, 20:12 UTC | The BIP-110 minority chain |
| 213,277–213,281 | 5 | time unknown | Not explained in our sources |
| 213,272–213,275 | 4 | Dec 23, 2012, 06:44 UTC | Not explained in our sources |
How this record is made
Only what happened
Every fact on these pages comes from a source linked beside it, primary sources first: BIPs, release notes, project alerts and the original reports. Where a detail could not be confirmed, it is left out.
What counts as an incident
A bug that broke Bitcoin’s rules, an accidental split of the chain, or a failure that put users on an invalid chain. Contested splits are on the forks page; exchange hacks and price crashes are on the crashes page.
Stale blocks are an incomplete record
The data set collects blocks seen by contributors’ own nodes, so it is not complete, especially before 2015. Blocks that break Bitcoin’s rules, such as those of July 2015, are usually not in it.
Prices at the moment
Dossiers show the last Bitstamp trade at the minute an incident began and the range over the next 24 hours, from the Time Machine data. Before 2012 only first-of-month prices exist.
Data and licences
Use our data. The incident record and the monthly stale-block counts are free to reuse under CC BY 4.0. Credit “Bitcoin Years, Bitcoin under stress” with a link to this page. Downloads: incidents.csv (each incident with its block, start time and primary source) · stale-monthly.csv (stale blocks per month). The advisory summaries belong to the Bitcoin Core project and are not covered.
Bitcoin Years. (2026). Bitcoin under stress: incident record and monthly stale blocks [Data set; stale blocks from bitcoin-data/stale-blocks, CC0]. CC BY 4.0. https://bitcoinyears.com/bitcoin-under-stress/
Sources. Stale blocks: bitcoin-data/stale-blocks, data CC0 1.0. Vulnerabilities: Bitcoin Core security advisories (titles, dates and severities as published; summaries are each advisory’s own excerpt). Copies, refreshed weekly: stale.json · advisories.json. Prices: Bitstamp BTC/USD via the Time Machine. Check today’s block 74,638 yourself: Proof of history.