Block.one Closed the EOS Token Sale as EOSIO 1.0 Arrived

Block.one’s nearly yearlong distribution of Ethereum-based EOS tokens closed on June 1, 2018 as the company delivered EOSIO 1.0, the open-source software intended to support independently operated blockchains. The paired milestones ended an extraordinary fundraising campaign and shifted attention from selling tokens to whether outside participants could securely assemble a functioning network.

The distinction mattered immediately: releasing EOSIO software did not launch the EOS blockchain. Block.one supplied code that prospective operators could inspect, configure and use, while community groups still had to agree on an opening account ledger, initialize a candidate chain, test its contracts and coordinate block producers.

GitHub’s retained release record timestamps EOSIO v1.0.0 at 23:01 on June 1. Its notes described an optional peer-to-peer networking plugin, controls for whitelisting or blacklisting actors and contracts, and experimental support for keeping block-signing keys outside the process executing smart-contract code. Those features addressed practical bootstrapping and security concerns, but the release notes did not certify that a public network was ready for unrestricted use.

A token sale reached its endpoint

The EOS distribution had begun on June 26, 2017. Participants sent ether through a series of auction-like periods for ERC-20 tokens recorded on Ethereum. The tokens were designed as an interim instrument rather than the native asset of an already operating EOSIO chain.

Contemporaneous CNBC reporting calculated that the offering had received ether worth approximately $4.1 billion as of May 31, using a quoted exchange rate of $576 per ether. That was an event-period conversion, not an audited final dollar balance. The offering received ETH rather than dollars, the sale had not yet completed at CNBC’s measurement point, and the dollar value of the proceeds changed with ether’s market price.

The scale placed unusual institutional weight on the software handoff. Purchasers had funded a private company developing open-source infrastructure, but owning the Ethereum token did not confer equity in Block.one. Nor did the end of the distribution prove that a successor blockchain would launch securely, achieve adoption or preserve the market value assigned to EOS.

Code release was not network activation

A same-day report from Blockchain Beach emphasized that Block.one would not itself operate an official public mainnet. Competing community groups could use the released software, and token holders might ultimately have to distinguish among candidate networks. That structure left consensus over the opening ledger, system contracts, governance rules and block-producer set unresolved on June 1.

EOSIO’s release controls also showed why activation required more than publishing code. Whitelists could restrict the contracts or accounts permitted during bootstrapping, while external block signing could reduce exposure of validator keys. Both were defensive tools; neither guaranteed correct configuration, secure operators or agreement over which chain should become economically dominant.

Accordingly, the defensible June 1 conclusion is narrow. Block.one completed the token-distribution phase and made EOSIO 1.0 available, creating the technical basis for others to attempt a launch. Native EOS transfers, elected production and an open public network remained future milestones.

Later regulatory and launch context

A September 30, 2019 Securities and Exchange Commission order later established a more precise record: Block.one distributed 900 million ERC-20 tokens from June 26, 2017 through June 1, 2018, reserved another 100 million founder tokens and raised ether worth several billion dollars. The SEC found that the offering was an unregistered securities sale and imposed a $24 million civil penalty; Block.one settled without admitting or denying the findings. That legal conclusion was not available on June 1, 2018.

The same SEC order records June 14, 2018 as the launch date of the first EOSIO-based blockchain. That later milestone confirms why the June 1 software release and token-sale close should not be described retrospectively as an already completed mainnet launch.