Skip to content

Commit

Permalink
Update docs/run/prepare/test-command.md
Browse files Browse the repository at this point in the history
Co-authored-by: Oisín Kyne <[email protected]>
  • Loading branch information
KaloyanTanev and OisinKyne authored Nov 29, 2024
1 parent 6800206 commit 004f1ad
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/run/prepare/test-command.md
Original file line number Diff line number Diff line change
Expand Up @@ -175,7 +175,7 @@ docker run obolnetwork/charon:v1.1.2 test validator

## Test MEV relay

Run tests towards MEV relay(s), to evaluate its effectiveness for a Distributed Validator cluster. If a MEV-Boost instance is configured for the validator node, it is of utmost importance that the connection to the relays it connects to is fast and reliable. If not, the chance of missing a block proposal increases significantly, because of a slow building of the block from the MEV. It is possible to also run a load test towards the MEV relay(s), where an actual block building will take place. This can be done by supplying `--load-test` flag and a second flog where beacon node endpoint is specified: `--beacon-node-endpoint`.
Run tests towards MEV relays, to evaluate their effectiveness for a Distributed Validator cluster. If MEV-Boost clients are configured for the distributed validator nodes, it is of utmost importance that the relays they connect to are fast and reliable. If not, the chance of missing a block proposal increases significantly. Supplying `--beacon-node-endpoint` and `--load-test` flags allows the test to ask relays for real MEV headers, increasing the accuracy (and duration) of this test.

At least 1 endpoint is required to be supplied to the `--endpoints` flag.

Expand Down

0 comments on commit 004f1ad

Please sign in to comment.