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
When I synchronize the node data these warnings keep coming up, is it possible to ignore these warnings? Or are there other checkpoints that are more suitable for mev-geth? or is it possible to synchronize the data with geth and prysm first, and then switch the geth to mev-geth after the synchronization is complete?
Actual behaviour
prysm side:
[2023-08-24 11:12:08] WARN initial-sync: Skip processing batched blocks error=could not process block in batch: method not found: received an undefined execution engine error
mev-geth side:
WARN [08-24|11:08:36.295] Served engine_newPayloadV2 conn=127.0.0.1:62081 reqid=6 duration="16.544µs" err="the method engine_newPayloadV2 does not exist/is not available"
System information
Geth version:
geth Version: 1.10.23-stable
OS & Version:Linux
Commit hash : (if
develop
)Expected behaviour
When I synchronize the node data these warnings keep coming up, is it possible to ignore these warnings? Or are there other checkpoints that are more suitable for mev-geth? or is it possible to synchronize the data with geth and prysm first, and then switch the geth to mev-geth after the synchronization is complete?
Actual behaviour
prysm side:
mev-geth side:
Steps to reproduce the behaviour
when sync with checkpoint this warning happens
The text was updated successfully, but these errors were encountered: