Ethereum Merge Testing and the Risks of Total Terminal Difficulty
Summary
This report summarizes Ethereum core developer discussions about testing the planned transition from proof of work to proof of stake. It explains the use of total terminal difficulty (TTD) to trigger the Merge and describes how a malicious miner manipulated the smaller Ropsten testnet’s hash rate, causing TTD to be reached before the Beacon Chain was ready. Developers responded by replacing the initial threshold with a much higher value and planned a later override after network preparation.
The report also describes plans to rehearse similar activation procedures on later testnets and potentially on mainnet, along with the coordination needed among client teams, validators, and node operators. The incident illustrates that TTD timing is uncertain and more vulnerable to manipulation on low hash rate testnets than on mainnet. The account is a snapshot of meetings and anticipated steps in 2022; it does not establish how later deployments performed.
Key ideas
- TTD was used to trigger the Merge because a simple block height could be manipulated by miners with minority hash power.
- Ropsten’s low hash rate made it vulnerable to a sudden increase that caused premature TTD activation.
- Developers raised the threshold and planned to issue a more accurate value after the Beacon Chain was running.
- Repeating activation procedures across testnets was intended to prepare client teams, users, validators, and node operators.
- Merge timing based on TTD remained an estimate and could differ from the expected date.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.