feat: provider StateCommitment integration #11867
Open
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.
Dependencies
This PR builds on #11842 and as such it should be reviewed after #11842 has been merged.
Overview
This PR introduces the
StateCommitment
type inStateProviders
such that the type can be used for state commitment operations. In this PR we do not utilise the types for state commitment operations, that will be implemented in follow up PR's.ToLatestStateProviderRef
traitWe introduce
ToLatestStateProviderRef
trait and implement it onDatabaseProvider
such that we can instantiate aLatestStateProviderRef
from aDatabaseProvider
without leakingStateCommitment
type data. We update components that instantiateLatestStateProviderRef
objects from aDatabaseProvider
to leverage this trait.supports: #11830