> ## Documentation Index > Fetch the complete documentation index at: https://l2docs.whitechain.io/llms.txt > Use this file to discover all available pages before exploring further. # Legacy Whitechain L1 overview > Reference for the legacy Whitechain Layer 1: its Proof of Authority consensus, endpoints, current live status, and what changes at L2 Mainnet launch. 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](/learn/general/what-is-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](/learn/general/migration). ## Current status of the legacy L1 | Question | Answer | | --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Is the L1 live? | Yes. The L1 mainnet (chain ID `1875`) produces blocks and accepts transactions today | | Has migration to L2 happened? | No. It happens at L2 Mainnet launch, on a date that is not yet announced | | When does L1 block production stop? | At L2 Mainnet launch. The last L1 block is the snapshot block, and no L1 transaction is possible after it | | Is the L1 testnet (chain ID `2625`) migrated? | No. It is superseded by Whitechain Sepolia, chain ID `1874`, which starts from its own genesis | | Does a WBT holder need to do anything? | No. Balances, contracts, storage, and nonces carry over to the L2 at the same addresses. L1 transaction history is not carried over | | Do the L1 hostnames change? | Yes. At L2 Mainnet launch `whitechain.io` and `explorer.whitechain.io` begin serving the L2, and the L1 services move to `legacy.whitechain.io` and `legacy-explorer.whitechain.io` | For the five sunset stages and what stops working at each, see [L1 sunset stages](/learn/general/migration#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. | Aspect | Value | | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Consensus | Proof of Authority (Clique, EIP-225), operated by WhiteBIT | | Base | go-ethereum | | Mainnet chain ID | `1875` (hex `0x753`) | | Testnet chain ID | `2625` (hex `0xa41`) | | Block time | 2s | | Gas price | Fixed 10 gwei | | Gas token | WBT | | Mainnet RPC | `https://rpc.whitechain.io` today. Serves the L2 after L2 Mainnet launch; the legacy read-only RPC hostname is published in the [Network reference](/learn/network/reference) before Mainnet launch | | Mainnet explorer | `https://explorer.whitechain.io` today. Serves the L2 after L2 Mainnet launch; the L1 explorer moves to `https://legacy-explorer.whitechain.io` | | Mainnet website | `https://whitechain.io` today. Serves the L2 after L2 Mainnet launch; the L1 site moves to `https://legacy.whitechain.io` | | Testnet RPC | `https://rpc-testnet.whitechain.io`. Not part of the migration, because the L1 testnet is not migrated | | Testnet explorer | `https://testnet.whitechain.io`. Not part of the migration, because the L1 testnet is not migrated | Confirm which chain an endpoint serves by calling `eth_chainId` rather than by hostname. See [Endpoint and domain changes](/learn/general/migration#endpoint-and-domain-changes).