Skip to content

EL warning : the method engine_newPayloadV2 does not exist/is not available #150

@kevgithub

Description

@kevgithub

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:

[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"

Steps to reproduce the behaviour

when sync with checkpoint this warning happens

./prysm.sh beacon-chain --execution-endpoint=http://localhost:8551 --jwt-secret=/Users/.../jwt.hex --datadir=/Users/.../data --checkpoint-sync-url=https://beaconstate.ethstaker.cc/ --genesis-beacon-api-url=https://beaconstate.ethstaker.cc/

./mev-geth/build/bin/geth --http --http.api eth,net,engine,admin --authrpc.jwtsecret /Users/.../jwt.hex --datadir /Users/.../data/

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions