As discussed on Discord, we're curious if you anything like erigon's rpcdaemon or cardinal-evm on your longer-term roadmap?
Personally most interested in solutions for scaling out state-related RPCs (mainly eth_call) while keeping both latency and disk footprint low on the scaled out portion.
Implementation wise, anything where we have a small redundant pool of full or archive nodes and a larger pool of “light” nodes connected to them that don’t need nearly as much disk (and ideally no disk or at least standard EBS volumes instead of nvme). Basically a cheaper way to scale out a lot of compute for handling eth_call at scale. Even better if it can scale up/down quickly for auto scaling.
Describe the feature
As discussed on Discord, we're curious if you anything like erigon's rpcdaemon or cardinal-evm on your longer-term roadmap?
Personally most interested in solutions for scaling out state-related RPCs (mainly eth_call) while keeping both latency and disk footprint low on the scaled out portion.
Implementation wise, anything where we have a small redundant pool of full or archive nodes and a larger pool of “light” nodes connected to them that don’t need nearly as much disk (and ideally no disk or at least standard EBS volumes instead of nvme). Basically a cheaper way to scale out a lot of compute for handling eth_call at scale. Even better if it can scale up/down quickly for auto scaling.