Networks and endpoints
Who this is for: anyone who needs to copy a network value into a wallet, config file, or script, and anyone who needs to know what permission mode that environment runs under before they connect. This page is the single source of truth: every other page should link here rather than restate a value.
A note on names
Lumia's live production network is called Lumia Prism. Where you see "mainnet" here it means Prism; the two names refer to the same network, chain ID 994873017. The testnet is called Beam.
A note on two different "Lumia Testnet" names
docs.lumia.org's /build/identity/on-chain-kyc-integration page states chain ID 1952959480 and labels it, verbatim, "Lumia Testnet." It does not call this network "Beam". That network is retired: its RPC (https://testnet-rpc.lumia.org) and explorer (https://testnet-explorer.lumia.org) both refuse the connection live. Full deprecation notice and migration steps: /reference/retired-testnet.
The live, current testnet is Beam, chain ID 2030232745. chainid.network's registry lists three separate Lumia entries: mainnet (994873017), the retired "Lumia Testnet" (1952959480, dead RPC/explorer as above), and Beam (2030232745, live beam-rpc.lumia.org / beam-explorer.lumia.org). This three-way listing resolves which chain ID belongs to which network. All Beam values below are for the network this doc site actually points builders at (faucet, MetaMask guides, bridge). Pick your environment below.
Chain ID
994873017RPC (HTTPS)
https://mainnet-rpc.lumia.orgRPC (WSS)
wss://mainnet-rpc.lumia.org/wsExplorer
https://explorer.lumia.orgNative currency symbol
LUMIANative currency decimals
18Bridge
https://bridge.lumia.org(native zkEVM bridge)
https://hyper.lumia.org(Hyperlane instant bridge)
DA layer
Avail DA, per docs.lumia.org's Data Availability section (validium model).
Permission model
Lumia's chain layer is permissionless: any address can transact. Compliance checks, where an application chooses to enforce them, live at the application layer, not the network layer. This does not vary by environment. See Permissionless base, permissioned app layer.
Chain ID
RPC (HTTPS)
RPC (WSS)
Explorer
Faucet
Native currency symbol
Native currency decimals
Bridge
Same bridge endpoints as mainnet route testnet traffic per docs.lumia.org framing.
Permission model
Lumia's chain layer is permissionless: any address can transact. Compliance checks, where an application chooses to enforce them, live at the application layer, not the network layer. This does not vary by environment. See Permissionless base, permissioned app layer.
Chain ID 1952959480 is a retired network. Its RPC and explorer are dead. It is not Beam. Do not use 1952959480 for anything, and do not treat it as an alternate name for Beam.
Referenced by docs.lumia.org's /build/identity/on-chain-kyc-integration page under this exact name. Do not use it. It is dead infrastructure, not an alternate name for Beam.
Chain ID
Labeled "Lumia Testnet" verbatim on docs.lumia.org/build/on-chain-kyc
RPC (HTTPS)
Is dead, connection refused live
Explorer
Is dead, connection refused live
Status
Deprecated/retired.
Full deprecation notice and migration steps: /reference/retired-testnet.
Need a value that isn't here? It hasn't been verified yet. Do not guess it from an old tutorial. Otherwise, put these values to use in the Quickstart: your first contract on Lumia.
Last updated
Was this helpful?