Replies: 1 comment
-
The issue here was that I was using the wrong contracts release for the downloaded op-deployer release. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Did you check the documentation?
Did you check for duplicate questions?
Issue Description
If I try to modify the genesis.json generated from the op-deployer directly, the rollup.json hashes do not properly update. What is the proper way to go about this. in my
intent.toml
file I have this config:l1ContractsLocator = "tag://op-contracts/v2.0.0"
l2ContractsLocator = "file:///Users/powvt/optimism/packages/contracts-bedrock/forge-artifacts/"
Where my l2ContractsLocator is pointing to a local fork of
tag://op-contracts/v1.7.0-beta.1+l2-contracts
where I added in my predeploy contracts to theL2Genesis.s.sol
andPredeploys.sol
. When I runop-deployer apply ...
I get aRevert: Config: unknown fork: holocene
error.When I run
op-deployer apply ...
with thetag://op-contracts/v1.7.0-beta.1+l2-contracts
in config everything works fine...I didnt touch anything related to the fork logic in the contract modifications I made... not sure why it is failing?
Logs
No response
Additional Information
No response
Feedback
No response
Beta Was this translation helpful? Give feedback.
All reactions