TRON Began Migrating TRX Away From Ethereum

TRON began its exchange-mediated TRX token migration on June 21, 2018, starting a five-day process intended to replace the project’s Ethereum-based ERC-20 token with a native asset on the TRON network.

The transition mattered because it moved TRX toward settlement on infrastructure controlled by TRON’s own protocol rather than Ethereum. It also placed cryptocurrency exchanges at the center of a technically and operationally sensitive conversion involving an asset that CoinMarketCap ranked tenth by circulating market capitalization on June 21.

The verified development was the beginning of migration—not the creation of TRON’s genesis block. TRON’s technical schedule said its mainnet remained in a testing period through June 24, with a data wipe planned before the genesis block’s scheduled launch at 10:00 a.m. GMT+8 on June 25.

Exchanges became the migration bridge

TRON’s instructions called for participating exchanges to transfer users’ ERC-20 TRX to the project. TRON would burn the received Ethereum tokens and send native TRX back to the exchanges, which would update their systems to support the new network’s wallet functions.

The operating timetable suspended TRX withdrawals from June 21 through June 24, all in GMT+8. Both deposits and withdrawals were to be unavailable on June 25, with service expected to resume on June 26. TRON said exchanges did not need to suspend trading or take a balance snapshot.

Bitfinex published a matching timetable. The exchange said it would handle the conversion automatically and credit customers with native TRX in equal proportion to their ERC-20 holdings. Trading would remain open while withdrawals were restricted. That arrangement reduced the steps required of exchange customers, but it also required them to depend on centralized venues to execute and account for the protocol change correctly.

TRON’s June 20 operational notice published designated Ethereum addresses for exchanges and warned individual holders not to transfer tokens to them directly. The notice demonstrates that project-controlled migration infrastructure existed before the June 21 start. It does not establish how much TRX had actually entered the process by the end of June 21.

A top-ten asset changed settlement systems

CoinMarketCap’s June 21 historical snapshot listed TRX at $0.04862 and ranked it tenth, with a circulating capitalization of $3,196,662,687.82 based on 65,748,111,645 TRX. Its displayed trailing 24-hour volume was $214,723,280. TRX was down 0.83% over the snapshot’s 24-hour window but up 7.49% over seven days.

Those figures establish the asset’s approximate market scale, not a migration-driven price reaction. CoinMarketCap aggregated trading across markets, and its preserved page does not identify a closing auction, single venue, precise observation time or complete historical calculation methodology. Crypto traded continuously, so the snapshot should not be treated as a universal daily close. The available record cannot isolate the migration’s effect from broader trading conditions.

Why the transition mattered

Token migrations test more than software. Exchanges had to reconcile customer balances, disable incompatible transfers, exchange the old units and deploy new deposit and withdrawal infrastructure without interrupting trading. Users holding TRX outside participating exchanges also faced different procedures and greater responsibility for completing the conversion.

The move additionally changed the system on which TRX ownership would ultimately be recorded. An ERC-20 balance depended on an Ethereum smart contract; native TRX would depend on TRON’s ledger, consensus rules, nodes and governance. Beginning migration therefore represented a concrete step toward protocol independence, but it did not prove that the new network was decentralized, secure, production-ready or broadly adopted.

Later context

Bitfinex updated its migration notice on July 11, 2018 to say that it had completed the conversion for its customers and reopened deposits and withdrawals. That subsequent venue-specific confirmation does not establish when every exchange or independently held token completed migration.