Closed UranusLin closed 5 months ago
Can you share your (Make sure to have secret masked)
# L1 node that the op-node (Bedrock) will get chain data from
OP_NODE__RPC_ENDPOINT=
# Type of RPC that op-node is connected to, see README
OP_NODE__RPC_TYPE=basic
But it's just a warning. If it happen randomly not always it's fine.
We using
# L1 node that the op-node (Bedrock) will get chain data from
OP_NODE__RPC_ENDPOINT=[Our Ethereum Goerli fullnode]
# Type of RPC that op-node is connected to, see README
OP_NODE__RPC_TYPE=basic
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 https://github.com/ethereum-optimism/developers/discussions/88
So core dev can look into that
I've responded in that thread: https://github.com/ethereum-optimism/developers/discussions/88#discussioncomment-7693613, 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: https://github.com/smartcontracts/simple-optimism-node/pull/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.