> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lumera.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Networks and Endpoints
> Network configuration, public endpoints, genesis files, and connection information for Lumera Mainnet and Testnet.
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.
| Service | Mainnet | Testnet |
| -------------- | ------------------------- | ----------------------------------------- |
| **gRPC** | `grpc.lumera.io:443` | `grpc.testnet.lumera.io:443` |
| **RPC** | `https://rpc.lumera.io` | `https://lumera-testnet-rpc.polkachu.com` |
| **LCD (REST)** | `https://lcd.lumera.io` | `https://lumera-testnet-api.polkachu.com` |
| **SN-API** | `https://snapi.lumera.io` | `https://snapi.testnet.lumera.io` |
Community infrastructure providers such as [Polkachu](https://www.polkachu.com/networks/lumera) also operate public Lumera endpoints. Validator snapshots and additional connection resources are available in the [validator setup guides](/validators/mainnet/node-setup).
## 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
| Parameter | Value |
| --------------------- | ---------------------------------------------------------- |
| **Chain ID** | `lumera-mainnet-1` |
| **Native denom** | `ulume` |
| **Minimum gas price** | `0.025ulume` |
| **Explorer** | [Lumera Portal](https://portal.lumera.io/lumera-mainnet-1) |
### Genesis File
Download the network genesis file from the official `lumera-networks` repository:
```bash theme={null}
curl -o genesis.json https://raw.githubusercontent.com/LumeraProtocol/lumera-networks/master/mainnet/genesis.json
```
Move the file into the node configuration directory:
```bash theme={null}
cp genesis.json ~/.lumera/config/genesis.json
```
### Seed Nodes
Add the network seed node to the `[p2p]` section of `~/.lumera/config/config.toml`:
```toml theme={null}
seeds = "f64b9efc5747cc3556bdc281dab930a716dd63af@seeds.lumera.io:26656"
```
### Minimum Gas Price
Set the minimum accepted gas price in `~/.lumera/config/app.toml`:
```toml theme={null}
minimum-gas-prices = "0.025ulume"
```
### Quick Configuration
```bash theme={null}
# Initialize node (replace with your node name)
lumerad init --chain-id lumera-mainnet-1
# Download genesis
curl -o ~/.lumera/config/genesis.json \
https://raw.githubusercontent.com/LumeraProtocol/lumera-networks/master/mainnet/genesis.json
# Set seeds in config.toml
sed -i 's/seeds = ""/seeds = "f64b9efc5747cc3556bdc281dab930a716dd63af@seeds.lumera.io:26656"/' \
~/.lumera/config/config.toml
# Set gas price in app.toml
sed -i 's/minimum-gas-prices = ""/minimum-gas-prices = "0.025ulume"/' \
~/.lumera/config/app.toml
# Start the node
lumerad start
```
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.
Testnet is where new validators onboard, developers test integrations, and SuperNode operators rehearse before staking on mainnet. Testnet LUME has no value. Request some from the [faucet](/faucet).
### Network Parameters
| Parameter | Value |
| --------------------- | ------------------------------------------------------------------------- |
| **Chain ID** | `lumera-testnet-2` |
| **Native denom** | `ulume` |
| **Minimum gas price** | `0.025ulume` |
| **Explorer** | [Lumera Portal](https://portal.testnet.lumera.io/lumera-testnet-2) |
| **Faucet** | [Portal faucet](https://portal.testnet.lumera.io/lumera-testnet-2/faucet) |
### Genesis File
Download the network genesis file from the official `lumera-networks` repository:
```bash theme={null}
curl -o genesis.json https://raw.githubusercontent.com/LumeraProtocol/lumera-networks/master/testnet-2/genesis.json
```
Move the file into the node configuration directory:
```bash theme={null}
cp genesis.json ~/.lumera/config/genesis.json
```
### Seed Nodes
Add the network seed node to the `[p2p]` section of `~/.lumera/config/config.toml`:
```toml theme={null}
seeds = "faff7c1350468c53121a669ac40e317a4a70c425@seeds.testnet.lumera.io:26656"
```
### Minimum Gas Price
Set the minimum accepted gas price in `~/.lumera/config/app.toml`:
```toml theme={null}
minimum-gas-prices = "0.025ulume"
```
### Quick Configuration
```bash theme={null}
# Initialize node (replace with your node name)
lumerad init --chain-id lumera-testnet-2
# Download genesis
curl -o ~/.lumera/config/genesis.json \
https://raw.githubusercontent.com/LumeraProtocol/lumera-networks/master/testnet-2/genesis.json
# Set seeds in config.toml
sed -i 's/seeds = ""/seeds = "faff7c1350468c53121a669ac40e317a4a70c425@seeds.testnet.lumera.io:26656"/' \
~/.lumera/config/config.toml
# Set gas price in app.toml
sed -i 's/minimum-gas-prices = ""/minimum-gas-prices = "0.025ulume"/' \
~/.lumera/config/app.toml
# Start the node
lumerad start
```
Use the [Lumera Portal](https://portal.testnet.lumera.io/lumera-testnet-2) to watch your validator status, inspect transactions, and confirm your node produces blocks.
## 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.
| Component | Minimum |
| ----------- | ------------------------------- |
| **CPU** | 8+ cores |
| **Memory** | 64 GB RAM |
| **Storage** | 2 TB+ SSD |
| **Network** | High bandwidth with low latency |
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](/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.
Get help with Validator, SuperNode, and developer questions.
Read the source for `lumerad`, the `supernode` daemon, and the SDKs.
Follow protocol announcements and upgrade notices.
## Next Steps
Connect to Lumera and store your first file through Cascade.
Request Testnet LUME for development and testing.
Configure a node and prepare to join the validator set.