EOS block producers authorized the mainnet launch sequence

EOS block-producer candidates voted at approximately 01:48 UTC on June 9, 2018 to proceed with the EOS mainnet launch sequence, ending several days of security testing and internal debate over whether the candidate network was ready.

The decision did not make EOS fully operational. By the end of the June 9 coordination call, participating producers were exchanging blocks across an increasingly connected network, but ordinary transactions remained disabled. Public access, token-holder voting and replacement of the appointed launch producers by elected producers still depended on later phases.

That distinction mattered because EOS was attempting an unusual handoff. Block.one had developed and released the open-source EOSIO software, but its repository explicitly said the company was not launching or operating the public blockchains built with it. Candidate block producers therefore had to organize the network, reconcile the token snapshot, agree on one candidate chain and decide collectively when to expose it to users.

From repeated delays to a go decision

The EOS Authority launch tracker records unanimous no-go decisions on June 7 and June 8. Testing included software and security work, and the launch process was designed to repeat that stage if a major defect emerged. The June 9 call also considered EOSIO version 1.0.2, a software release referenced in the launch record shortly before voting began.

At 01:48 UTC, the tracker described a resounding go decision. CoinDesk reported that the vote was unanimous or nearly unanimous but noted that moderators did not announce a final numerical tally. That limitation is important: the surviving evidence establishes overwhelming approval to proceed, but it does not support an exact vote count or participation percentage.

The approved plan called for appointed block producers to begin the next phase at 13:00 UTC. The launch record says producers were receiving blocks and meshing their nodes during that session. At 13:34 UTC, blocks were circulating among connected producers while transactions remained switched off.

What had—and had not—launched

By 13:52 UTC on June 9, participants had agreed to continue validating the chain and defer opening it to the public until after another coordination call on June 10. Token holders therefore could not yet treat the candidate network as an unrestricted, activated blockchain.

The published launch process imposed an additional threshold after public access: 15% of EOS tokens had to be staked and used in producer voting before the network would be considered activated. At that point, the appointed launch producers were supposed to give way to the elected block producers. Neither public transaction access nor that voting threshold had been completed on June 9.

The defensible event-day description is consequently narrower than “EOS went live.” June 9 established collective authorization to proceed and produced an interconnected, block-producing candidate network. It did not establish public usability, elected governance, stable application operation or completion of the broader launch.

Why the decision mattered

The go vote tested whether a geographically dispersed group of prospective validators could coordinate a public network without the software developer operating it directly. It also exposed the governance burden embedded in EOS’s delegated proof-of-stake design before token holders had elected the permanent producer set.

For exchanges, wallet providers and token holders, the sequence created operational uncertainty. A software release, a producing chain, an open network and an activated governance system were four different milestones. Treating them as one event could lead users to assume transfers or voting were available before the responsible producers had enabled them.

No EOS price movement is attributed to the vote. The cited records do not supply a standardized exchange, trading pair, UTC observation window or methodology adequate for calculating an event-day return or assigning causation.

Later context

The participant-maintained timeline records that public transactions were enabled at 13:00 UTC on June 10, 2018. It records the 15% voting threshold and transition to elected producers on June 14. Those subsequent milestones clarify the launch sequence but were not completed facts on June 9.