Run kona-node in sequencer mode from the command line, including required arguments, sequencer-specific flags, and example configurations.
This guide shows how to run kona-node in sequencer mode from the command line. For how sequencer mode works internally and how to configure it programmatically through the Node SDK, see the sequencer mode design page.
Sequencer mode is an advanced configuration primarily used by rollup operators. Most users will run nodes in the default validator mode.
Required ConfigurationSequencer mode requires all standard node arguments plus the --mode=Sequencer flag and a block signer. Missing any required argument will prevent the node from starting.
Argument
Flag
Environment Variable
Description
Mode
--mode
KONA_NODE_MODE
Must be set to Sequencer
L1 RPC
--l1-eth-rpc
KONA_NODE_L1_ETH_RPC
L1 execution client RPC URL
L1 Beacon
--l1-beacon
KONA_NODE_L1_BEACON
L1 beacon API URL
L2 Engine
--l2-engine-rpc
KONA_NODE_L2_ENGINE_RPC
L2 engine API endpoint
JWT Secret
--l2.jwt-secret
KONA_NODE_L2_ENGINE_AUTH
Path to JWT secret file
Chain ID
--chain
KONA_NODE_L2_CHAIN_ID
L2 chain identifier
Block Signer
--p2p.sequencer.key.path, --p2p.sequencer.key, or --p2p.signer.endpoint with --p2p.signer.address
L1 Confirmations: The --sequencer.l1-confs setting determines how many L1 blocks the sequencer waits before using an L1 block as an origin. Higher values provide more safety but increase latency.
Recovery Mode: Use --sequencer.recover=true when the sequencer needs to catch up after being offline.
Conductor Integration: For multi-sequencer deployments, configure the conductor service for proper leader election.
Running a sequencer in production requires careful consideration of infrastructure, monitoring, and failover procedures. Ensure proper JWT secret management and secure network configuration.
Was this page helpful?
Assistant
Responses are generated using AI and may contain mistakes.