Summary
When using kona-node with Kurtosis devnets that have custom L1 chain IDs (like 3151908), kona-node fails to start because it can't find L1 configuration for the non-standard chain ID.
Error
Error: Failed to find l1 config for chain ID 3151908: ChainIDDoesNotExist(3151908)
Root Cause
kona-node requires the --l1-config-file (or --rollup-l1-cfg) argument to be provided when running on custom devnets. Without this, it tries to look up L1 config from a registry of known chains, which fails for custom devnet chain IDs.
Proposed Fix
Add --l1-config-file support to the kona-node launcher in src/cl/kona-node/launcher.star. This should point to the L1 genesis config file that Kurtosis generates for the devnet.
References
Context
This was discovered while trying to run conductor tests with kona-node on Kurtosis devnets.
Summary
When using kona-node with Kurtosis devnets that have custom L1 chain IDs (like 3151908), kona-node fails to start because it can't find L1 configuration for the non-standard chain ID.
Error
Root Cause
kona-node requires the
--l1-config-file(or--rollup-l1-cfg) argument to be provided when running on custom devnets. Without this, it tries to look up L1 config from a registry of known chains, which fails for custom devnet chain IDs.Proposed Fix
Add
--l1-config-filesupport to the kona-node launcher insrc/cl/kona-node/launcher.star. This should point to the L1 genesis config file that Kurtosis generates for the devnet.References
Context
This was discovered while trying to run conductor tests with kona-node on Kurtosis devnets.