-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(mev-build): support multiple forks when submitting bid #135
Conversation
17485ba
to
7f8f969
Compare
ExecutionPayload::Deneb(deneb_payload_bundles) | ||
} | ||
|
||
fn get_blob_bundles<Pool>(pool: &Pool, tx_hashes: Vec<H256>) -> BlobsBundle |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this logic would be encapsulated in the PayloadBuilder
abstraction so we wouldn't need to pass this Pool
generic around through all of this code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for this!
we do want to do something here but let's consider the design a bit first
do you know how reth handles polymorphism of the SealedBlock
type? is it just Option<T>
for the relevant T
s for each fork?
f9f8bec
to
a6165e8
Compare
I may not be aware of this but I think there's just one form for |
this has partially been handled in #151 the builder API type for Deneb needs to change to support the blinded blob sidecars which I intend to do in another PR coming up soon |
Execution Payload
forBellatrix
&Deneb
forks