Skip to main content
This section documents the legacy Whitechain Layer 1 (L1): mainnet chain ID 1875 and testnet chain ID 2625. The L1 mainnet 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 L2, see Introduction to Whitechain.
Whitechain launched as an EVM-compatible L1 built on go-ethereum, secured by Proof of Authority (PoA) consensus operated by WhiteBIT. The L1 runs with 2-second block times, a fixed 10 gwei gas price paid in WBT, and a single validator. Whitechain moved to an L2 built on the OP Stack, which settles on Ethereum through blob data availability. At the migration on 26 October 2026, L1 block production ended, the L1 state became the L2 genesis, and the L1 now answers read methods only. No decommissioning date is set. This section collects the L1 reference material: its architecture, validator design, endpoints, and developer workflows. For the migration plan and its stages, see Migration to L2.

Current status of the legacy L1

For the sunset stages and what stopped working at each, see L1 sunset stages.

What this section covers

  • Background and vision the mission statement and design principles of the L1 chain
  • Architecture go-ethereum base, Clique PoA, validator network design
  • Wallet configuration how to connect a wallet to the L1 mainnet and testnet
  • WBT how WBT is obtained, withdrawn, and used as gas on the L1
  • Smart contracts L1 deployment, verification, and proxy verification workflows
  • Run a node the L1 mainnet node guide
  • Bridge the L1 cross-chain bridge reference
  • Migration the L1 to L2 transition from the L1 side

L1 network details

Values in this table are the L1 values. The hostnames changed at the migration, as noted per row. eth_chainId returns 0x753 on both the L2 and the legacy L1, so it cannot tell them apart. Read legacy L1 data only from the legacy hostnames above. See Endpoint and domain changes.