Whitechain L2 migration: what will change for the users?

Why is Whitechain migrating to a Layer 2?

There are several reasons why Whitechain is migrating to a Layer 2 network:

  • Security, inherited from Ethereum. On the L2, chain data is published and settled on Ethereum, so Whitechain inherits Ethereum's security and data-durability guarantees instead of carrying its own.
  • Less centralization. The old L1 used a single-validator Proof of Authority model. Moving to the OP Stack is a step away from that toward decentralized sequencing over time.
  • Lower upgrade complexity and better performance. The OP Stack separates execution, data availability, and settlement into distinct layers, which simplifies upgrades and sets up later performance work.
  • Shared ecosystem and tooling. The OP Stack also underlies Base, Optimism, and the Superchain, which gives Whitechain shared tooling and a path toward decentralized sequencing.

On 26 October 2026, the Whitechain L1 was replaced by Whitechain L2. At the switch, the entire state of the old chain (every balance, contract, and storage slot) was copied into the new chain, so everything continues at the same addresses

Which actions are required for the migration? 

No action is required. You do not need to claim, swap, unlock, re-register, or move anything. Your WBT balance carried over to L2 exactly as it stood at the snapshot, at the same address. If you keep WBT on WhiteBIT, the exchange handled the transition for you. If you self-custody, your balance is on L2 at the same address, controlled by the same seed phrase and private key.

You do not need to change your wallet settings either. Chain ID 1875 and the RPC URL https://rpc.whitechain.io stayed the same, so your existing network entry now shows your L2 balance.

What exactly is preserved, and what is not?

PreservedNot migrated
  • Smart contracts (bytecode, storage, nonces, addresses)
  • Token balances
  • Native WBT balances (preserved to the wei)
  • Transaction history
  • Event logs
  • Pending (mempool) transactions

The migration took place on 26 October 2026 at 02:00 UTC. The L1 snapshot, the L2 launch, and the domain cut-over happened on the same day. Your L1 transaction history stays available on the legacy explorer at https://legacy.explorer.whitechain.io.

How is a scam defined during the migration?

Please note that there is no manual migration step, and no legitimate support agent will ever ask for your seed phrase, private key, or a wallet signature to complete a migration step. Do not connect your wallet or share any keys. Confirm any information through an official channel first.

Whitechain announces migration news in only three places: X (https://x.com/Whitechain_io), the Telegram channel (https://t.me/Whitechain_io), and the migration page in the docs. The migration is complete and there is nothing to claim, so treat any message that pressures you to act before a deadline as a scam.

 

To avoid fake tokens, sites, and endpoints, check contract addresses and links only against official Whitechain and WhiteBIT sources. Use only the official endpoints: https://rpc.whitechain.io for Whitechain, and https://legacy.rpc.whitechain.io for read-only legacy L1 data. Both return chain ID 1875, so eth_chainId cannot tell them apart. Treat any other endpoint claiming to serve chain ID 1875 or 1874 as unofficial. When in doubt, do nothing and ask in an official channel.

Please note that a transaction you signed for the legacy L1 and did not broadcast is still valid on L2, because the chain ID did not change. Anyone who holds the signed transaction can submit it at its nonce. To cancel it, send any transaction from the same address with that nonce on L2.

Related articles:

What will happen to Whitechain Legacy L1 after the L2 migration?

What will change for the dApps and smart contracts after the L2 migration?

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request