[OP Stack Deployment] Incorrect L1 Genesis Block Hash Error When Starting op-node #838
Replies: 2 comments 6 replies
-
please provide your rollup.json try to relace the expected 0xebd4d8820e2f0a63ef4630456ee9f23a0d76f43dcf28c049e987e9a0fb325885" with the rollup.json's l1 block hash frist, |
Beta Was this translation helpful? Give feedback.
6 replies
-
Since the original issue has been resolved, I will close this discussion, but we can still discuss new issues here or open a new discussion |
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
I'm following the official Optimism OP Stack "Creating your own L2 rollup testnet" tutorial and running op-node v1.12.0. After deploying contracts and generating config files with op-deployer and successfully running op-geth, I attempt to start my node with the following command:
./bin/op-node \ --l2=http://localhost:8551 \ --l2.jwt-secret=./jwt.txt \ --sequencer.enabled \ --sequencer.l1-confs=5 \ --verifier.l1-confs=4 \ --rollup.config=./rollup.json \ --rpc.addr=0.0.0.0 \ --rpc.port=8547 \ --p2p.disable \ --rpc.enable-admin \ --p2p.sequencer.key=$GS_SEQUENCER_PRIVATE_KEY \ --l1=$L1_RPC_URL \ --l1.rpckind=$L1_RPC_KIND \ --l1.beacon="https://ethereum-sepolia-beacon-api.publicnode.com/"
Steps already taken:
Despite this, op-node still reports a mismatch between the actual L1 genesis block hash and the expected one from the rollup config.
Looking for guidance on resolving this persistent genesis hash mismatch when following the official OP Stack deployment flow and using a public Sepolia endpoint.
Logs
ERROR[06-19|19:59:51.447] Error initializing the rollup node err="failed to init L1: failed to validate the L1 config: incorrect L1 genesis block hash 0x6f20370b4b334facc1256614b10a4eeab71146e298f1ca8b9bad2bfa9dfdcce9, expected 0xebd4d8820e2f0a63ef4630456ee9f23a0d76f43dcf28c049e987e9a0fb325885"
CRIT [06-19|19:59:51.448] Application failed message="failed to setup: unable to create the rollup node: failed to init L1: failed to validate the L1 config: incorrect L1 genesis block hash 0x6f20370b4b334facc1256614b10a4eeab71146e298f1ca8b9bad2bfa9dfdcce9, expected 0xebd4d8820e2f0a63ef4630456ee9f23a0d76f43dcf28c049e987e9a0fb325885"
Additional Information
No response
Feedback
No response
Beta Was this translation helpful? Give feedback.
All reactions