Ethereum set Medalla’s earliest genesis for August 4

The July 23 record

On July 23, 2020, the Ethereum Foundation set the earliest genesis time for Medalla, a community-maintained, multi-client test network for the proof-of-stake system then commonly called “eth2.” The protocol update assigned `MIN_GENESIS_TIME` the Unix timestamp 1596546000, corresponding to August 4, 2020 at 1:00 p.m. UTC.

That timestamp was a floor, not an unconditional launch appointment. Medalla also needed at least 16,384 validators, representing 524,288 testnet ETH under the 32-ETH-per-validator configuration. If the deposit threshold had not been reached by August 2 at 1:00 p.m. UTC—48 hours before the minimum genesis time—the network would start later. Genesis was to occur 48 hours after both conditions had been satisfied.

The Foundation expected at least four independently developed clients to be fully operational at genesis: Lighthouse, Nimbus, Prysm and Teku. Lodestar was expected to participate in some capacity. The accompanying Medalla repository identified the network with version 0.12.2 of the then-current specification and documented it as a public testnet.

Why Medalla mattered

Ethereum was still secured by proof of work on July 23, 2020. Its proposed proof-of-stake transition depended on multiple software teams implementing the same consensus rules and remaining interoperable under live network conditions. Medalla moved that work beyond earlier networks that the Foundation described as developer-oriented “devnets.” Its health would depend much more heavily on community validators rather than primarily on client teams and Foundation participants.

That made Medalla an operational rehearsal, not merely a date on a roadmap. Deposits, validator setup, key handling, client diversity, peer-to-peer communication, block production, attestations and finality all had to work across separately written programs. A network that could only function under one dominant client would retain a concentrated failure mode; a multi-client network could expose disagreements before production use.

The institutional significance was therefore technical evidence about launch readiness. The July 23 announcement created a public, falsifiable checkpoint: a defined configuration, a participation threshold and named client implementations. It did not establish that the proof-of-stake mainnet was ready, secure under every condition or certain to launch on any later date.

Security testing ran in parallel

The same July 23 update said three deliberately small, single-client attack networks had been launched during that week. Each used four nodes and carried a $5,000 bounty for disrupting finality for at least 16 continuous epochs. The Foundation also reported that a researcher had found a critical Lighthouse discovery bug, while noting that the finding had not stopped testnet finality and that a fix followed.

Those details qualify the headline. Medalla’s schedule reflected progress, but the test program was actively seeking failures. The update also described experimental work toward connecting the proposed proof-of-stake consensus system with the existing Ethereum execution chain. That merger work was presented as a next-stage simulation effort, not as completed integration.

What the record did not show

The announcement did not change Ethereum mainnet consensus on July 23, activate staking with real ETH, or process existing Ethereum applications through Medalla. It also supplied no market dataset from which to infer a price response. Coinburn therefore makes no claim that the update caused an ETH price move; continuous crypto trading and overlapping news would make such attribution unreliable without a specified venue, pair and measurement window.

Contemporaneous reporting described Medalla as the intended final testnet before mainnet, but that label expressed the development plan, not a guarantee that no further rehearsal would be required.

Later context

A December 9, 2020 Ethereum Foundation research update later recorded that the proof-of-stake Beacon Chain launched on December 1, 2020. That subsequent milestone helps establish why the July rehearsal mattered, but it was not certain on July 23 and is not used here to turn a conditional testnet schedule into a foregone conclusion.