1875. You do not need to do anything.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 ID1875, 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.
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:- Froze the L1 at a chosen snapshot block, so it produced no further blocks.
- Exported the full state at that block and verified it against the block state root and the known total supply.
- Transformed that state into the OP Stack L2 genesis, so L2 started with the complete L1 state in place.
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.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
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 ID1875. 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.
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.
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.Where to get help
Staying safe
- 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.
FAQ
For WBT holders
Do I need to move or claim my WBT?
Do I need to move or claim my WBT?
Does my address change, and do I need a new wallet?
Does my address change, and do I need a new wallet?
What happens to WBT I hold on WhiteBIT?
What happens to WBT I hold on WhiteBIT?
Do my ERC-20 tokens and NFTs carry over?
Do my ERC-20 tokens and NFTs carry over?
Do I need to change my wallet settings after migration?
Do I need to change my wallet settings after migration?
1875) and RPC URL are the same, so your existing wallet entry shows your L2 balance.Will my transaction history follow me to L2?
Will my transaction history follow me to L2?
https://legacy.explorer.whitechain.io.I have a transaction pending on L1. What happens to it?
I have a transaction pending on L1. What happens to it?
Does WBT supply or tokenomics change?
Does WBT supply or tokenomics change?
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
I run an exchange, wallet, or custody service. What do I have to do?
I run an exchange, wallet, or custody service. What do I have to do?
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.Do I need to redeploy my smart contracts?
Do I need to redeploy my smart contracts?
Will my contract behave the same on L2?
Will my contract behave the same on L2?
- 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) == 0ortx.origin == msg.senderno 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.
How do I test my integration?
How do I test my integration?
1874, at https://rpc.testnet.whitechain.io. Claim test WBT from the faucet.My indexer relies on L1 history. What are my options?
My indexer relies on L1 history. What are my options?
https://legacy.explorer.whitechain.io, then index the L2 from its genesis block. L1 history is not on the L2.How long will the legacy L1 RPC and explorer stay online?
How long will the legacy L1 RPC and explorer stay online?
Where do I read legacy L1 data?
Where do I read legacy L1 data?
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.Where do I get the L2 chain ID and endpoints for Mainnet?
Where do I get the L2 chain ID and endpoints for Mainnet?
1875, RPC https://rpc.whitechain.io, explorer https://explorer.whitechain.io. See Whitechain Mainnet.Timing and safety
When did the migration happen?
When did the migration happen?
Can I still use the old L1?
Can I still use the old L1?
https://legacy.explorer.whitechain.io.Is the legacy L1 testnet migrated as well?
Is the legacy L1 testnet migrated as well?
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.Someone asked me to connect my wallet to complete the migration. Is that legitimate?
Someone asked me to connect my wallet to complete the migration. Is that legitimate?

