[Node Operator Question] Execution Client not syncing with syncmode=execution-layer #720
-
Are you running the most up to date node software?
Did you check the documentation?
Did you check for duplicate questions?
Issue DescriptionHello everyone, I'm having trouble synchronizing op-erigon with the op-node using the Steps to ReproduceStart op-node and op-erigon with the provided config. Which component is affected?
Expected vs. Actual Behaviorop-erigon should sync with op-node option Environment DetailsOS: Ubuntu Protocol Informationop-erigon and op-node use the latest image. Node LogsOP-NODE: OP-ERIGON Troubleshooting AttemptsI have tested multiple configuration of op-node. Additionally, I have also tried op-reth as the execution client. Additional InformationNo response FeedbackNo response |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
snap sync only apply to initial sync,once you catch up on chain head,it will switch back to sync by reading onchain blobs |
Beta Was this translation helpful? Give feedback.
-
I haven't tried it, but I feel it's necessary to use a stable version of op-node image: us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.10.3 |
Beta Was this translation helpful? Give feedback.
I haven't tried it, but I feel it's necessary to use a stable version of op-node image: us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.10.3
Because engineers are discussing whether to delete the syncmode flag