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. :::note 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 Configuration

The --l1-trust-rpc and --l2-trust-rpc flags control whether Kona performs additional verification on RPC responses to protect against malicious or faulty RPC providers.

Trust Modes

Default Behavior (trust enabled, true):
  • No additional block hash verification is performed
  • Optimized for performance
  • Suitable for local nodes and trusted infrastructure
  • Assumes the RPC provider is reliable and honest
Verification Mode (trust disabled, false):
  • All fetched blocks have their hashes verified against the requested hashes
  • Protects against malicious RPC providers returning incorrect blocks
  • Recommended for public or third-party RPC endpoints
  • Small performance overhead due to hash verification

Examples

Using trusted local RPCs (default):
Using untrusted public RPCs:
Mixed trust configuration:

Security Recommendations

  1. Local Infrastructure: Keep the default true setting for RPCs you control
  2. Public RPCs: Always set --trust-rpc false when using third-party endpoints
  3. Shared Infrastructure: Consider setting --trust-rpc false as a precaution
  4. Performance Testing: The verification overhead is minimal but can be measured in high-throughput scenarios