[MANDATORY] Ecotone upgrade and snap sync support #133
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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-composeIn 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
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:
docker compose down
anddocker compose up -d --build
OP_GETH__SYNCMODE=full
in .env and restart docker compose