Stader - ETHx
  • Introduction
    • Explore ETHx
    • ETHx Tech blogs
    • ETHx Governance
  • Launch Incentives
    • ETHx Stakers
    • ETHx Node Operators
      • ETHx Boosted Commission
      • 13000 $SD top-up pool
      • $65000 Reward pool for AVADO user
  • ETHx Staking
    • Guides
    • FAQs
  • Node Operator
    • Staking on Ethereum
      • What is Ethereum staking?
      • ETH staking rewards and penalties
      • Solo-staking vs ETHx
    • Permissionless node operator
      • Responsibilities of a node operator
      • Pre-requisite
      • Node registration and adding validators
        • Step 1: Hardware and platform
          • DIY kit
          • Cloud services
          • VPS services
          • AVADO
          • Allnodes
        • Step 2: Download Stader node
        • Step 3: Install Stader node
        • Step 4: Configure Stader services
          • Step 4.1 Network selection
          • Step 4.2 ETH client configuration
          • Step 4.3 ETH1 - Execution client selection
          • Step 4.4 ETH2 - Consensus client selection
          • Step 4.5 Add a graffiti
          • Step 4.6 Add checkpoint URL
          • Step 4.7 Enable Doppelganger protection
          • Step 4.8 Add fallback clients
          • Step 4.9 Enable monitoring
          • Step 4.10 MEV Boost
          • Confirmation and configuration settings
        • Step 5: Execution and Consensus client sync
        • Step 6: Wallet setup
        • Step 7: Register your node on the Stader network
        • Step 8: Deposit SD collateral
        • Step 9: Deposit ETH bond
        • Validator States
      • ETHx rewards for permissionless node operators
        • Socializing Pool
        • SD rewards
        • Claim CL rewards
        • Claim EL and SD rewards
      • Node Monitoring
      • Node Migration
      • Validator exits and node termination
      • Latest update
      • CLI Command sheet
    • Permissioned node operator
      • Pre-requisite for permissioned node operators
      • Web3Signer setup guide
      • Node registration and adding validators
        • Step 1: Download Stader node
        • Step 2: Install Stader node
        • Step 3: Configure and start Stader services
        • Step 4: Wallet setup
        • Step 5: Set the fee recipient of your validator client to Stader socializing pool
        • Step 6: Check Docker and node status
        • Step 7: Operator address whitelisting
        • Step 8: Register you node on the Stader network
        • Step 9: Add validators to your node
        • Step 10: Check your node and validator status
      • ETHx rewards for permissioned node operators
        • Claim CL rewards
        • Claim EL rewards
      • Node Migration
      • Latest update
    • FAQs
  • Smart Contracts
  • Oracles
  • ETHx Security
    • Immunefi Bug Bounty
    • Audit Reports
    • Public Repositories
  • ETHx Integration
  • Connect with us
Powered by GitBook
On this page
  • What is MEV?
  • What are Block builders and Relays?
  • What is MEV Boost?
  • Please note that it is mandatory for node operators to choose an MEV option during ETH client configuration.
  • If your prefer a locally managed MEV Boost:
  • If your prefer a externally managed MEV Boost:
  1. Node Operator
  2. Permissionless node operator
  3. Node registration and adding validators
  4. Step 4: Configure Stader services

Step 4.10 MEV Boost

PreviousStep 4.9 Enable monitoringNextConfirmation and configuration settings

Last updated 1 year ago

What is MEV?

Maximal Extractable Value (MEV) has emerged as a significant concept on the Ethereum network. It refers to the maximum potential value that can be extracted from the execution of transactions on a blockchain network, often through the manipulation of transaction ordering and inclusion.

When a validator creates a , the usual approach involves a simple algorithm: maintaining a list of pending transactions, bundling as many as possible into the block being built, and submitting the block to the chain. MEV arises from the opportunities presented by the inherent transparency of blockchain networks, specifically the ability to observe the publicly accessible pool of pending transactions, also known as the .

The transaction visibility on the mempool empowers validators to employ sophisticated and clever algorithms to manipulate the order of these pending transactions and, in certain instances, introduce new transactions between them to directly or indirectly profit.

MEV introduces risks such as , , and other transaction manipulation techniques, which can exploit the sequential nature of transaction execution. Therefore, MEV relays have emerged as a solution to address the challenges and concerns surrounding MEV in blockchain networks.

What are Block builders and Relays?

We discussed MEV and how validators can profit using MEV techniques. However, discovering MEV opportunities is not an easy task; it is quite challenging. This process requires powerful systems and complex algorithms that operate at high speeds to swiftly identify and extract MEV. These tasks are performed by state-of-the-art opportunity finders known as . Once an opportunity is discovered by the Searchers, they are shared with block builders who gather them to form complete Ethereum blocks.

One advantage for block builders is the visibility of validators assigned to each slot for an epoch. This information becomes visible to everyone a few minutes in advance. This advanced knowledge has enabled block builders to create entities where validators can register themselves for upcoming block proposals. Block builders can then submit bids for the blocks they want the validators to propose. Validators evaluate these bids and choose the one that offers the highest profit, proposing that block instead of creating their own. This entity where block builders and validators interact is known as a Relay.

MEV relays are actively being researched and developed by the Ethereum blockchain community. The goal is to create a more secure, efficient, and equitable environment for validators, decentralized applications, and end users.

What is MEV Boost?

We discussed MEV relays and how they help the validators above, however, navigating multiple relays and ensuring your node is registered and connected to each of them can be a daunting task. This is where MEV Boost helps us. MEV Boost, developed by Flashbots, is an middleware that enables validators to participate in a competitive block-building market. It serves as an implementation of specifically designed for proof-of-stake (PoS) Ethereum networks.

MEV Boost simplifies relay management by establishing communication with multiple relays which a validator has selected. So, the validator doesn't need to navigate through all the selected relays, MEV Boost operates and takes charge of the necessary tasks, such as registration, bidding, blind signing, and proposal management in collaboration with your Consensus client.

Please note that it is mandatory for node operators to choose an MEV option during ETH client configuration.

Node operators can select an MEV option provided under locally or externally managed:

  • Locally managed: Choose this option if you would like Stader Node to take care of the MEV Boost client for you

  • Externally managed: Choose this option if you would like to use and externally managed MEV Boost client.

If your prefer a locally managed MEV Boost:

You can select regulated or unregulated of both type of MEV. Below is the description of regulated and unregulated

  • Regulated: Choose this option to activate relays that adhere to government regulations such as OFAC sanctions. "Regulated (All MEV Types)" permits all forms of MEV, including sandwich attacks.

    Relays for regulated type MEV: Blocknative, BloXroute regulated, Flashbots and Eden Network.

  • Unregulated: Choose this option to activate relays that don't adhere to any sanctions lists and won't censor transactions. Unregulated (All MEV Types) permits for all forms of MEV, including sandwich attacks. (except BloXroute ethhical)

    Relays for unregulated type MEV: BloXroute ethical, Ultra Sound and bloXroute Max Profit

If your prefer a externally managed MEV Boost:

Please enter the externally managed MEV Boost client URL, e.g. http://192.168.1.46:18550

block
mempool
front-running
sandwich attacks
Learn more
Searchers
Learn more
open-source
proposer-builder separation (PBS)
Learn more