Chris Hager

Could you provide a specific example? An issue is that mev-boost and the relay needs to conform to the builder spec: https://ethereum.github.io/builder-specs/ This API spec only allows setting `fee_recipient` and...

hmmm i see, i think this would indeed be easiest handled in mev-boost. and it seems related to #155, file based relay list, where you could set this relation. we'll...

For reference, the Teku/Lighthouse config file format looks like this: ```json { "proposer_config": { "0xa057816155ad77931185101128655c0191bd0214c201ca48ed887f6c4c6adf334070efcd75140eada5ac83a92506dd7a": { "fee_recipient": "0x50155530FCE8a85ec7055A5F8b2bE214B3DaeFd3", "validator_registration": { "enabled": true, "gas_limit": "12345654321" } } }, "default_config": { "fee_recipient":...

The most simple config for mev-boost could look like this (and allow per-proposer overrides): ```json { "default_config": { "relays": [ "https://0xb5246e299aeb782fbc7c91b41b3284245b1ed5206134b0028b81dfb974e5900616c67847c2354479934fc4bb75519ee1@builder-relay-kiln.flashbots.net" ] } } ```

* `relays` needs to be an array * i prefer to allow setting `relays` directly, not requiring groups * i'd prefer the prop be named only `relays` instead of `builder_relays`,...

Looks good too. In this case we could consider changing `builder_relays` to `relays` because it's already in the builder context 🤔

For reference: see also the Prysm PR https://github.com/prysmaticlabs/prysm/pull/10992

It should not replace the -relays flag, but i think if someone specifies the config and -relays, it should fail with a log message

@michaelsproul mev-boost only uses the relays config from this file, gasLimit and feeRecipient need to be sent as a validator registration that's signed with the validator key, so mev-boost wouldn't...

Thanks everyone for all the input so far (and @0xpanoramix for his work on implementing this in #186). Let's continue the spec-specific conversations in https://github.com/ethereum/builder-specs/pull/41/files 🙏