Skip to content

Conversation

geoknee
Copy link
Contributor

@geoknee geoknee commented Oct 2, 2025

I believe this is the right way to implement this flag, as it belongs with the rollup cfg and l2 genesis flags.

@geoknee geoknee marked this pull request as ready for review October 2, 2025 21:11
@geoknee geoknee requested review from a team as code owners October 2, 2025 21:11
@geoknee geoknee requested a review from Inphi October 2, 2025 21:11
@geoknee geoknee linked an issue Oct 2, 2025 that may be closed by this pull request
@geoknee geoknee requested a review from mbaxter October 2, 2025 21:47
EnvVars: envVars,
}
})
L1GenesisFlag = NewVMFlag("l1-genesis", EnvVarPrefix, faultDisputeVMs, func(name string, envVars []string, traceTypeInfo string) cli.Flag {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch! There are also a number of checks (example) that disallow custom chain flags if the Network flag is set. We should also disallow the l1GenesisFlag if a known network is set.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good call, pushed a fix for that.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Noticed a few remaining issues with the validation. Pushed up some changes based on this PR here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants