kona-node
A modular, robust rollup node implementation for the OP Stack built in rust.
Installation
You can install kona-node directly from crates.io using Cargo:
Usage
Basic Command Structure
Available Subcommands
node(alias:n) - Runs the consensus node for OP Stack rollup validationnet(aliases:p2p,network) - Runs the networking stack for the noderegistry(aliases:r,scr) - Lists OP Stack chains available in the superchain-registrybootstore(aliases:b,boot,store) - Utility tool to interact with local bootstoresinfo- Get information about OP Stack chains
Running the Consensus Node
The primary use case is running the consensus node with the node subcommand:
Example: OP Sepolia Configuration
Here's a complete example for running a kona-node connected to OP Sepolia:
# Set required environment variables
# Run the node
Configuration via Environment Variables
Many configuration options can be set via environment variables:
KONA_NODE_L1_ETH_RPC- L1 execution client RPC URLKONA_NODE_L1_BEACON- L1 beacon API URLKONA_NODE_L2_ENGINE_RPC- L2 engine API URLKONA_NODE_L2_ENGINE_AUTH- Path to L2 engine JWT secret fileKONA_NODE_MODE- Node operation mode (default: validator)RUST_LOG- Logging configuration
Example using environment variables:
Help and Documentation
Use the --help flag to see all available options and subcommands:
# General help
# Help for specific subcommands
Networking and P2P
Run just the networking stack:
Registry Information
List available OP Stack chains:
Get information about a specific chain:
Requirements
- L1 Execution Client: Access to an Ethereum L1 execution client RPC endpoint
- L1 Beacon API: Access to an Ethereum L1 beacon chain API endpoint
- L2 Execution Client: Access to an OP Stack L2 execution client (e.g., op-reth)
- JWT Secret: A JWT secret file for authenticated communication with the L2 execution client
Advanced Configuration
For production deployments and advanced configurations, refer to the docker recipe in the main repository at docker/recipes/kona-node/ which provides a complete setup example with monitoring and multiple services.