Skip to main content
This section documents the legacy Whitechain Layer 1 (L1): mainnet chain ID 1875 and testnet chain ID 2625. The L1 is live and producing blocks. It is a separate chain from the Whitechain Layer 2 (L2) documented in the rest of these docs, and its mainnet state migrates to the L2 at L2 Mainnet launch. 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 is moving to an L2 built on the OP Stack, which settles on Ethereum through blob data availability. That move has not happened yet. The L1 mainnet still produces blocks and still accepts transactions. At L2 Mainnet launch its block production ends, its state becomes the L2 genesis, and the L1 then answers read methods only until it is decommissioned. 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 five sunset stages and what stops 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 in effect today. The hostnames change at L2 Mainnet launch, as noted per row. Confirm which chain an endpoint serves by calling eth_chainId rather than by hostname. See Endpoint and domain changes.