Overview
kona-node performs the same protocol role as op-node: it reads batch data and deposits from the data availability layer, derives the canonical L2 chain, and drives an execution-layer client (such as op-reth) through the Engine API. It also participates in the unsafe-block gossip network and can run in sequencer mode. It exists to bring client diversity to the OP Stack: with independent rollup node implementations, a bug in one client cannot take down every node on a chain. Kona is in active development and kona-node should be considered experimental. Who runs it: node operators, as the consensus-layer half of a node stack, paired with an execution client. Chain operators can also run it in sequencer mode.Get started
- Install kona-node: pre-built binaries, Docker images, or building from source. Check the system requirements first.
How-tos
- Run a node: using the binary or the Docker recipe, including how sync works and RPC trust considerations.
- Run a sequencer node: flags, key management, and example configurations for sequencer mode.
- Monitoring: logging, Prometheus metrics, and Grafana dashboards.
Configuration & flags reference
- kona-node CLI reference: every
CLI flag and environment variable for the
nodesubcommand, plus default ports and default runtime behavior. kona-nodesubcommands: the other subcommands the binary ships.- JSON-RPC reference: the P2P, rollup, and admin RPC namespaces.
Releases
Source & spec links
- Source:
rust/kona/bin/nodein the Optimism monorepo. - Kona developer documentation: the Kona project book, covering the node’s design internals and the SDK its components are built from.
- Rollup node specification: the normative definition of the rollup node’s role.