Chris Hager

Tried to distill the conversations and open questions into a single draft document: https://hackmd.io/@metachris/mev-boost-inclusion-list-implementation-draft/edit

How to handle stałe transactions is a key open question. Providing the list just when builders start building seems too late because: 1. List needs to go from proposer to...

Interesting idea! This would be an mev-boost internal implementation detail, since mev-boost will always provide only a single `SignedBuilderBid` to the proposer.

Absolutely. Thinking about this from the perspective of mev-boost: * a `registerValidator` call is received (containing a single or an array of individual registrations) * mev-boost sends this call to...

@realbigsean mentioned they implemented resending once per epoch into the Lighthouse validator client. I'm not sure if it's best to move this functionality to mev-boost or have it in the...

Yep, that's correct, and we are also just mapping out the infra to handle this. I don't think there's a good way around this, since we want relays coming online...

Relays need to be designed in a way that can handle the load. Some variance might be nice but couldn't be relied upon anyway.

> Is block level scoring pre-submission or post-submission (by the validator after signing the blinded block)? The relay does the block scoring when it receives a block submission by a...

I think that might make sense, mev-boost won't allow unknown fields in the decoding, so it's not really backwards compatible. Fwiw, I think there's a push towards block scoring by...

Anything that's verifiable by mev-boost is also verifiable by the BN. But mev-boost needs to be able to verify, otherwise it couldn't pick the best valid bid from all the...