[OP Stack Deployment] upgrade to op-contracts/v2.0.0 #803
Replies: 1 comment 1 reply
-
It looks like this part of the script — [SuperchainAddressRegistry.sol#L105](https://github.com/ethereum-optimism/superchain-ops/blob/main/src/improvements/SuperchainAddressRegistry.sol#L105) — references the [superchain-registry at commit 0831c25](https://github.com/ethereum-optimism/superchain-registry/tree/0831c2509152b457d865634616925ca6240b219e), which contains hardcoded contract addresses. If your chain is not a member of the Superchain, it’s likely that your addresses won’t be included in that registry. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Did you check the documentation?
Did you check for duplicate questions?
Issue Description
I'm currently working on upgrading to op-contracts/v2.0.0 using the superchain-ops.
I have create the new task using the OPCMUpgradeV200.sol template.
In the config.toml file i have used this addresses
[addresses]
OPCM = "0x1B25F566336F47BC5E0036D66E142237DcF4640b"
StandardValidatorV200 = "0x37739a6b0a3F1E7429499a4eC4A0685439Daff5C"
Poa="address of proxy Admin (safe account)"
when I run the simulation command , I encounter the following error:
SIMULATE_WITHOUT_LEDGER=1 just --dotenv-path ${PWD}/.env --justfile ../../../single.just simulate POA
error message :
└─ ← [Revert] revert: OPCMUpgradeV200: upgrade call failed in _build.
1.What are the possible causes of _build failing during simulation?
2. Are there any prerequisites or manual steps needed before simulating the v2.0.0 upgrade?
Let me know if logs or configs would help further.
Thanks!
Logs
No response
Additional Information
No response
Feedback
No response
Beta Was this translation helpful? Give feedback.
All reactions