Skip to main content
This document lists all CLI flags for the kona-node node subcommand, grouped by category. All flags can be provided as command-line arguments or via environment variables.
For more details on each flag, see the inline help (kona-node node --help) or the source code.

Default Ports

Core Node Arguments

Global Arguments

Chain ID Support

The --l2-chain-id flag supports flexible chain identification using the alloy_chains crate: Numeric Chain IDs:
String Chain Names:
Short Flag and Environment Variable:
Supported chain names include all those recognized by alloy_chains (e.g., optimism, base, mainnet). Unknown numeric chain IDs are accepted for custom networks.

P2P Arguments

RPC Arguments

Sequencer Arguments

Supervisor Arguments

RPC Trust Flags

The --l1-trust-rpc and --l2-trust-rpc flags control whether Kona verifies the block hashes of RPC responses. For guidance on when to disable trust and worked examples for trusted, untrusted, and mixed provider setups, see configure RPC trust.

Default Behavior

Unless overridden by the flags above, a kona-node node run has the following defaults:
  • The P2P stack is spun up. The libp2p swarm listens on TCP 9222 to receive block gossip. The discv5 discovery service runs on UDP port 9223. Peer scoring is enabled.
  • An RPC server is exposed at 0.0.0.0:9545. Websocket connections are disabled by default.
  • Prometheus metrics are disabled. Enable them with the --metrics.enabled flag; metrics are then served on 0.0.0.0:9090, configurable via the --metrics.port and --metrics.addr flags.

Rollup Configuration Loading

If a file path to a rollup config is not specified via the --l2-config-file cli flag, the Rollup Config will be loaded via the superchain registry. A custom rollup config can either be specified through the --l2-config-file flag, or specific values may be overridden using a set of override flags provided by the kona-node. Override flags (for example --canyon-override) can be viewed in the help menu by running kona-node node --help. The only overrides currently supported are hardfork timestamps in seconds.