MEV Configuration

This guide outlines the necessary steps required to configure MEV within your SSV node to enable operators to participate in proposing MEV blocks for the validators they manage.

Prerequisite: Enable MEV in Beacon Client

Enable MEV by connecting to the Builders API from your Beacon client.
This integration will grant you access to a network of block builders, who collaborate with MEV searchers to produce the most valuable blocks that validators can propose.
Follow the setup guidelines for configuring MEV on your preferred client:
For reference, the ETHStaker community provides a list of MEV relays and their corresponding endpoints.

How to enable MEV in SSV node

Update the config.yaml file in the SSV node to enable MEV for your operator:
BuilderProposals: true
Once the config flag has been updated, rebuild the container and restart the node as outlined in the Installation guide.
It is very important to ensure that Beacon client have been set up with MEV before changing the SSV node configuration to enable it. Failing to do so could result in missed blocks for the validators your operator manages.

Considerations for MEV Relays Selection

In, every time a validator is assigned a block proposal, one operator within its cluster is selected to propose the block. Given that MEV-enabled blocks are broadcasted through relays, only operators supporting the chosen relay can broadcast it to the network.
Consequently, a greater correlation between the relays supported by operators in a cluster enhances the number of operators capable of broadcasting the block proposal, ultimately enhancing the liveness of the proposal duty.
  • Full Relay Correlation: When all operator nodes support the same relays, each node can both sign and broadcast the block, enhancing liveness beyond the industry standard.
  • Partial Relay Correlation: In cases where overlap is lacking, only the operator responsible for proposing the block will broadcast the task. This aligns with the standard liveness of non-DVT validators.
  • Minimal or No MEV Support: If certain cluster operators do not enable MEV (when the count of MEV-enabled operators falls below quorum), consensus might not be reached for the task. This could lead to the block proposal not being executed at all.
  • No MEV Support: In instances where a non-MEV operator proposes the block, the proposal would proceed but without any MEV rewards.
Therefore, it is recommended to support as many relays as possible in your operator setup. The more correlation among supported relays, the higher the liveness for block proposal duties and the greater favorability among stakers during operator selection. This approach minimizes the chances of missed proposals or non-MEV blocks in edge cases, ensuring optimal network performance and alignment with staker expectations.

Showcase Supported Relays

It's crucial for the network to display the relays supported by operators. The availability of this information aids the network's stability by enabling stakers to use it when considering how to form their clusters, thereby preventing the problems highlighted earlier. Additionally, this practice enhances the operator's likelihood of being selected by stakers.
To showcase the relays your operator supports to the network, it's essential to include them in your operator metadata.

How to show supported relays in operator metadata

  1. 1.
    Head over to the Operators Dashboard in the SSV webapp:
Operators Dashboard
  1. 2.
    Navigate to the operator page and click the Edit Details:
Operator Page
  1. 3.
    Choose from the “MEV relays” list and click Update when done.
Edit Metadata Interface
  1. 4.
    Sign the signature request from the Web3 wallet used to sign-in (Metamask, in this case). This is needed to confirm ownership, it is not an actual on-chain transaction (no gas fees required).
Signature Request
  1. 5.
    Success! The new operator metadata should be set and will be visible to everyone in the network.