EOS jumped as its Ethereum token entered the mainnet transition

EOS was marked at $14.74 in CoinMarketCap’s June 2, 2018 historical snapshot, up 20.44% over the provider’s displayed 24-hour window as the project moved from an Ethereum-based token toward the opening ledger for a proposed EOS blockchain. The snapshot ranked EOS fifth by estimated cryptocurrency market capitalization, at approximately $13.21 billion.

Kraken recorded the same direction but a different magnitude. Its June 2 exchange report displayed EOS at $15.23, up 26.9% for Kraken’s reporting window, with $19.8 million of EOS turnover. That was the largest percentage increase among the 16 assets shown in Kraken’s report and substantially exceeded bitcoin’s 3.20% and ether’s 4.95% gains on the venue.

The move mattered because traders were assigning greater value to EOS during an operationally incomplete transition. EOSIO 1.0 software had been released on June 1, but software publication was not equivalent to an active public blockchain. Token balances still had to be extracted from Ethereum, reproduced by independent launch teams and imported into a candidate network.

Two market records, two measurement windows

CoinMarketCap’s June 2 snapshot reported an EOS price of $14.74, approximately $2.88 billion in 24-hour volume and a 20.44% rolling gain. Bitcoin was marked 1.54% higher and ether 2.11% higher over the same displayed window. Within that dataset, EOS therefore outperformed bitcoin by 18.90 percentage points and ether by 18.33 percentage points, calculated from CoinMarketCap’s published figures.

Those calculations establish relative performance within one provider’s snapshot; they do not establish a universal closing return. Cryptocurrency traded continuously across fragmented venues without a consolidated closing auction. CoinMarketCap does not identify a precise observation time or preserve complete constituent-venue and weighting details on the historical page.

Kraken’s $15.23 EOS mark and 26.9% increase should likewise be treated as venue-specific. Its report covered Kraken markets quoted in crypto, euros, US dollars, Japanese yen, Canadian dollars and British pounds. The retained page does not specify the exact daily cutoff, individual trading pairs or dollar-conversion method behind its summarized volume.

The difference between Kraken’s 26.9% reading and CoinMarketCap’s 20.44% figure is therefore not evidence that either record is necessarily wrong. It illustrates how venue selection, timing and aggregation could produce materially different daily measurements.

The token transition was not yet complete

EOS Authority’s participant-maintained launch timeline records that at 21:59 UTC on June 2, launch teams began retrieving the final Ethereum balance and registration-key data after a 23-hour token freeze. That snapshot was intended to provide the opening allocations for a separately operated EOSIO chain.

The milestone did not make native EOS transfers available. It also did not establish that balances had been independently reproduced, that system contracts were secure or that prospective block producers had agreed on a candidate chain. Those unresolved steps limited what the June 2 rally could reasonably be said to price.

The contemporaneous facts support an association, not a single-cause finding: EOS rose sharply across two provider windows while the anticipated transition entered its snapshot stage. The evidence cannot isolate how much of the move reflected the software release, token-sale completion, speculative positioning, exchange liquidity or expectations surrounding the eventual network.

Why the distinction mattered

EOS combined a large market valuation with an unusual handoff. Block.one developed the software and conducted the token distribution, but outside participants were expected to configure and operate a public blockchain. The market could trade the Ethereum token immediately even though the successor network still depended on coordinated technical and governance decisions.

That gap created execution risk. A faulty snapshot could misstate ownership, competing launch groups could produce incompatible chains, and security testing could delay public access. The June 2 price increase showed strong demand around the transition; it did not verify that any of those risks had been resolved.

Later context

Launch participants agreed on a snapshot on June 3, enabled public transactions on June 10 and crossed the required voting threshold on June 14. These later milestones clarify why June 2 should be recorded as a market rally during the transition, not as the date of a fully activated EOS mainnet.