Skip to main content
Quantum Chain is configured through three layers: the genesis file (chain rules), geth command-line flags (runtime), and JSON-RPC API admin calls (live).

Genesis file

A complete mainnet genesis lives at configs/mainnet/genesis.json. The fields specific to Quantum Chain are: Standard Ethereum hard-fork toggles (homesteadBlock, byzantiumBlock, … londonBlock) work as in upstream geth.

Geth flags

The most common production flags are listed below. Run geth --help for the full list.

Networking

JSON-RPC

Mining (Clique sealer)

Account unlocking

Storage and pruning

TxPool

Runtime configuration via JSON-RPC

Some parameters are runtime-tunable through the admin_*, miner_*, and debug_* namespaces:
These namespaces must be enabled with --http.api admin,miner,debug and should never be exposed publicly.

Validator (Clique sealer)

Always run validators without --http.addr 0.0.0.0. Expose only on localhost.

Public RPC node

Place behind a TLS reverse proxy (nginx, Caddy) and a rate limiter.

Archive node

Where to go next