Selecting MEV Relays

You will need ssh access or connect a screen to your dappnode to complete this step.

Dappnode has a set of MEV Boost relay endpoints that you can select in the Staker tab, as shown in the previous page. You might not have a great connection to all of them and a high latency could lead to proposal misses in extreme cases.

On the machine running your node, run this script developed by Obol to check your MEVBoost relay latency:

docker run -it obolnetwork/charon:v1.1.0 alpha test mev --endpoints=https://0xa15b52576bcbf1072f4a011c0f99f9fb[e-mail],https://0xa7ab7a996c8584251c8f925da3170bdf[e-mail],https://0x8b5d2e73e2a3a55c6c87b8b6eb92e014[e-mail],https://0xb0b07cd0abef743db4260b0ed50619cf[e-mail],https://0xb3ee7afcf27f1f1259ac1787876318c6[e-mail],https://0xac6e77dfe25ecd6110b8e780608cce0d[e-mail],https://0xa1559ace749633b997cb3fdacffb890a[e-mail],https://0x8c4ed5e24fe5c6ae21018437bde14769[e-mail]

In this script, you can input any mev-relay endpoint after "endpoints=". Add the ones your dappnode uses.

You can find the MEVBoost endpoints your dappnode can connect to by going to "Packages"-> "MEVBoost" -> Config. There you will find your relays:

Copy this text, these are the relay endpoints.

The output should look like this:

...
https://0xa7ab7a996c8584251c8f925da3170bdf[e-mail]
ping                                                            OK
pingMeasure                                        186.935525ms Poor

https://0xa1559ace749633b997cb3fdacffb890a[e-mail]
ping                                                            OK
pingMeasure                                         84.627757ms Avg

...

Usually you will have some relays with poor performance, meaning more than 100ms latency. You should remove those and stay connected to all relays with good or average performance.

This works the same way with MEV Boost Holesky.