Run a Full Node
Requirements and inputs for running a Lithosphere full node.
Last reviewed: 2026-08-01
This page summarizes non-validating full-node requirements. The canonical, command-by-command guide is the Exchange Node Guide.
Immutable inputs
| Input | Approved value |
|---|---|
| Cosmos chain ID | lithosphere_9005-1 |
| EVM chain ID | 9005 (0x232d) |
| Genesis URL | https://rpc-mainnet.litho.ai/genesis.json |
| Genesis SHA-256 | 13e4875b4a9dddc63bdfbd4968c7265f9bbc49218b59c5b49231a56fa313046f |
| Approved binary SHA-256 | 0546677a9cf3a7f458797b65181a46f21c89185933e832d89ce728a144fd258c |
| Base denomination | ulitho |
The binary includes a consensus-critical fixed-supply patch. Verify the exact approved release artifact and checksum. The public signed binary URL is still a publication gate; do not download an old testnet binary or accept one through an unverified file share.
Recommended capacity
| Profile | CPU | RAM | Disk |
|---|---|---|---|
| Pruned full node | 8 vCPU | 32 GiB | 500 GB NVMe |
| Archive/historical node | 8–16 vCPU | 32–64 GiB | Start at 1 TB NVMe |
Use stable 100 Mbps or faster networking and keep at least 30% disk space free.
Port policy
| Service | Default | Exposure |
|---|---|---|
| CometBFT P2P | TCP 26656 | Public or outbound-only through NAT |
| CometBFT RPC | TCP 26657 | Loopback/private only |
| REST/LCD | TCP 1317 | Loopback/private only |
| gRPC | TCP 9090 | Loopback/private only |
| EVM JSON-RPC | TCP 8545 | Loopback/private only |
| EVM WebSocket | TCP 8546 | Loopback/private only |
| Prometheus | TCP 26660 | Monitoring network only |
Never expose a custody or administrative RPC directly to the Internet.
Bootstrap status
No checksum-pinned public Lithosphere snapshot is currently approved. Start from the canonical genesis and block-sync from the official peers documented in the full guide.
Synchronization is complete only when the node reports the correct network,
catching_up is false, the latest block time is current, the height advances,
and the height agrees with independent endpoints.
Validator separation
A normal full node does not require a validator consensus key. Never copy a
validator priv_validator_key.json or priv_validator_state.json onto a public,
exchange, indexing, or application node.