Binance Chain Went Live as BNB Prepared to Leave Ethereum

Binance announced that Binance Chain went live on April 18, 2019, with preselected validators producing blocks from the network’s genesis block. The launch established a purpose-built blockchain for the exchange company’s BNB asset and its planned decentralized exchange, shifting Binance from operating trading venues toward supporting its own settlement infrastructure.

The event-day boundary is important. Binance Chain was producing blocks, and native BNB was created through the genesis process, but the broad token migration had not been completed. Binance’s public explorer and web wallet were initially reserved for selected partners and beta testing, with public access expected around April 23. No trading pairs were to be listed until the first BNB conversion occurred.

April 18 therefore marked the network’s technical beginning—not the completion of every product and migration milestone associated with it.

A controlled migration from Ethereum

BNB had been issued as an ERC-20 token on Ethereum. Binance’s April 18 plan called for those tokens to be replaced progressively with native BEP-2 BNB on Binance Chain. Binance.com expected to begin assisting users with the conversion on April 23 at the earliest, principally by accepting deposits of ERC-20 BNB and processing withdrawals as native BNB.

The company set the native ledger’s initial total supply at 200 million BNB. Its announcement said 11,654,398 BNB would be treated as burned and 48 million would be frozen, mirroring the existing ERC-20 accounting. An initial five million native BNB were to be allocated to a Binance-controlled address for conversions, accompanied by the destruction of five million ERC-20 BNB.

Binance said proportional amounts of the Ethereum token would continue to be burned as native coins were released, with the objective of keeping the combined supply across both networks constant. That was the company’s stated migration mechanism. The surviving event-day sources do not provide an independent audit of every genesis allocation, frozen balance or subsequent burn.

Why the genesis block mattered

The launch changed BNB’s intended role. It was no longer meant to remain only an exchange-related token implemented through Ethereum. Native BNB would pay Binance Chain transaction fees and serve as the base asset for an on-chain market infrastructure built around Binance DEX.

That strategy represented substantial vertical integration. Binance could connect its centralized exchange, token conversion process, wallet ecosystem, blockchain settlement layer and decentralized-exchange interface around one native asset. Projects could potentially issue assets on the chain and seek markets through the Binance ecosystem without relying on Ethereum for settlement.

The model also concentrated important early decisions around Binance and its selected network participants. Validators had been chosen before launch, Binance controlled the principal conversion route, and the company defined the initial supply treatment. Producing a genesis block established that the network operated; it did not establish broad validator independence, durable security, competitive liquidity or adoption by outside issuers.

What remained unresolved on April 18

The April 18 record did not show that ordinary users could access every network tool, that ERC-20 holders had completed conversion, or that Binance DEX had begun executing trades. Those were separate milestones expected around or after April 23, subject to Binance’s explicit warning that the schedule could change.

No event-day market dataset reviewed for this reconstruction can isolate the genesis launch as the cause of a particular BNB price move. The consequential and verifiable development was narrower: Binance Chain began producing blocks, creating the technical foundation for BNB’s planned departure from Ethereum and for an exchange-sponsored blockchain marketplace.