-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
primitives: use alloy Sealed<Header>
instead of SealedHeader
#11123
Comments
hey I'm down to work on this |
did you get around to starting on this @greged93 ? |
@emhane I started and got caught in something else, let me jump back on it. |
@emhane this solves it for compact but we still have the same issue for |
thanks for the investigation @greged93 . blocked by alloy-rs/core#754, alloy-rs/core#755 and alloy-rs/core#762. |
there's no reason this type should even have rlp support. the current arbitrary derive is also problematic as highlighted here alloy-rs/core#762 |
I'll check where it is needed but currently Encodable and Decodable are implemented on |
none of this should be there because using rlp on a sealed type is never used in any protocol |
Ok! Will wait on arbitrary and remove rlp then! |
@mattsse what should we do for |
main reason we want this is to use the alloy rlp traits will have to be implemented on a wrapper type in reth @greged93 |
noted! just waiting on arbitrary which should be in alloy-primitives |
This issue is stale because it has been open for 21 days with no activity. |
Describe the feature
The current codebase uses the
SealedHeader
struct:reth/crates/primitives-traits/src/header/sealed.rs
Lines 13 to 24 in 7529d36
This is redundant with Alloy's
Sealed<Header>
type:https://github.com/alloy-rs/core/blob/4b823f7977fcdc181a0bd04ba1b2c51f7a29b4e2/crates/primitives/src/sealed.rs#L3-L14
After the merge of #10691, we have multiple unnecessary conversions between
Sealed<Header>
andSealedHeader
when sealing headers, as we now rely on the Alloy consensusHeader
type.Task
SealedHeader
from the codebase.Sealed<Header>
from Alloy consistently.Related #10691 (comment)
Additional context
No response
The text was updated successfully, but these errors were encountered: