fix: create l1-chain-config artifact and wire to op-node (#404) #408

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open

gologo13 wants to merge 1 commit into ethpandaops:main from gologo13:fix-404

gologo13 commented Jan 19, 2026

Summary:

Create an L1 chain config artifact for local L1s and pass it through the L2/CL launch flow.
Update op-node to mount/use the chain config artifact and pass --rollup.l1-chain-config.
Adjust the hildr launcher signature and CL launcher tests to accept the new argument.

Testing:

kurtosis-test . ✅
kurtosis lint --format . ✅
devnet started with network-config.yaml using op-node later than v1.16.1

Related:

op-node:v1.16.1 fails to start due to missing L1 chain config file #404


          fix: create l1-chain-config artifact and wire to op-node (ethpandaops…

439c5d0

…#404)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet