-
Notifications
You must be signed in to change notification settings - Fork 133
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
Failed to share forkchoice-updated signal #103
Comments
Can you share your (Make sure to have secret masked)
But it's just a warning. If it happen randomly not always it's fine. |
We using
It's still not syncing, should we re init data and sync from 0? |
I am experiencing this as well. Node is stuck and not syncing. |
Hi @UranusLin @mmd-afegbua I'm forwarding this issue to ethereum-optimism/developers#88 So core dev can look into that |
I've responded in that thread: ethereum-optimism/developers#88 (comment), it looks like this is due to the canyon hardfork on testnets. This repo probably needs the configuration for Canyon and should also migrate over to OP Sepolia for testnets because OP Goerli will not be supported starting next year. |
I opened a PR to fix this issue, but I haven't tested it: #106 |
I am running simple-optimism-node on Goerli and have updated to op-node:v1.3.0, but the op-node can't sync due to the error "Failed to share forkchoice-updated signal".
The op-node logs show:
How can I fix this? Any help is appreciated.
The text was updated successfully, but these errors were encountered: