Chris Hager

Yes, validators need to configure mev-boost with each relay to connect to specifically (using the relay address and pubkey, as cli arg or [a config file](https://github.com/flashbots/mev-boost/issues/154)).

This topic was discussed in [today's Consensus-layer call](https://github.com/ethereum/pm/issues/555), see also [notes from Ben](https://hackmd.io/@benjaminion/HJNt57iq5#MEV-Boost) and the [recording](https://youtu.be/Fid8hTxkRHM?t=1268) (excuse my bumbling ^^).

The Flashbots relays offer a data API that provides summaries for all delivered payloads: https://flashbots.notion.site/Relay-API-Spec-5fb0819366954962bc02e81cb33840f5#417abe417dde45caaff3dc15aaae65dd The summaries include the value that the relay confirmed by simulating the block. Here's an...

Agree that having all the data needed for checking on-chain would be preferable. For that to work, wouldn't the validator registrations also need to be on-chain, to know the `feeRecipient`...

Fyi, we (Flashbots) are currently proceeding with payment from builder to proposer in a direct transaction at the end of the block.

The payment via transaction is live now. > Reason for asking is, for reporting purposes and calculating the EL block reward, we'd like to identify if a block was built...

You could, but that's likely to change at some point (soon).

Continuation of the discussion: https://collective.flashbots.net/t/block-scoring-for-mev-boost-relays/202

We've decided against having a default relay. Closing now.

The [Flashbots Goerli relay](https://builder-relay-goerli.flashbots.net/) now allows block submissions by external builders 🎉 See also [Relay API documentation - Block Builder API](https://flashbots.notion.site/Relay-API-Spec-5fb0819366954962bc02e81cb33840f5#854339c909a042d0bbca6e8f8069674e) The endpoints are: * `getValidators`: https://builder-relay-goerli.flashbots.net/relay/v1/builder/validators (GET) * `submitBlock`:...