EIP-2387 Muir Glacier hard fork ("Hardfork Meta: Muir Glacier")

Final · Consensus & staking · EIP status Final · created 2019-11-22

This is a meta EIP that compiles the contents of the 'Muir Glacier' hard fork, which delays the slowdown in block production caused by the difficulty bomb (ice age). It activated at mainnet block 9,200,000, and the only change it includes is EIP-2384.

Why it is needed

Ethereum uses a difficulty retargeting mechanism that raises mining difficulty when blocks come too fast and lowers it when they come too slow, keeping block time around 13 to 14 seconds. However, this mechanism also contains an element called the 'difficulty bomb' or 'ice age'. Every 100,000 blocks, it artificially adds a small amount to the difficulty, and at some point the retargeting mechanism can no longer keep up with this increase, causing the network-wide block time to noticeably lengthen. The problem is that this bomb is intertwined with the complex algorithm that regulates block time. Because two mechanisms with entirely different purposes are mixed together, it is very difficult to simulate or predict when and how strongly the bomb will take effect. Muir Glacier is a hard fork that pushes the bomb back as far as reasonably possible while buying time to fix this design problem more fundamentally.

What changes

Today

After EIP-2387

Who is affected

In depth

The only included EIP is EIP-2384

This fork's codename is Muir Glacier, and the only change it includes is EIP-2384 (Istanbul/Berlin Difficulty Bomb Delay). As a meta EIP, it specifies EIP-1679 (the Istanbul hard fork meta EIP) and EIP-2384 under requires. In other words, this fork was created solely to handle the difficulty bomb right after the Istanbul fork.

Activation blocks

Activates at Block >= 9,200,000 on mainnet and Block >= 7,117,117 on the Ropsten testnet. Kovan, Rinkeby, and Görli are marked N/A, with no activation block specified.

The design problem of the ice age

The difficulty bomb is intertwined with the difficulty retargeting algorithm that regulates block time. Because two mechanisms with entirely different purposes sit inside one mechanism, simulating or predicting the bomb's effect requires assuming future mainnet difficulty and estimating how difficulty changes affect both the bomb and block time together. The source states that any future design improvement should satisfy two conditions: it should be easy to model the effect on the network, and it should be easy to predict when it will occur.

The ice age's original intent

The source lists four original intentions for the bomb: preventing unintended fork chains from growing large at upgrade time, encouraging timely upgrades on the path to Eth 2.0, giving the community repeated opportunities to reconfirm consensus and letting those who want to fork have that chance, and checking core developers from freezing client code without community consent. The source adds that this is not a device to prevent the 'freedom to fork', and that in practice, as with Ethereum Classic, one can fork by patching the client to counter the bomb.

Two long-term resolution directions

This fork is a temporary measure that buys time by delaying the bomb, and during that period it proposes two solutions to review: fixing the mechanism so the bomb's behavior becomes predictable, or removing the ice age entirely. The source states that either approach first requires reconfirming and clarifying the community's priorities and the bomb's intent.

PoA testnets and issuance

Muir Glacier does not activate on PoA (Proof of Authority) chains, so it has no effect on forkid (EIP-2124). Also, past hard forks that delayed the bomb included changes reducing the block reward from 5 ETH to 3 ETH and then to 2 ETH, but this time there is no issuance change and the block reward remains at 2 ETH.

Original EIP · ← EIPs