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
Let’s also improve it to post a comment on the PR like the k8s diff bot and not count as a CI failure. The comment can come with warnings: “did a hardfork timestamp change? triple check to avoid chain splits!”
Let’s also improve it to print a diff when a new chain is added, not just a modification to an existing chain.
Let's update the registry readme (adding a new chain section). It should explain that a diff should be expected and the PR author should check to see it makes sense.
geoknee
changed the title
SuperchainRegistry: improve the rollup-config-diff tool
SuperchainRegistry: improve the rollup-config-diff tool to print a diff for op-geth as well as op-node
Jul 10, 2024
bitwiseguy
changed the title
SuperchainRegistry: improve the rollup-config-diff tool to print a diff for op-geth as well as op-node
SuperchainRegistry: improve the diff tools
Jul 10, 2024
It should:
genesis-diff
tool #379https://www.notion.so/oplabs/Superchain-Registry-Failure-Modes-and-Recovery-Path-Analysis-f863f6e4e4bb49a5894f43d404319d8c?pvs=4#69687a82ff504460a3d070e550123d56
The text was updated successfully, but these errors were encountered: