Skip to main content
This page documents the legacy Whitechain Layer 1 (L1), mainnet chain ID 1875. The L1 stopped producing blocks at the migration on 26 October 2026, 02:00 UTC, and its state became the genesis of the Whitechain Layer 2 (L2) documented in the rest of these docs. It now serves read-only history at legacy.explorer.whitechain.io and legacy.rpc.whitechain.io. For the full migration plan, sunset stages, and milestones, see Migration to L2.
This page covers the L1 to L2 migration from the perspective of the legacy L1. The migration ran on 26 October 2026 at 02:00 UTC. The L1 mainnet no longer produces blocks or accepts transactions. For the full migration narrative, the technical comparison table, and the current network details, see Migration to L2.

What was migrated

The complete state of the Whitechain L1 mainnet became the OP Stack L2 genesis:
  • All account balances, for both externally owned accounts and contracts
  • All smart contract code and storage slots
  • Nonce values for every account
No user action was required. Addresses on the L1 map one to one to the same addresses on the L2, so balances and contract identities are preserved. Transaction history and event logs were not migrated, and pending mempool transactions never executed on the L1. The L2 genesis block number is the last L1 block number plus 1. Migration applied to Mainnet only. The L1 testnet, chain ID 2625, was not migrated; it stopped on 26 October 2026. It is superseded by Whitechain Sepolia, chain ID 1874, which starts from its own genesis. See Scope of the migration.

L1 state at the cut-over

The L1 validator stopped at the snapshot block, the last block the L1 produced. The full state at that block was exported and transformed into the L2 genesis. After the snapshot block the L1 entered a read-only period. The L1 explorer and the L1 JSON-RPC API answer read methods against L1 state up to the snapshot block, and they refuse the methods that submit a transaction. No new L1 transaction is possible. No decommissioning date is set. See What read-only mode means. See Deadlines for the migration dates.

Endpoints at the cut-over

At the cut-over the L1-linked hostnames were reassigned to the L2, and the L1 services moved to legacy hostnames. whitechain.io, explorer.whitechain.io, and rpc.whitechain.io serve the L2 since the cut-over, at the same chain ID 1875. eth_chainId returns 0x753 on both the L2 and the legacy L1, so it cannot tell them apart; read L1 data only from the legacy hostnames. See Endpoint and domain changes.

What replaces the L1 components

L1 decommissioning

No decommissioning date is set. The legacy L1 explorer and JSON-RPC API stay read-only until the decommissioning date is published; after that, L1 transaction history is no longer reachable from any Whitechain endpoint.
L1 transaction history and event logs are not migrated to the L2. Export the L1 history your systems need from https://legacy.explorer.whitechain.io before decommissioning.
For why Whitechain moved to L2 and the broader technical comparison, see Migration to L2.