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
We should make it easy for chains to opt into receiving hardforks even if they are not fully standard yet, I think that will tend to increase the usage of the --network flags. At the moment, they are automatically opted in when they promote to a standard chain, but we should explicitly document that they can opt in whenever they like.
We should make it easy for chains to opt into receiving hardforks even if they are not fully standard yet, I think that will tend to increase the usage of the --network flags. At the moment, they are automatically opted in when they promote to a standard chain, but we should explicitly document that they can opt in whenever they like.
We could have a flag in the
.env
file to declare opt-in, and theadd-chain
tool checks for that and setssuperchain_time
accordingly. See https://github.com/ethereum-optimism/superchain-registry/blob/main/docs/hardfork-activation-inheritance.mdThe text was updated successfully, but these errors were encountered: