mev-boost/config.example.yaml at develop · flashbots/mev-boost · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
# Example configuration for mev-boost
# This file can be passed to mev-boost using the -config flag: ./mev-boost -config config.yaml
# the configuration supports hot-reloading, changes to this file will be automatically applied without restarts

# Timeout in milliseconds for get_header requests to relays.
# This value should be less then the timeout on the CL, since
# CL's has their own get_header deadline.
# Default: 950ms
timeout_get_header_ms: 950

# Threshold in milliseconds that marks when in a slot is considered "too late".
# If a getHeader request arrives after this threshold, mev-boost skips all relay requests
# and forces local block building, to reduce the risk of missed slot.
# Default: 2000ms
late_in_slot_time_ms: 2000

# Relay Configurations
# Each relay can be configured individually. Relays can also be provided via cli using
# the -relay flag. Cli provided relays will be merged with config file relays.

relays:
  # Relay with timing games enabled
  # Timing games allow mev-boost to send multiple requests at strategic intervals
  # to capture the latest, most valuable bids right before the proposal deadline.
  - url: https://0x9000009807ed12c1f08bf4e81c6da3ba8e3fc3d953898ce0102433094e5f22f21102ec057841fcb81978ed1ea0fa8246@relay.relayer1.net
    # Enable timing games strategy for this relay.
    # When enabled, mev-boost will delay the first request and send multiple follow up requests.
    # Default: false
    enable_timing_games: true

    # Target time in milliseconds when the first getHeader request should be sent.
    # Only used when enable_timing_games is true.
    # Example: 200 means wait until 200ms before sending the first request.
    target_first_request_ms: 200

    # Interval in milliseconds between subsequent getHeader requests to the same relay.
    # After the first request, mev-boost will keep sending new requests every frequency_get_header_ms
    # until the global timeout budget (maxTimeout) is exhausted.
    # Only used when enable_timing_games is true.
    # Example: 100 means send a new request every 100ms.
    frequency_get_header_ms: 100

  # Relay with timing games disabled (standard behavior)
  # This relay will receive a single getHeader request immediately when the CL
  # calls mev-boost, following the standard mev-boost behavior.
  - url: https://0x9000009807ed12c1f08bf4e81c6da3ba8e3fc3d953898ce0102433094e5f22f21102ec057841fcb81978ed1ea0fa8246@relay.relayer2.com
    # Disable timing games - use standard single-request behavior
    enable_timing_games: false

    # These values are ignored when enable_timing_games is false
    target_first_request_ms: 0
    frequency_get_header_ms: 0

# Relay Muxing Configuration (optional)
# Allows different validators to use different relay sets for getHeader requests.
# each validator pubkey must belong to at most one mux group.

mux:
  # Unique identifier for this mux group
  - id: "lido"
    # List of validator pubkeys that belong to this group
    validator_pubkeys:
      - "0x8a1d7b8dd64e0aafe7ea7b6c95065c9364cf99d38470c12ee807d55f7de1529ad29ce2c422e0b65e3d5a05c02caca249"
      - "0x8b1d7b8dd64e0aafe7ea7b6c95065c9364cf99d38470c12ee807d55f7de1529ad29ce2c422e0b65e3d5a05c02caca250"
    # optional, per mux override falls back to global default
    timeout_get_header_ms: 900
    # optional, per mux override falls back to global default
    late_in_slot_time_ms: 1500
    # relay configurations specific to this group (supports timing games)
    relays:
      - url: https://0x9000009807ed12c1f08bf4e81c6da3ba8e3fc3d953898ce0102433094e5f22f21102ec057841fcb81978ed1ea0fa8246@lido-relay.example.com
        enable_timing_games: true
        target_first_request_ms: 200
        frequency_get_header_ms: 100
  - id: "rocket-pool"
    validator_pubkeys:
      - "0x8d1d7b8dd64e0aafe7ea7b6c95065c9364cf99d38470c12ee807d55f7de1529ad29ce2c422e0b65e3d5a05c02caca252"
    relays:
      - url: https://0x9000009807ed12c1f08bf4e81c6da3ba8e3fc3d953898ce0102433094e5f22f21102ec057841fcb81978ed1ea0fa8246@rocketpool-relay.example.com