Tracking: StateCommitment abstraction

[frisitano]

Describe the feature

Overview

This issue will be used to plan the implementation of the StateCommitment implementation. The StateCommitment will be used to provide an abstraction over the types associated with the state commitment. This will allow reth to be used with different state representations configured by the user. Initial POC implemented here.

Plan

We will implement the StateCommitment via the following units of work:

• Introduce StateCommitment trait, integrate with NodeTypes and provide MPT implementation. - feat: introduce StateCommitment type #11842
• Introduce StateCommitment types within providers. - Introduce StateCommitment in StateProviders #12602
• Introduce HashedPostStateProvider and refactor methods on HashedPostState and PrefixSetLoader to be generic over the KeyHasher - Introduce HashedPostStateProvider #12607
• Introduce HashedStorageProvider - Introduce HashedStorageProvider #12894
• Introduce KeyHasherProvider - Introduce KeyHasherProvider #12895

Refactor codebase to leverage StateCommitment types for all operations:

• StateRoot - Introduce StateRootProviderExt and Integrate with StateCommitment #12896
• StorageRoot
• StateProof
• StateWitness
• KeyHasher
• ParallelStateRoot

Additional context

#11786

Tasks

Beta Give feedback

1. feat: introduce StateCommitment type #11842
   +0
2. Introduce StateCommitment in StateProviders #12602
   +0
3. Introduce HashedPostStateProvider #12607
   +0
4. Introduce HashedStorageProvider #12894
   +0
5. Introduce KeyHasherProvider #12895
   +0
6. Introduce StateRootProviderExt and Integrate with StateCommitment #12896
   +0

[Thegaram]

This could be added to #11241. @mattsse

[Rjected]

Just added to the tracking issue @Thegaram

[github-actions]

This issue is stale because it has been open for 21 days with no activity.