-
Notifications
You must be signed in to change notification settings - Fork 51
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
Testnet node is always ~12 hours and 50 minutes behind #11
Comments
I tried again from the latest snapshot in https://bwarelabs.com/snapshots/blastl2 and the node forked again..
block with "hash":"0xb631cd788e1425f2dba305f2b52331d6858a4e5a52f830ca52f9fa06339acd67" is not a valid blast testnet block |
tried to use op-wheel to set geth back to the snapshot block,.. however the blast-geth does not support debug_chainConfig method
|
as per https://safe-violet-16b.notion.site/Blast-Deployment-Docs-b2f2b7b3c9a645fe8d6ce49fb963a467, we need to use sepolia-testnet branch. "If you’d like to run a sepolia node, you’ll need to use the sepolia-testnet branch of the blast repo." |
Our Blast testnet node is always around ~12 hours and 50 minutes behind the latest block and it is unable to catch up.
Basically, the node is forking from the network and keeps producing blocks...
We tried to recover the node using https://bwarelabs.com/snapshots/aptos snapshot ... it synced until it gets around 12-13 hours behind and it is unable to catch up.
Logs
op-geth
op-node
Configuration
op-geth
op-node
Related
Related with the following issues:
The text was updated successfully, but these errors were encountered: