Replies: 2 comments 7 replies
-
|
Beta Was this translation helpful? Give feedback.
5 replies
-
From what I understand, op-deployer still seems to be under active development,
|
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.
-
Did you check the documentation?
Did you check for duplicate questions?
Issue Description
I'm working on a Move and OP stack combining setup involves using a locally running geth node. I've been using a pre fault games version of OP stack and am finally trying to go through the upgrade process. For that I used to rely on the legacy deployment method via state dumping, calling
Deploy.s.sol
and config generation withop-node
, but am now trying to do it with a deployer.I first go through the bootstrap process as outlined in the docs, and all the bootstrap steps (proxy -> superchain -> implementations) are applied successfully. Then I run
op-deployer init --l2-chain-ids=42069 --l1-chain-id=1337 --intent-type custom
, modify the intent as below and try to apply it as a live deployment strategy, but it fails with below logs.Surprisingly, changing to deployment target as calldata succeeds, but then the whole deployment fails further down the line with a genesis block mismatch in
op-node
(for which I've seen recent open discussions here). What would be the most foolproof way to make the deployment work or is there any piece of documentation I'm missing? I went through all the docs on the site I could find, markdown files in the deployer package, issues and now down to the source code level, but that's taking forever.Logs
The
intent.toml
isand the
op-deployer
logs areAdditional Information
op-deployer
version 0.3.3, batcher/op-geth/proposer built on1.13.4
tag, geth version 1.15.11.The command to run geth:
Feedback
No response
Beta Was this translation helpful? Give feedback.
All reactions