update (masked) standard bytecode hash for mips @ op-contracts/v1.6.0 #688
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.
I believe we have the incorrect bytecode hash stored in the standard TOML file for the MIPS contract at the latest governance approved release. This PR updates it to the correct value and gets
just validate 10
passing again.To reproduce this:
op-contracts/v1.6.0
in the monorepoforge build
immutableReferences
field fromforge-artifacts/MIPS.sol/MIPS.json
and updatestandard-immutables.toml
(no semantically meaningful change here actually)cast code 0x16e83cE5Ce29BF90AD9Da06D2fE6a15d5f344ce4
and verify (using https://difff.jp/en/) returned bytecode matches thedeployedBytecode
from the aboveMIPS.json
file, with the immutables filled in with thePreimageOracle
address.standard-bytecodes.toml
with the hash reported by thejust validate 10
command.