Skip to content

kona-node launcher needs --l1-config-file support for custom devnet chains #406

@Himess

Description

@Himess

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions