Just two days after Ethereum activated the Spurious Dragon hard fork, the network faced an unexpected crisis that exposed the fragility of its consensus mechanism. On November 24, 2016, a critical bug in Geth — the most widely used Ethereum client — caused a network fork at block #2,686,351, temporarily splitting the blockchain into two incompatible chains and sending shockwaves through the growing Ethereum community.
TL;DR
- A consensus bug in Geth v1.4.19 and v1.5.2 caused an unintentional chain fork at block #2,686,351 on November 24, 2016
- The bug prevented Geth from reverting empty account deletions when transactions ran out of gas
- Approximately 165 blocks were mined on the now-abandoned chain before the issue was resolved
- Geth 1.5.3 was released as an emergency fix to restore network consensus
- Ethereum traded at approximately $9.23, down nearly 6% on the day amid the uncertainty
The Spurious Dragon Hard Fork and Its Unintended Consequences
The Spurious Dragon hard fork, activated on November 22, 2016, was designed to address several lingering issues on the Ethereum network. Central to this upgrade was EIP 161, which introduced a consensus rule requiring that empty accounts touched by transactions would be permanently removed from the blockchain. This was a direct response to a series of attacks — later attributed to a blackhat hacker operating since the Ethereum Devcon2 conference in Shanghai — that had exploited mispriced EVM opcodes to create approximately 19 million empty accounts, bloating the blockchain and burdening nodes with unnecessary computational overhead.
The EIP 150 hard fork on October 18, 2016, had already addressed the mispriced opcodes that enabled these attacks, but the cleanup of existing empty accounts required the more aggressive approach implemented in Spurious Dragon. By November 24, roughly 4 million of those empty accounts had already been cleared through the new consensus rules.
The Consensus Bug That Split the Chain
The vulnerability emerged from an intricate interaction between Geth’s journaling mechanism and the new empty account deletion rules. Specifically, when a transaction that deleted empty accounts ended with an out-of-gas exception, Geth failed to revert those deletions — violating a fundamental invariant of the Ethereum Virtual Machine that state changes should always be rolled back when a transaction runs out of gas.
This seemingly edge-case scenario had real consequences. At 14:12:07 UTC on November 24, Geth and Parity clients began producing different blocks, creating two separate versions of the Ethereum blockchain. The divergence was not immediately apparent to all users, and approximately 165 blocks were mined on the chain that would ultimately be abandoned.
The Ethereum Foundation’s official security alert noted: “Geth was failing to revert empty account deletions when the transaction causing the deletions of empty accounts ended with an out-of-gas exception.” A related but distinct issue was also identified in the Parity client, where it “incorrectly failed to revert empty account deletions in a more limited set of contexts involving out-of-gas calls to precompiled contracts.”
Emergency Response and Network Recovery
The Ethereum development team responded swiftly, releasing Geth version 1.5.3 to patch the journaling issue and repair the fork. The updated client automatically reverted the blockchain from the point of the fork, even for nodes that had already synced past the divergence point. Users of the Mist wallet received the update through the built-in auto-update mechanism.
Transactions broadcast during the fork period were largely present on both chains, minimizing disruption for regular users. However, mining rewards and transaction fees earned on the abandoned chain were permanently lost — a costly lesson for miners who had not updated their clients promptly.
A Community Warning That Went Unheeded
In a remarkable twist, a community member had raised concerns about this exact class of vulnerability during the discussion of EIP 158, the precursor to EIP 161. They asked: “If empty accounts are deleted even in the case of an EVM exception, would that not break the guarantee that EVM exceptions revert the state back as if the transaction was never made?” The question proved prophetic, highlighting the complexity of implementing consensus-level changes on a live blockchain with billions of dollars at stake.
Why This Matters
The November 24 consensus bug serves as a stark reminder that even carefully planned hard forks can introduce unexpected vulnerabilities. For a network like Ethereum, which was still in its early stages of adoption with a market capitalization of under $800 million at the time, such incidents tested the resilience of both the technology and the community. The event reinforced the Ethereum Foundation’s recommendation that exchanges and high-value users run multiple clients and implement automatic safeguards when chains diverge by more than 10 blocks — advice that remains relevant as the Ethereum ecosystem continues to grow in complexity. Bitcoin, trading at approximately $740 during this period, remained unaffected, highlighting the relative stability of the more mature network.
Disclaimer: This article is for informational purposes only and does not constitute financial advice. Cryptocurrency investments carry significant risk. Always conduct your own research before making investment decisions.