Closed Chomtana closed 8 months ago
Existing operators upgrading to this release should include OP_NODE__L1_BEACON=<YourBeaconNodeEndpoint> in the .env file before restarting the docker-compose
OP_NODE__L1_BEACON=<YourBeaconNodeEndpoint>
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
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
docker compose up -d --build
OP_GETH__SYNCMODE=full
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