TL;DR: Flashbots is requesting that working group node operators point mev-boost to Kiln/Ropsten Relay URLs with our provided identifier as soon as possible. Your testing support will ensure the robustness and readiness of mev-boost ahead of The Merge, and is greatly appreciated.

Action Needed from Node Operators

Get your Green Checkmark ✅

Point mev-boost to the testnet Relay URL with your identifier

Green checkmarks on boost.flashbots.net, signifying your readiness, will be assigned to node operators that successfully:

  1. Connect to Kiln/Ropsten Flashbots Relays with your unique working-group identifier (provided in the table below) appended as a URL parameter.
  2. Produce a block on the corresponding testnet.

Steps

  1. Install the latest mev-boost version

  2. Install and configure one of the supported consensus clients. Detailed instructions are available on the mev-boost testing wiki.

  3. Replace <IDENTIFIER> with your unique identifier from the table below, and run mev-boost using the following commands:

    Testnet Relay Commands with Identifiers

    **# Kiln**
    mev-boost -kiln -relays https://0xb5246e299aeb782fbc7c91b41b3284245b1ed5206134b0028b81dfb974e5900616c67847c2354479934fc4bb75519ee1@builder-relay-kiln.flashbots.net<IDENTIFIER>
    
    **# Ropsten**
    mev-boost -ropsten -relays https://0xb124d80a00b80815397b4e7f1f05377ccc83aeeceb6be87963ba3649f1e6efa32ca870a88845917ec3f26a8e2aa25c77@builder-relay-ropsten.flashbots.net<IDENTIFIER>
    

    Example connects to Kiln using the flashbots identifier:

    ./mev-boost -kiln -relays https://0xb5246e299aeb782fbc7c91b41b3284245b1ed5206134b0028b81dfb974e5900616c67847c2354479934fc4bb75519ee1@builder-relay-kiln.flashbots.net**?id=flashbots**

    Identifier Table

    Append Flashbots Relay URLs with your identifier below.

    Note: If you need additional identifiers or are not listed on this table, please complete the node operator testnet setup and notify Kailin (Telegram/Discord: @imkailin) for support.

    Identifier
    Kiln ?id=kiln
    Blockdaemon ?id=blockdaemon
    Blocknative ?id=blocknative
    Bitcoin Suisse ?id=bitcoin-suisse
    Coinbase Cloud ?id=coinbase
    Chorus One ?id=chorus-one
    Consensys Codefi ?id=consensys
    ETHPool ?id=bitfly
    Figment ?id=figment
    Foundry ?id=foundry
    Lido ?id=lido
    P2P ?id=p2p
    Rocketpool ?id=rocketpool
    RockX ?id=rockx
    Staked ?id=staked
    Stakefish ?id=stakefish
    Stakewise ?id=stakewise
    Staking Facilities ?id=staking-facilities
    BloxStaking ?id=bloxstaking
  4. Wait for a block to be produced. Inform Kailin (Telegram/Discord: @imkailin) or the Flashbots Discord that you are ready for verification. 🚀

Current ‘MEV-Boost Ready’ Node Operators 🥳

We will be tracking the readiness of each node operator, and publishing results to boost.flashbots.net by August 1st, 2022.

Goerli Mainnet Links
Timeline: LIVE! Sep 15, 2022
Blockdaemon ✅ ⏳ announcement
Figment ✅ ⏳ announcement
Foundry ✅ ⏳
Kiln ⏳ ⏳ announcement
Lido ✅ ⏳ dao vote
Rocketpool ✅ ⏳
Staked ✅ ⏳
Bitcoin Suisse ⏳ ⏳ announcement
BloxStaking ✅ ⏳
Chorus One ⏳ ⏳
Coinbase Cloud ⏳ ⏳ announcement
Consensys Codefi ⏳ ⏳
ETHPool ⏳ ⏳
SharedStake ⏳ ⏳ announcement
Staking Facilities ⏳ ⏳
Stakefish ⏳ ⏳ announcement

Additional Information

Testnet Details
Goerli Goerli is a permissionless testnet that will not be depreciated after The Merge. The Flashbots Goerli Shadow Fork 5 Relay is live for local testing. The official Goerli Flashbots Relay URL and associated Merge Readiness checkmarks will be assigned after Goerli’s transition to proof-of-stake.
Sepolia Sepolia is a permissioned testnet that transitioned to PoS July 6, 2022, and will not be depreciated after The Merge. We encourage those with existing access to Sepolia to setup MEV-Boost on the Sepolia network.
Kiln Kiln is a permissionless testnet that underwent the The Merge in March 2022. Kiln will be deprecated in the second half of 2022 shortly after the merge.
Ropsten Ropsten is a permissionless testnet that underwent the The Merge on June 8, 2022.
Mainnet
(mid-Sept) The most important milestone. In order to minimize network disruption caused by MEV, MEV-Boost should be tested and running in mainnet validators in preparation for the merge. Protocol developers have recommended that validators start producing MEV-Boost blocks after 16 epochs.