Roll-op enables you to deploy a rollup (create the genesis file & deploy contracts to L1) and only run it later.
However, since that's two separate commands, you could in theory specify conflicting options to bot. We should store the deploy config (= config specified for deploy) and validate the run config (= config specified to run the rollup) are consistent.
These two configs are allowed to be different! e.g. changing your mind on which ports to bind should affect anything, however, there are options that might be more problematic (TODO: which ones??)
Bonus: currently we don't regenerate the L2 genesis if it exists. We probably always should regenerate it, to avoid the same kind of issue.
Roll-op enables you to deploy a rollup (create the genesis file & deploy contracts to L1) and only run it later.
However, since that's two separate commands, you could in theory specify conflicting options to bot. We should store the deploy config (= config specified for deploy) and validate the run config (= config specified to run the rollup) are consistent.
These two configs are allowed to be different! e.g. changing your mind on which ports to bind should affect anything, however, there are options that might be more problematic (TODO: which ones??)
Bonus: currently we don't regenerate the L2 genesis if it exists. We probably always should regenerate it, to avoid the same kind of issue.