Skip to main content
The legacy Layer 1 (L1) was migrated to Whitechain L2 on 26 October 2026 at 02:00 UTC. Its full state became the L2 genesis, and Whitechain Mainnet keeps chain ID 1875. You do not need to do anything.
Whitechain ran as an EVM-compatible L1 maintained by a single authorized validator. It moved to an L2 built on the OP Stack. At migration the full L1 state became the L2 genesis, so funds and contracts carried over as they were, at the same addresses. State migration is executed on a best-effort basis without warranties of uninterrupted availability or absolute immunity from data conversion discrepancies.

Who this page is for

This article is for the people affected by the L1 to L2 migration: users of the L1, holders of WBT on the old chain, and the support and community teams who answer their questions. The answer is the same for all of them. No action is required.

WBT holders on the old chain

At migration, your WBT balance carried over to L2 exactly as it stood at the snapshot. You did not need to claim, swap, re-register, or move it. WBT stays the native gas token on L2, and its supply and tokenomics do not change. If you keep WBT on WhiteBIT, there is nothing to do. The exchange handles the transition for the balances it holds, under its own User Agreement and compliance terms. If you self-custody, your balance appears on L2 at the same address.

Users of the L1

Every account, contract, and storage slot was migrated into the L2 genesis. The migration copied the full L1 state instead of restarting from empty, so there was no gap and no redeployment step. Work continues on L2 from the point where L1 stopped.

Integrations and service operators

If you run software that reads or writes the chain, check the changes below. Your users’ balances migrated on their own. Chain ID 1875, https://rpc.whitechain.io, and https://explorer.whitechain.io did not change, and since the cut-over they serve the L2. The legacy L1 explorer is at https://legacy.explorer.whitechain.io. Test changes against Whitechain Sepolia (chain ID 1874) first. See the Network reference.

Support and community teams

When a user asks what they must do, the answer is nothing. Balances, contracts, and tokens move automatically. Point users to this page, to the FAQ, and to the channels in Where to get help. Migration events attract phishing. The guidance in Staying safe is the part to repeat.

Why Whitechain moved to L2

The OP Stack separates execution, data availability, and settlement into distinct layers, which lowered upgrade complexity and set up later performance work. Chain data is published and settled on Ethereum, so Whitechain inherits Ethereum’s security and data-durability guarantees instead of carrying its own, subject to underlying Ethereum consensus and OP Stack framework performance. The OP Stack is also the base for Base, Optimism, and the wider Superchain, so building on it gives Whitechain shared tooling and a path toward decentralized sequencing. Moving off a single-validator PoA model reduced the centralization of the previous L1.

How the migration works

The migration followed a freeze then dump procedure at Mainnet:
  1. Froze the L1 at a chosen snapshot block, so it produced no further blocks.
  2. Exported the full state at that block and verified it against the block state root and the known total supply.
  3. Transformed that state into the OP Stack L2 genesis, so L2 started with the complete L1 state in place.
The genesis block number appears as number in genesis.json and as genesis.l2.number in rollup.json. The NativeAssetLiquidity allocation does not change any holder balance or the total WBT minted across chains. It is the reserve from which WBT that arrives from another chain is released on the L2, sized as the WBT minted on all chains minus the WBT already on the L2. See How the migration works.

Scope of the migration

Migration applies to Mainnet only. The legacy L1 testnet was not migrated and stopped on 26 October 2026; its endpoints are removed by 30 October 2026. Contracts and balances on chain ID 2625 do not appear on chain ID 1874. For the legacy L1 testnet, see Legacy. Use Whitechain Sepolia and claim test WBT from the faucet.

What changes on L2

For chain IDs, block times, block fields, and endpoints, see the Network reference.

L1 sunset stages

The L1 sunset ran in stages. Stages 1 to 3 completed on 26 October 2026. The L1 now stays in read-only mode, and no decommissioning date is set.

What read-only mode means

Read-only mode applies to the legacy L1 mainnet, chain ID 1875. The L1 JSON-RPC API answers read methods against L1 state up to the snapshot block. It refuses the methods that would submit a transaction. eth_blockNumber returns the snapshot block number and does not advance, because the L1 produces no further blocks. The L1 explorer stays available for the same reads: blocks, transactions, addresses, token transfers, and verified contract source up to the snapshot block.

Endpoint and domain changes

At the domain cut-over, whitechain.io and explorer.whitechain.io begin serving the Whitechain L2, and the legacy L1 services move to legacy hostnames. A client still configured with https://rpc.whitechain.io now reads the L2, at the same chain ID 1875. eth_chainId returns 0x753 on the L2 and on the legacy L1, so it cannot tell them apart. Read legacy L1 data only from the legacy endpoints.
L1 transaction history and event logs are not migrated to the L2. Read them from the legacy explorer.

Moving WBT between Ethereum and Whitechain

Your balance is already on the L2. To move WBT between Ethereum and Whitechain L2 by choice, use either route:

Deadlines

The migration had no deadline for holders, because holders had no task to complete. There is nothing to claim and no window to miss. The milestones below matter to integrations and to anyone who wants historical L1 data. Whitechain published migration dates on X, in the Whitechain Telegram channel, and on this page. For the stage-by-stage sequence, see L1 sunset stages.

Where to get help

Whitechain support never asks for your seed phrase, private key, or a wallet signature to complete a migration step.

Staying safe

Migration announcements attract phishing. Treat any message that pressures you to act before a deadline as suspicious.
  • No official process asks you to migrate, claim, or unlock WBT.
  • Never share your seed phrase or private key. No support agent asks for it.
  • Check contract addresses and links only against official Whitechain and WhiteBIT sources.
  • If a message pressures you, do nothing and confirm through an official channel first.
A transaction you signed for the legacy L1 and did not broadcast is still valid on the 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 the L2.

FAQ

For WBT holders

No. Your balance migrated to L2 automatically and stayed at the same address. You transact only when you choose to.
No. Your address is the same on L2, and your existing seed phrase and private key control it. You do not create a new wallet or move funds to a new address.
Nothing on your side. The exchange handled the transition for balances held on WhiteBIT, subject to WhiteBIT’s policies and compliance terms. Trading and internal balances were unaffected by the on-chain snapshot.
Yes. Token balances live in contract storage, and contract storage migrated in full. Your token and NFT holdings appear on L2 at the same contract addresses.
No. The chain ID (1875) and RPC URL are the same, so your existing wallet entry shows your L2 balance.
No. Only final state migrated, so balances, contract code, storage, and nonces carried over, but transaction history and event logs did not. The L2 explorer shows your balance; your L1 transactions are on https://legacy.explorer.whitechain.io.
It never executed on the L1. Because the chain ID did not change, a transaction you signed for the L1 is still valid on the L2 at the same nonce, and anyone who holds the signed transaction can submit it. To cancel it, send any transaction from the same address with that nonce on the L2.
No. WBT stays the native gas token on L2, with 18 decimals. The migration copied balances to the wei, and the total WBT minted across chains is unchanged. The L2 genesis also holds a 200,000,000 WBT reserve in the NativeAssetLiquidity predeploy for WBT that arrives from other chains; see How the migration works. WBT remains a functional utility token for network gas settlement.

For integrations

Chain ID 1875 and https://rpc.whitechain.io are unchanged and now serve the L2. Update fee logic: the L2 uses EIP-1559 with a 5 gwei base fee floor plus an L1 data fee, and produces a block every second. eth_chainId returns 0x753 on both the L2 and the legacy L1, so do not use it to tell them apart.
No. Bytecode, storage, nonces, and addresses are preserved, and the RPC URL and chain ID are unchanged. If your contract shows as unverified on the explorer, verify it again.
Its logic is preserved, with the exceptions below. The legacy L1 was limited to the Paris instruction set. The L2 runs Prague (Pectra) through the OP Stack Isthmus upgrade, plus a subset of Osaka through the OP Stack Karst upgrade. Opcodes such as PUSH0, TSTORE, MCOPY, and CLZ are now available. See Network reference.Four changes between Paris and the L2 EVM affect contracts that were already deployed:
  • SELFDESTRUCT (EIP-6780). It no longer deletes code or storage, unless the contract was created in the same transaction. It only sends the balance. A contract that relies on removing itself, or on being redeployed at the same address, behaves differently.
  • Delegated code on EOAs (EIP-7702). An externally owned account can now carry delegated code. Checks such as extcodesize(addr) == 0 or tx.origin == msg.sender no longer prove that the caller is a person. Review any access control or anti-bot logic built on them.
  • Calldata floor price (EIP-7623). Transactions that carry a lot of calldata and do little computation cost more gas than on the legacy L1.
  • Transaction gas cap (EIP-7825, from Karst). A single transaction can use at most 16,777,216 gas. A transaction that used more gas than that on the legacy L1 is now rejected.
The fee model also changes. The legacy L1 charged a fixed 10 gwei gas price, while the L2 uses EIP-1559 plus an L1 data fee, and blocks arrive every second instead of every two seconds. Review any logic that hardcodes a gas price or assumes a block interval. See Network fees.
Use Whitechain Sepolia, chain ID 1874, at https://rpc.testnet.whitechain.io. Claim test WBT from the faucet.
Read the L1 history from https://legacy.explorer.whitechain.io, then index the L2 from its genesis block. L1 history is not on the L2.
The legacy L1 stays in read-only mode, and no decommissioning date is set.
Use https://legacy.explorer.whitechain.io, or the read-only RPC at https://legacy.rpc.whitechain.io. https://explorer.whitechain.io and https://rpc.whitechain.io serve the L2, at the same chain ID 1875.
Chain ID 1875, RPC https://rpc.whitechain.io, explorer https://explorer.whitechain.io. See Whitechain Mainnet.

Timing and safety

On 26 October 2026 at 02:00 UTC. Holders had nothing to do.
Only for reading. The legacy L1 refuses new transactions; read its data on https://legacy.explorer.whitechain.io.
No. Migration applies to Mainnet only. The legacy L1 testnet, chain ID 2625, stopped on 26 October 2026 and is superseded by Whitechain Sepolia, chain ID 1874, which starts from its own genesis. Contracts and balances on chain ID 2625 do not appear on chain ID 1874. See Scope of the migration and Legacy.
No. There is no manual migration step. Any such request is a scam. Do not connect your wallet or share any keys.