Precompile cache

[bertmiller]

rbuilder has a cache for precompiles which is interesting because

• it allows for the sharing of execution results across top of block simulation and block building
• it reducing latency
• it helps with DOS

it'd be nice to support the same thing in rblib. rbuilder integrates it here, but I didn't see an obvious comparable integration point since rblib instruments the EVM a bit differently.

[julio4]

rbuilder seems to implement this with a custom EvmFactory implementation, which wraps create_evmt o add precompiles cache. In rblib, we can add ConfigureEvm trait bounds at platform level:

rblib/src/platform/mod.rs

Lines 65 to 71 in 740efa8

	/// A type that provides a complete EVM configuration ready to be used
	/// during the payload execution simulation process. This type is used to
	/// create individual EVM instances that are used to execute transactions.
	type EvmConfig: reth::api::ConfigureEvm<
	Primitives = types::Primitives<Self>,
	NextBlockEnvCtx: Send + Sync + 'static,
	>;

We can follow the same implementation as rbuilder with a EthCachedEvmFactory and use it in the Ethereum Platform implementation:

rblib/src/platform/ethereum/mod.rs

Line 71 in 740efa8

type EvmConfig = EthEvmConfig;

Then, should we also do same for all platforms? Is the precompile cache the same? If so, we could try to abstract underlying factory of the CachedEvmFactory with ConfigureEvm bound and use it in Platform

[bertmiller]

Hmmm... I can't imagine a chain that wouldn't want a precompile cache unless it didn't have precompiles. I can imagine that precompiles might vary (e.g. OP-Stack vs L1). In my mind, ideally we have one precompile cache that just works everywhere.

[SkandaBhat]

Can I help with this? I understand this might need some design beforehand, I could put it across here for discussion if that's ok. @julio4