Invert provider access in SparseTrie

[Rjected]

Right now the SparseTrie takes ownership over a provider, this is used only in reveal / update methods:

reth/crates/trie/sparse/src/trie.rs

Lines 177 to 178 in 2101ae8

	/// Blinded node provider.
	provider: P,

This is what causes our issues when we try to operate over many storage tries in parallel, the provider under the hood is a tx which gets shared.

This is used in two places:

reth/crates/trie/sparse/src/trie.rs

Line 1122 in 2101ae8

self.provider.blinded_node(&current)?

reth/crates/trie/sparse/src/trie.rs

Line 1285 in 2101ae8

self.provider.blinded_node(&child_path)?

Owning the provider is partially for type safety, so that we can give a BlindedProviderFactory to the SparseStateTrie, and have it make sure storage tries are operating over storage tables, but this means we do not have control over where / when database txs are created. If we really needed this type safety, we could probably solve it with some phantomdatas?

We could instead invert provider access, requiring these methods to take in a provider as an argument.

[frankudoags]

I'd love to work on this @Rjected

[PoulavBhowmick03]

I have been working on this, implemented the provider as argument. a few stuffs to get cleared on the inverting part. Can I be assigned to this?

[stfnberat]

@Rjected can I do this?