labs
Chain ID:
0G-Mainnet
RPC Status:
End-to-end guide for spinning up an aristotle-mainnet full node. 0G runs a Cosmos-SDK consensus layer (0gchaind) alongside an EVM execution layer (geth). Both ship in the same release tarball, run as systemd services, and share a JWT secret over the engine API.
Install build tools and lz4 (used for snapshot decompression). Recommended: Ubuntu 22.04 or 24.04 with 8 CPU cores, 32 GB RAM, 1 TB NVMe disk.
0gchaind is built with Go. Use the official toolchain rather than the apt-shipped version (often outdated).
Aristotle is the 0G mainnet release line. v1.0.6 is the current stable. The tarball ships both the consensus daemon (0gchaind) and the EVM execution layer (geth), plus the geth configs, the EVM genesis, and the KZG trusted setup file required by the consensus engine.
Pick a moniker (display name) — visible on explorer.0g.ai and our 0g.exploreme.pro validator list.
Wire to our public peer for initial PEX, set pruning to keep your disk in check, and zero out the minimum gas price (0G mainnet currently runs with no fee floor).
Skip downloading every historical block — pull a recent state snapshot from our RPC and start syncing from there. Takes minutes instead of days for a fresh full sync.
0G runs Cosmos-SDK consensus + a separate EVM execution layer. The 0gchaind daemon talks to geth via the engine API over JWT.
Standard systemd service. Note the mandatory --kzg.trusted-setup-file flag — without it 0gchaind panics on start.
Execution layer service. Exposes RPC on :8545 / WS on :8546, engine-API on :8551 (consensus talks to it via the shared JWT).
Bring up geth first, give it 5 seconds, then start 0gchaind. The consensus daemon needs the engine-API alive before it tries to produce/import blocks.
After full sync, register as a validator. Fund the validator key from a CEX or bridge first; details on explorer.0g.ai.