Skip to content
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

[MANDATORY] Ecotone upgrade and snap sync support #133

Merged
merged 12 commits into from
Mar 10, 2024

Conversation

Chomtana
Copy link
Collaborator

For existing node operators

Existing operators upgrading to this release should include OP_NODE__L1_BEACON=<YourBeaconNodeEndpoint> in the .env file before restarting the docker-compose

In case you don't have a beacon node available, you can use QuickNode for the beacon endpoint. For example: https://xxx-xxx-xxx.quiknode.pro/db55a3908ba7e4e5756319ffd71ec270b09a7dce

Changes

  1. Bump op-node to version v1.7.1 which is a mandatory upgrade for Ecotone
  2. Snap sync support
  3. Expose an extra port 39393 for op-geth p2p (Changed from the default port 30303 to prevent conflict with the operator's Ethereum node)
  4. Base mainnet and sepolia support

Troubleshooting

Walking back L1Block with curr=0x0000...:0 next=0x0000...:0

If you experience "walking back L1Block with curr=0x0000...:0 next=0x0000...:0" for a long time after the Ecotone upgrade, consider these fixes:

  1. Wait for a few minutes. This issue usually resolves itself after some time.
  2. Restart docker compose: docker compose down and docker compose up -d --build
  3. If it's still not working, try setting OP_GETH__SYNCMODE=full in .env and restart docker compose

@Chomtana Chomtana merged commit a14fb44 into smartcontracts:main Mar 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant