You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running on kiln testnet pre-merge, lodestar sometimes ends up with ETH1_ERROR_NON_CONSECUTIVE_LOGS which resolves itself on a restart of lodestar (without restarting ethereumjs). This got resolved each time via a restart.
Investigate/discuss and brainstorm and fix if any issue. The current hypothesis is PoW chain reorged which caused the deposit history to alter as the follow distance is just 16. restarting lodestar resets its tracker and everything gets back on track.
Running on kiln testnet pre-merge, lodestar sometimes ends up with
ETH1_ERROR_NON_CONSECUTIVE_LOGS
which resolves itself on a restart of lodestar (without restarting ethereumjs). This got resolved each time via a restart.Investigate/discuss and brainstorm and fix if any issue. The current hypothesis is PoW chain reorged which caused the deposit history to alter as the follow distance is just 16. restarting lodestar resets its tracker and everything gets back on track.
The text was updated successfully, but these errors were encountered: