Open mempirate opened 1 week ago
Yep sounds good, can you clarify what would your use case for eval_bid
is it just whether to accept or reject a given block?
Yes exactly, it will be applied to each incoming block from each relay before selecting the best bid
Context
In the
get_header_with_proofs
endpoint of the constraints-API, we reuse practically all the same functionality of theget_header
call defined in commit-boost PBS. The only differences are:GetHeaderWithProofsResponse
)It would be great if we could reuse the same
get_header
implementation with all of the existing configuration, without having to copy over all of that functionality. For that, we'd need to makemev_boost::get_header
generic over the response type and provide an optional genericeval_bid
closure. Something like the following function signature should make it clear:Would this be something we could implement? Happy to open a PR if so.