Generate Genesis Files on an L3 deployment #823
euler-singularity
started this conversation in
General
Replies: 1 comment 2 replies
-
|
After which command does this error appear? |
Beta Was this translation helpful? Give feedback.
2 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.
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
After running this deployer's
applycommand:The contracts are successfully deployed, but it fails to generate the genesis file with the following error:
For the artifacts I am using version
v3.0.0-rc.2I couldn't make the/op-deployer applyrun with any of the other versions.I think the root of the issue is that the downloaded artifact for the
L2Genesis.s.solscript (attached) doesn't match the number of inputs of the L2Genesis used when theGenesisL2is called indeploy.go:As you can see the
if err := genesisScript.Runhas one input (L2GenesisInput), but the abi accepts zero inputs.L2Genesis.json
Anyone has encountered this issue before? For the artifacts, I am using version
v3.0.0-rc.2. I couldn't get the/op-deployer applycommand to run with any of the other versions. So, I don't know how to make the artifacts to match the code.Logs
error in pipeline stage apply: failed to create L2Genesis script: script L2Genesis does not have a method run that accepts an argument of type opcm.L2GenesisInput: ABI arguments don't match Go types: ABI has 0 arguments, Go has 1
Additional Information
No response
Feedback
No response
Beta Was this translation helpful? Give feedback.
All reactions