This release allows validators to be grouped into mux groups, each with their own relay set, timeouts, and timing game configurations via the global config file. This enables node operators running multiple validator sets to route getHeader requests to different relays per group.

Example Configuration

Docker Image: <a href=https://hub.docker.com/layers/flashbots/mev-boost/1.12/images/sha256-338d3ef5a7eedd5f3e0b8607af80c3a0ffac68de185d08c4bc88a10165e769a9 rel="nofollow noreferrer noopener" target=_blank> flashbots/mev-boost:1.12
Full Changelog: <a href=https://github.com/flashbots/mev-boost/compare/v1.11...v1.12 rel="nofollow noreferrer noopener" target=_blank> v1.11...v1.12

...
mux:
  - id: "lido"
    validator_pubkeys:
      - "0x8a1d7b..."
    timeout_get_header_ms: 900
    late_in_slot_time_ms: 1500
    relays:
      - url: https://0xpubkey@lido-relay.example.com
        enable_timing_games: true
        target_first_request_ms: 200
        frequency_get_header_ms: 100

  - id: "rocket-pool"
    validator_pubkeys:
      - "0x8d1d7b..."
    relays:
      - url: https://0xpubkey@rocketpool-relay.example.com

Docs and example config can be found here.

🚀 Features

Relay multiplexing by @faheelsattar in #826

flashbots/mev-boost v1.12 on GitHub

Example Configuration

🚀 Features

flashbots/mev-boost v1.12
on GitHub