NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #1374 by repository stars
Latest stable
v1.12.0
Last release 4 months ago
30 Jun 2026
Release timing varies
gaps range from 2 weeks to 7 months
Some releases are documented
notes for 26 of 47 stable releases
Nothing withdrawn
no release was ever pulled
5 years old
143 releases · first in 2022
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Docker Image: `flashbots/mev-boost:1.12`
flashbots/mev-boost:1.12This 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.
...
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.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Docker Image: `flashbots/mev-boost:1.11`
flashbots/mev-boost:1.11This release introduces YAML based configuration with a new Timing Games feature for optimizing bid selection. If you'd like to configure timing games, read the docs here. Docs and example related to config file can be found here.
getHeader calls to optimize bid selection.--log-color flag for colored text output in logs (#871)le (less than or equal) labels (#876)Nothing published for this version
⚠️ This is a required update for the upcoming Fusaka upgrade! ⚠️
⚠️ This is a required update for the upcoming Fusaka upgrade! ⚠️
[!NOTE] The Fusaka upgrade will happen at epoch 411392 (Dec-03-2025 09:49:11 PM UTC).
flashbots/mev-boost:1.10.1getPayload requests to relays in the background after a successful response by @faheelsattar in https://github.com/flashbots/mev-boost/pull/850
GetPayloadV2 to GetPayloadV1 by @klim0v in https://github.com/flashbots/mev-boost/pull/855⚠️ This is a required update for the upcoming Fusaka upgrade! ⚠️
⚠️ This is a required update for the upcoming Fusaka upgrade! ⚠️
[!NOTE] The Fusaka upgrade will happen at epoch 411392 (Dec-03-2025 09:49:11 PM UTC).
Docker Image: flashbots/mev-boost:1.10
Some of the major features added in this release are:
Remove deprecated HeaderStartTimeUnixMS by @alextes in https://github.com/flashbots/mev-boost/pull/749
⚠️ This is a required update for the upcoming Pectra upgrade! ⚠️
[!NOTE] The Pectra upgrade will happen at epoch 364032 (May 7, 2025, 10:05:11am UTC).
Docker Image: flashbots/mev-boost:1.9
.env.example by @thedevbirb in https://github.com/flashbots/mev-boost/pull/696flashbots/mev-boost:1.9Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
MEV-Boost v1.8 includes two noteworthy (albeit minor) changes, and a bit of cleanup and dependency updates.
MEV-Boost v1.8 includes two noteworthy (albeit minor) changes, and a bit of cleanup and dependency updates.
https://github.com/flashbots/mev-boost/compare/v1.7.1...v1.8
https://hub.docker.com/r/flashbots/mev-boost/tags
flashbots/mev-boost:1.8flashbots/mev-boost:latestNothing published for this version
Nothing published for this version
Nothing published for this version
Deneb ready release for mainnet. Required upgrade for upcoming mainnet dencun fork on March 13 13:55:35 UTC.
Deneb ready release for mainnet. Required upgrade for upcoming mainnet dencun fork on March 13 13:55:35 UTC.
If building from source please upgrade to the latest stable go version (1.22.0)
https://github.com/flashbots/mev-boost/compare/v1.6...v1.7
https://hub.docker.com/r/flashbots/mev-boost/tags
flashbots/mev-boost:1.7flashbots/mev-boost:latestNothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Send getPayload requests to all relays (for additional data availability) in https://github.com/flashbots/mev-boost/pull/531
getPayload requests to all relays (for additional data availability) in https://github.com/flashbots/mev-boost/pull/531We're happy to announce that we've obviated the need for portable builds. They've been necessary due to the previously used blst library, which we've replaced with gnark-crypto https://github.com/flashbots/mev-boost/pull/479
From now on, everyone can use the regular builds!
https://github.com/flashbots/mev-boost/compare/v1.5.0...v1.6
https://hub.docker.com/r/flashbots/mev-boost/tags
flashbots/mev-boost:1.6flashbots/mev-boost:latestNothing published for this version
Nothing published for this version
This release is primarily to test the new statically linked builds!
This release is primarily to test the new statically linked builds!
Full Changelog: https://github.com/flashbots/mev-boost/compare/v1.5.0...v1.5.1-alpha1
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Capella decode and fallback to bellatrix by @avalonche in https://github.com/flashbots/mev-boost/pull/431
See this writeup for more information about the Capella changes across the MEV-Boost ecosystem.
mev-boost will retry the getPayload request, in case of network (or other) errors.
GLIBC_2.34 not foundThe previous binaries attached to this release didn't work with Ubuntu 20.04 LTS, and would give you this error:
/lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.34 not found
Resolution:
mev-boost_1.5.0_linux_amd64.tar.gz, sha256: 6356098bdf466cb7907e09a31e9d369a899685f4aa1830f950c2e5ac32b01bec). Re-download from below and all should work!go install github.com/flashbots/mev-boost@latestExec format errorYou're probably using the wrong binary for your operating system architecture.
https://github.com/flashbots/mev-boost/compare/v1.4.0...v1.5.0-alpha2
https://hub.docker.com/r/flashbots/mev-boost/tags
flashbots/mev-boost:1.5.0-portableflashbots/mev-boost:1.5.0flashbots/mev-boost:latestNothing published for this version
Nothing published for this version
Nothing published for this version
Capella decode and fallback to bellatrix by @avalonche in https://github.com/flashbots/mev-boost/pull/431
See this writeup for more information about the Capella changes across the MEV-Boost ecosystem.
https://github.com/flashbots/mev-boost/compare/v1.4.0...v1.5.0-alpha2
https://hub.docker.com/r/flashbots/mev-boost/tags
flashbots/mev-boost:1.5.0-alpha2-portableflashbots/mev-boost:1.5.0-alpha2Capella decode and fallback to bellatrix by @avalonche in https://github.com/flashbots/mev-boost/pull/431
See this writeup for more information about the Capella changes across the MEV-Boost ecosystem.
https://github.com/flashbots/mev-boost/compare/v1.4.0...v1.5.0-alpha1
https://hub.docker.com/r/flashbots/mev-boost/tags
flashbots/mev-boost:1.5.0-alpha1-portableflashbots/mev-boost:1.5.0-alpha1Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Cleanup deprecated testnets from docs by @avalonche in https://github.com/flashbots/mev-boost/pull/368
-min-bid flag) by @allboxes in https://github.com/flashbots/mev-boost/pull/274-log-service cli flag by @metachris in https://github.com/flashbots/mev-boost/pull/355getHeader: print bid value in eth instead of wei by @metachris in https://github.com/flashbots/mev-boost/pull/366Why run mev-boost? in README by @franciscodiazydiaz in https://github.com/flashbots/mev-boost/pull/391$ mev-boost -help
Usage of mev-boost:
-addr string
listen-address for mev-boost server (default "localhost:18550")
-debug
shorthand for '-loglevel debug'
-genesis-fork-version string
use a custom genesis fork version
-goerli
use Goerli
-json
log in JSON format instead of text
-log-no-version
disables adding the version to every log entry
-log-service string
add a 'service=...' tag to all log messages
-loglevel string
minimum loglevel: trace, debug, info, warn/warning, error, fatal, panic (default "info")
-mainnet
use Mainnet (default true)
-min-bid float
minimum bid to accept from a relay [eth]
-relay value
a single relay, can be specified multiple times
-relay-check
check relay status on startup and on the status API call
-relay-monitor value
a single relay monitor, can be specified multiple times
-relay-monitors string
relay monitor urls - single entry or comma-separated list (scheme://host)
-relays string
relay urls - single entry or comma-separated list (scheme://pubkey@host)
-request-timeout-getheader int
timeout for getHeader requests to the relay [ms] (default 950)
-request-timeout-getpayload int
timeout for getPayload requests to the relay [ms] (default 4000)
-request-timeout-regval int
timeout for registerValidator requests [ms] (default 3000)
-sepolia
use Sepolia
-version
only print version
Using multiple -relay flags (and -mainnet is now used by default):
mev-boost -relay-check \
-relay https://0xac6e77dfe25ecd6110b8e780608cce0dab71fdd5ebea22a16c0205200f2f8e2e3ad3b71d3499c54ad14d6c21b41a37ae@boost-relay.flashbots.net \
-relay https://0x8b5d2e73e2a3a55c6c87b8b6eb92e0149a125c852751db1422fa951e42a09b82c142c3ea98d0d9930b056a3bc9896b8f@bloxroute.max-profit.blxrbdn.com \
-relay https://0xb3ee7afcf27f1f1259ac1787876318c6584ee353097a50ed84f51a1f21a323b3736f271a895c7ce918c038e4265918be@relay.edennetwork.io \
-relay https://0x9000009807ed12c1f08bf4e81c6da3ba8e3fc3d953898ce0102433094e5f22f21102ec057841fcb81978ed1ea0fa8246@builder-relay-mainnet.blocknative.com
Setting a minimum bid value of 0.02 ETH:
mev-boost \
-min-bid 0.02 \
-relay https://0xac6e77dfe25ecd6110b8e780608cce0dab71fdd5ebea22a16c0205200f2f8e2e3ad3b71d3499c54ad14d6c21b41a37ae@boost-relay.flashbots.net \
-relay https://0x8b5d2e73e2a3a55c6c87b8b6eb92e0149a125c852751db1422fa951e42a09b82c142c3ea98d0d9930b056a3bc9896b8f@bloxroute.max-profit.blxrbdn.com
Using the -min-bid flag to set a minimum bid value will incur a small opportunity cost and increase the chance of building local mempool blocks. These are the chances per value of building a local block (based on median payload values during the past two weeks):
| min-bid | % chance for building a local block |
|---|---|
| 0.1 ETH | 97.2% |
| 0.06 ETH | 50% |
| 0.03 ETH | 13.5% |
| 0.02 ETH | 2.3% |
| 0.01 ETH | 0.01% |
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.