Skip to main content
Lumera operates two public networks: Mainnet, the production network for applications and protocol services, and Testnet, a development environment for testing integrations, deploying smart contracts, and onboarding validators and SuperNode operators. Both networks use the same lumerad binary and protocol architecture. Network-specific configuration—including chain IDs, genesis files, seed nodes, and public endpoints—is provided below.

Public Endpoints

Public endpoints allow applications and developers to query network state without running a node. These endpoints may be rate-limited and should not be treated as guaranteed production infrastructure. For high-volume or production workloads, run your own node or use a dedicated provider. Community infrastructure providers such as Polkachu also operate public Lumera endpoints. Validator snapshots and additional connection resources are available in the validator setup guides.

Network Configuration

Select a network below to view its chain parameters, genesis file, seed nodes, and node configuration.
Mainnet is Lumera’s production network. LUME carries economic value, validators and SuperNodes earn protocol rewards, and data stored through Cascade is retained under the network’s permanent-storage model. Protect all Mainnet keys using production-grade security practices.

Network Parameters

Genesis File

Download the network genesis file from the official lumera-networks repository:
Move the file into the node configuration directory:

Seed Nodes

Add the network seed node to the [p2p] section of ~/.lumera/config/config.toml:

Minimum Gas Price

Set the minimum accepted gas price in ~/.lumera/config/app.toml:

Quick Configuration

Never share your validator key at ~/.lumera/config/priv_validator_key.json or your operator key mnemonic. Back both up securely before starting the node.

Node Requirements

The following specifications are the minimum recommended baseline for a production validator. SuperNode operators should provision additional CPU, memory, storage, and network capacity based on the protocol services they intend to support.
Underpowered validators may miss blocks, become jailed, or incur slashing penalties. SuperNodes that fail performance or availability requirements may fall out of the active service set and lose protocol-service rewards.
Note: Chain state and protocol-service storage requirements grow over time. Maintain sufficient capacity headroom and continuously monitor disk usage, memory utilization, network performance, and service availability.

EVM Access

Beginning with v1.20.0, Lumera nodes enable the EVM JSON-RPC server and OpenRPC discovery by default, allowing a node to support Ethereum-compatible tooling such as Hardhat, Foundry, and standard wallet integrations. Mainnet and Testnet may upgrade on different schedules. Confirm the software version currently deployed on a network before relying on EVM functionality. See the Smart Contracts overview for configuration and development details.

Resources and Support

Join our growing community and use the following resources for technical support, source code, protocol announcements, and network upgrade information.

Discord

Get help with Validator, SuperNode, and developer questions.

GitHub

Read the source for lumerad, the supernode daemon, and the SDKs.

X

Follow protocol announcements and upgrade notices.

Next Steps

Quickstart

Connect to Lumera and store your first file through Cascade.

Faucet

Request Testnet LUME for development and testing.

Validator Setup

Configure a node and prepare to join the validator set.