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
Currently, superchain config does not have any information about the deployed contract implementation addresses for the contract set in a release. It would be nice to have superchain registry be the source of truth for this information so that other components such as op-stack-manager and even the chain validation code in superchain registry can refer to this.
Hello @vdamle
Hope you are doing well
I have checked superchain github and very interested in this project
I would love to engage in your team
is there any opportunity to work with you?
Currently, superchain config does not have any information about the deployed contract implementation addresses for the contract set in a release. It would be nice to have superchain registry be the source of truth for this information so that other components such as
op-stack-manager
and even the chainvalidation
code in superchain registry can refer to this.See discord thread
In addition, we also found that this information is necessary to perform MCP L1 upgrade on certain legacy chains.
The text was updated successfully, but these errors were encountered: