Geth Consensus Bug Splits Ethereum, Takes Infura Offline

On November 11, 2020, the Ethereum mainnet suffered a network-wide disruption after a consensus-layer flaw surfaced, splitting participants who were still running older versions of the geth client onto a minority chain. Because so many applications depend on those nodes, the fault rippled outward into a cascading failure across the ecosystem.

For most users, the first sign of trouble was the failure of Infura's API. As the Ethereum network's largest node-infrastructure provider, Infura underpins many of the most widely used Web3 products and exchanges, including MetaMask, Uniswap, and Binance. The disruption exposed that Binance either depends on Infura directly or was itself running out-of-date nodes — neither a comfortable position for an exchange of its size.

It isn't unusual that Infura hadn't updated to the newest geth release: absent a hard fork forcing the issue, large infrastructure operators have little incentive to move off a proven, stable build onto an untested one.

The blockchain search and analytics platform Blockchair ran into the same wall, tweeting that its Ethereum explorer was down because of an apparent chain split, with both its own nodes and those of some miners stranded on the minority fork:

We're experiencing an issue with our #Ethereum explorer and working on a fix. It seems like there is a chain split, and some nodes (including ours and some miners') are stuck on a minority chain.

Blockchair's lead developer, Nikita Zhavoronkov, shared the error message his node produced:

########## BAD BLOCK #########

< …>

Error: invalid merkle root (remote: 57cc91ee8b91b956592a27b14386abc2aba723b5f4f9e5d3181ace6b5d3cd433 local: 1f9ee59bfa683a25c7a15b626995a3ad7c58c571b40df96eea31e5c5eed9732d)

Behind the outage sat two separate vulnerabilities in the geth codebase, both uncovered by John Youngseok Yang of Software Platform Lab — work that earned him 20,000 points on the Ethereum Bug Bounty leaderboard. Because publicly discussing consensus bugs on GitHub Issues risks tipping off attackers, the technical specifics have not been disclosed. Mhswende suggested a fuller write-up or DevCon talk on the issue might surface eventually.

To contain the fallout, Ethereum's core developers opted to push through a hard fork. Péter Szilágyi explained the reasoning on Twitter:

It was an "unannounced hard fork" (from a bad chain to the good one). That said, silently fixing a bug dormant for 2+ years has a much lower chance of causing a disruption than raising awareness to it. We strive to minimize potential damage.

For anyone frustrated by Infura going dark, the episode is a reminder that outsourcing node operation means ceding control over how — and when — that infrastructure is run. To its credit, Infura was forthcoming about the incident and moved quickly to resolve it; the service is back online, with ongoing updates posted to its status page.

The episode underscored just how reliant the ecosystem has become on a single provider — a centralized chokepoint sitting in front of a supposedly decentralized system. It's a dynamic both individual users and institutions need to reckon with. Exchanges regarded as top-tier, including Binance and Bithumb, saw their reputations dinged when they had to suspend ETH and ERC-20 withdrawals during the outage — a poor look for platforms expected to be resilient to this kind of disruption.

MetaMask's default routing through Infura meant that when Infura stumbled, the wider Ethereum network effectively idled — gas prices collapsed to just 12 gwei. That is the signature of an unhealthy dependency, and a warning about the damage a similar failure could cause in the future. It raises a broader question: does the industry want to replicate the internet's own history of concentrating power in a handful of centralized gatekeepers — Chrome, Safari, Brave — while the freer, more anonymous corners of the web get pushed to the margins as a barely-accessible "Dark Net"? Crypto shouldn't be allowed to drift toward the same outcome.

David Mihal noted that the outage sent people scrambling for alternative RPC endpoints, and said he had put together ethereumnodes.com as a running list of free public RPC providers and their status. Michael O'Rourke offered a workaround for anyone locked out of MetaMask: switching the RPC provider to Pocket via this endpoint.

Ultimately, any break in consensus is a serious matter — an unannounced hard fork implies these bugs, left unaddressed, could have caused significant harm. Thankfully, between the bounty hunters who found the flaws and the Ethereum developers who moved quickly, no funds or data were lost, and per Zhavoronkov, the eventual fix looks to be a fairly straightforward one.