EOS launch participants agreed on the mainnet’s opening ledger

At 09:35 UTC on June 3, 2018, the EOS Mainnet Launch Group and other launch participants reached consensus on the account snapshot to use in bootstrapping a proposed EOS mainnet. The agreement supplied prospective block producers with a common opening ledger derived from the final state of the EOS token contract on Ethereum.

The milestone was narrower than a mainnet launch. EOS Authority’s participant-maintained timeline records that the snapshot process began after the Ethereum-based tokens were frozen. It says EOS Authority published the first final snapshot files at 00:35 UTC on June 3 and that two other block-producer teams had recreated the snapshot by 02:58 UTC. Consensus on the file followed at 09:35 UTC.

Those reproductions mattered because a faulty balance or key mapping could have carried errors into every chain initialized from the file. Agreement established the input for the next stage; it did not prove that every account was correct, guarantee that one candidate chain would prevail or make native EOS transactions available.

A ledger before a network

Block.one developed EOSIO and released version 1.0 as open-source software immediately before the snapshot process, but community participants were responsible for configuring and launching a public chain. The release repository documented bootstrapping controls such as actor and contract whitelists and blacklists, which were intended to limit the attack surface while core contracts were tested.

The separation between software, ledger and network was central to the June 3 event. EOSIO 1.0 supplied software. The snapshot supplied proposed account allocations and registered keys. Prospective block producers still had to import and verify those records, inspect system contracts, secure their nodes, agree on a candidate chain and decide when public access could begin.

Contemporaneous reporting subsequently confirmed that competing groups were testing different chain configurations from the snapshot. That did not make the June 3 agreement meaningless: without a shared ownership record, competing boot procedures could also have produced conflicting token allocations. The snapshot consensus reduced one source of disagreement while leaving chain selection and security testing unresolved.

The market remained exposed to launch risk

Kraken’s daily market report for June 3 displayed EOS at $14.61, down 4.07% for the report’s daily measurement window, with $18.6 million in reported EOS trading volume on the exchange. EOS ranked behind only ether and bitcoin by volume in that Kraken report, illustrating the financial significance attached to a launch process that was still incomplete.

Those figures are venue-specific rather than a consolidated crypto-market close. Kraken’s retained report does not specify an EOS/USD closing auction, the precise cutoff convention behind the displayed daily change or how trading across quote currencies was converted into the dollar-denominated volume. The figures therefore describe Kraken’s June 3 summary, not a universal EOS price or audited global turnover.

The negative daily reading also cannot establish that snapshot work caused the move. Cryptocurrency traded continuously across exchanges, while expectations about the token sale, software release and anticipated network launch were already circulating. The defensible conclusion is simply that substantial trading continued while participants were still assembling the network’s initial state.

Why the snapshot decision mattered

EOS was attempting to convert the record produced by a nearly yearlong Ethereum token distribution into the genesis state of a separately operated blockchain. June 3 demonstrated that prospective validators could independently reproduce and then agree on the ledger input. It also exposed the institutional burden of the design: coordination that a single network operator might perform internally instead required agreement among organizations seeking future block-production roles.

For token holders, the distinction was operationally important. Snapshot inclusion did not mean that native tokens could be transferred, that voting had begun or that elected producers were running the network. Describing EOS as fully live on June 3 would collapse several later milestones into one and overstate what participants had completed.

Later context

The launch tracker records that two candidate chains completed the boot phase on June 4. Producers authorized the launch sequence on June 9, public transactions opened on June 10, and the required token-voting threshold was reached on June 14. Those later events clarify the process but were not completed facts on June 3.