-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
l2 network rollup stuck #13809
Comments
Can you share the CLI flags / env vars you use to configure the op-node / op-geth / op-batcher? The batcher seems to be getting stuck on invalid blocks, which might mean the op-node or op-geth node are not set up right. And it appears like the sequencing-window has expired, forcing the op-node verifier to generate batches, to ensure liveness. This is worst-case scenario, it happens if the batcher is not doing its job. Also double check the batcher signs batches with the same key as that the chain was configured with to trust (the batcher address). |
Sure
op-node
op-batcher
and last op-proposer
|
Bug Description
Network reset at any time.
Steps to Reproduce
Environment Information:
Configurations:
Use branch tutorials/chain
env from file .envrc
L1_RPC_KIND=debug_geth
config network use by default. Only change l2ChainID
Logs:
Op-batcher
Op-geth
op-node logs
Additional context
I restarted the network several times, same problem. Network uptime varies
The text was updated successfully, but these errors were encountered: