Skip to main content
The legacy Layer 1 (L1) is live and producing blocks. The Layer 2 (L2) is live on Testnet as Whitechain Sepolia (chain ID 1874). State migration and the end of L1 block production happen at L2 Mainnet launch, on a date that is not yet announced. When migration happens, you will not need to do anything.
Whitechain runs as an EVM-compatible L1 operated by WhiteBIT. It is moving to an L2 built on the OP Stack. At migration the full L1 state becomes the L2 genesis, so your funds and contracts carry over as they are, at the same addresses.

​
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 will be carried over to L2 exactly as it stands at the snapshot. You will 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 you. If you self-custody, your balance appears on L2 at the same address once migration completes.

​
Users of the L1

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

​
Integrations and service operators

If you run software that reads or writes the legacy L1, you have changes to make, even though your users do not. User balances migrate on their own; connection settings do not. The legacy L1 mainnet runs at chain ID 1875 (hex 0x753), with its JSON-RPC endpoint at https://rpc.whitechain.io and its explorer at https://explorer.whitechain.io today. Both hostnames serve the L2 after L2 Mainnet launch, and the L1 services move to legacy hostnames. See Endpoint and domain changes. Test every change against Whitechain Sepolia (chain ID 1874) before Mainnet migration. Sepolia runs the same OP Stack software as L2 Mainnet, so a fix that works there works at launch. 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 is moving to L2

The OP Stack separates execution, data availability, and settlement into distinct layers, which lowers upgrade complexity and sets 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. 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 reduces the centralization of the previous L1.

​
How the migration works

The migration follows a freeze then dump procedure at Mainnet:
  1. Freeze the L1 at a chosen snapshot block, so it produces no further blocks.
  2. Export the full state at that block and verify it against the block state root and the known total supply.
  3. Transform that state into the OP Stack L2 genesis, so L2 starts with the complete L1 state in place.

​
Scope of the migration

Migration applies to Mainnet only. The legacy L1 testnet is not migrated. Whitechain Sepolia starts from its own genesis, so contracts and balances on chain ID 2625 do not appear on chain ID 1874. Redeploy test contracts on 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 shuts down in five stages. Stages 1 to 3 happen on the day L2 Mainnet launches. Stages 4 and 5 follow it. The length of the read-only period is not yet announced.

​
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. The legacy L1 testnet (chain ID 2625) is not migrated, so rpc-testnet.whitechain.io and testnet.whitechain.io are not part of this cut-over. See Scope of the migration. A hostname does not identify a chain. After the cut-over, a client still configured with https://rpc.whitechain.io reads the L2, at a different chain ID, without any change on the client side. Confirm which chain an endpoint serves by calling eth_chainId:
The legacy L1 mainnet returns 0x753, chain ID 1875. The L2 Mainnet chain ID is published in the Network reference before Mainnet launch. Compare the response against that value in every environment you operate.
L1 transaction history and event logs are not migrated to the L2, and they are not reachable once the L1 is decommissioned. Export the L1 history you need while the legacy explorer and the legacy read-only RPC endpoint are online.

​
Moving WBT between L1 and L2

You do not have to move anything. Your balance will already exist on L2 after migration. To move WBT between Ethereum and Whitechain L2 by choice, use either route:

​
Deadlines

The migration has no deadline for holders, because holders have 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. No migration date is announced. Every milestone in this table is pending. Whitechain publishes 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.

​
FAQ

​
For WBT holders

No. Your balance migrates to L2 automatically and stays 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 handles the transition for balances held on WhiteBIT. Trading and internal balances are unaffected by the on-chain snapshot.
Yes. Token balances live in contract storage, and contract storage migrates in full. Your token and NFT holdings appear on L2 at the same contract addresses.
Yes, once. The L2 uses a different chain ID and RPC URL than the legacy L1, so add the L2 network to your wallet to see your balance and transact. The L2 chain ID and endpoints are published before Mainnet launch in the Network reference.
No. Only final state migrates, so balances, contract code, storage, and nonces carry over, but transaction history and event logs do not. To export the history you need, use https://explorer.whitechain.io while the L1 is live, and https://legacy-explorer.whitechain.io after L2 Mainnet launch, when explorer.whitechain.io serves the L2. Export before the L1 is decommissioned. See Endpoint and domain changes.
Pending mempool transactions are not migrated. Anything unconfirmed at the snapshot block never executes. Resubmit it on L2 after launch if you still want it.
No. WBT stays the native gas token on L2, with 18 decimals and unchanged supply. The migration copies balances to the wei.

​
For integrations

Repoint your infrastructure to the L2 chain ID, RPC URL, and explorer, and stop crediting L1 deposits at the snapshot block. User balances migrate on their own; your connection settings do not. Pin each endpoint by the chain ID it reports, because rpc.whitechain.io and explorer.whitechain.io serve the L2 after the cut-over. See Integrations and service operators for the change list by integration type.
No. Bytecode, storage, nonces, and addresses are preserved, so your contracts exist on L2 at the same addresses. Repoint your RPC URL and chain ID, then re-verify the source on the L2 explorer so users can read it there.
Its logic does. The EVM is unchanged, so contract code runs identically. The fee model changes from a fixed 10 gwei gas price to 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. It runs the same OP Stack software as L2 Mainnet, so an integration that works there works at launch. Claim test WBT from the faucet.
Export what you need while the L1 endpoints are online, then index the L2 from its genesis block. L1 history is not reachable from the L2.
The length of the read-only period is not yet announced. After the snapshot block the L1 explorer and JSON-RPC API answer read methods at the legacy hostnames, and they shut down permanently at L1 decommissioning. See L1 sunset stages and Deadlines.
Use https://legacy-explorer.whitechain.io for the L1 explorer, and the legacy read-only RPC hostname published in the Network reference before Mainnet launch. https://explorer.whitechain.io and https://rpc.whitechain.io serve the L2 from the cut-over onward, so a client left pointing at them reads the L2 at a different chain ID. Confirm the chain with eth_chainId. See Endpoint and domain changes.
From the Network reference. Mainnet values are published there before Mainnet launch. Whitechain Sepolia values are published there now.

​
Timing and safety

Migration happens at L2 Mainnet launch, on a date that is not yet announced. Holders cannot miss anything, because holders have no task to complete. Integrations should be ready by the snapshot block, which is announced with the launch date. See Deadlines.
The L1 is live and accepts transactions until the snapshot block. After that block it answers read methods only, at the legacy hostnames, and it is decommissioned later. Export any historical data you need before decommissioning. See What read-only mode means.
No. Migration applies to Mainnet only. The legacy L1 testnet, chain ID 2625, 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.
No. There is no manual migration step. Any such request is a scam. Do not connect your wallet or share any keys.
Whitechain publishes migration dates on X, in the Whitechain Telegram channel, and on this page. No date is published yet. Check any date you see against those three sources. See Deadlines.