feat(flashtypes): Introduce Minimal Flashtypes Crate #284
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Introduces
base-flashtypes, a new crate containing the core primitive types forflashblocks. This extractsFlashblock,Metadata,FlashblockDecodeError, and the execution payload types fromrollup-boost-types(which is an unpublished crate we previously depended on) into their own minimal crate.The main motivation is to remove the
rollup-boostdependency from the workspace, andbase-reth-flashblocksspecifically. By defining these types locally, we avoid pulling in the fullrollup-boostcrate and its transitive dependencies just for a handful of type definitions. This reduces the dependency tree and gives us more control over flashblocks type wire format.Eventually, once
rollup-boost-typesis a published crate, we can deprecate the payload types inbase-flashtypes, re-using the types fromrollup-boost-types. We could also upstream types frombase-flashtypesintorollup-boost-typesand deprecate this crate entirely.Usage