refactor(engine): enable sharing of PayloadProcessor and state caches#23354
Open
sieniven wants to merge 2 commits intoparadigmxyz:mainfrom
Open
refactor(engine): enable sharing of PayloadProcessor and state caches#23354sieniven wants to merge 2 commits intoparadigmxyz:mainfrom
sieniven wants to merge 2 commits intoparadigmxyz:mainfrom
Conversation
🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This PR enables the sharing of the payload processor, so that other external customized components are able to leverage on the payload processor's optimized caches and payload processing logic.
For example, this allows external components building on top of reth, such as flashblocks on optimism chains or other customized payloads, to have their customized validators to share the same payload processor logic and its state caches. The customized validator can encapsulate its own customizable logic for that unique payload, while directly leveraging on the payload processor for optimized payload execution and merklization.
Note - the state consistency is guaranteed on the customizer's end, and the payload processor cache states require an engine validator controller for atomic payload validation operations between the default engine validation and the customized layer.