You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
op-deployer generates SCR files and runs checks for new chains. It looks like these chains are (at least by default) non-standard, non-standard candidate chains: the default standard candidate flag is false.
But op-deployer is often used to deploy both standard candidates and fully standard chains. We need an easy way to make sure that these chains are fully validated with op-deployer inspect (the command that chain deployers run to confirm that a chain has been correctly deployed).
We should probably make the standard checks the default, with an option to run only frontier or standard candidate checks instead.
This might mean one of the following approaches:
Adding a non-standard flag to the op-deployer inspect subcommand
Adding an option for frontier/standard candidate flags to the intents files consumed by op-deployer
The text was updated successfully, but these errors were encountered:
op-deployer generates SCR files and runs checks for new chains. It looks like these chains are (at least by default) non-standard, non-standard candidate chains: the default standard candidate flag is false.
But op-deployer is often used to deploy both standard candidates and fully standard chains. We need an easy way to make sure that these chains are fully validated with
op-deployer inspect
(the command that chain deployers run to confirm that a chain has been correctly deployed).We should probably make the standard checks the default, with an option to run only frontier or standard candidate checks instead.
This might mean one of the following approaches:
op-deployer inspect
subcommandThe text was updated successfully, but these errors were encountered: