feat: transition from &mut State<DB> -> StateDB
#20113
Draft
+139
−119
Conversation
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
1 participant
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.
This PR moves reth traits from using the concrete
State<DB>to relying on a newStateDBtrait. This allows trait implementations to be much more flexible, and allows for greater code reuse.In particular, we're implementing Flashblock based block access lists, and we need a DB wrapper around
Statethat can construct the access lists. This will allow us to build something likeBalBuilderDB<&mut State>, and then implStateDBfor this type.This PR is marked as a draft because it depends on these upstream PRs.