mev-geth can't connect to prysm beacon client

[sirgarfieldc]

System information

Geth version: v1.10.19-mev0.6.1
OS & Version: Linux
Commit hash : 2e855b3

Expected behaviour

Starting mev-geth with cmd below to accept beacon client connection via localhost:8551

mev-geth/build/bin/geth --datadir geth --mainnet --syncmode snap --http --ws  --authrpc.addr localhost --authrpc.port 8551 --authrpc.vhosts localhost --authrpc.jwtsecret /root/workspace/prysm/jwt.hex

then starting prysm client

./prysm.sh beacon-chain --execution-endpoint=http://localhost:8551 --jwt-secret=/root/workspace/prysm/jwt.hex

Expecting prsym to connect to mev-geth via port 8551. Prsym was able to connect to official go ethereum client.

Actual behaviour

prsym can not connect to mev-geth via port 8551

Steps to reproduce the behaviour

Backtrace

[backtrace]

When submitting logs: please submit them as text and not screenshots.

[shea851]

I had this same issue, but changed to use the ipc socket instead and it began to communicate.

However, another problem came up: Served engine_exchangeTransitionConfigurationV1 err="the method engine_exchangeTransitionConfigurationV1 does not exist/is not available"

Same version of mev-geth as you have above.

[Code0x2]

Mev-geth is reaching EOL come the merge, however I am maintaining a fork of geth that will have callBundle and other searcher features here

[shea851]

Mev-geth is reaching EOL come the merge, however I am maintaining a fork of geth that will have callBundle and other searcher features here

Thanks for the info and link. Just curious, without this fork, how would one simulate bundles after the fork ?

[Code0x2]

Mev-geth is reaching EOL come the merge, however I am maintaining a fork of geth that will have callBundle and other searcher features here

Thanks for the info and link. Just curious, without this fork, how would one simulate bundles after the fork ?

You could add the function yourself to whatever execution client you're using

[sambacha]

Mev-geth is reaching EOL come the merge, however I am maintaining a fork of geth that will have callBundle and other searcher features here

Thanks for the info and link. Just curious, without this fork, how would one simulate bundles after the fork ?

if you want as well we can expose this rpc method post merge on our end