Update the chain configuration to match the keys in use so safe head can advance #201
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The previous configuration stored the address
0xafF0CA253b97e54440965855cec0A8a2E2399896for all roles in the protocol, but that key wasn't being used. The batcher uses0xa0Ee7A142d267C1f36714E4a8F75612F20a79720and op-node signs unsafe blocks with0x9965507D1a55bcC2695C58ba16FB37d819B0A4dc. This discrepancy prevented safe head from advancing and op-node peers from successfully processing signed unsafe blocks. These changes fix both issues.op-contracts has been updated to v4.0.0 (via
l1ContractsLocatorandl2ContractsLocator), and op-deployer v0.4.2 was used to regenerate the rollup configuration.