[EPIC]: Node Pruning
We should allow nodes to prune historical blocks stored in storage. alternatively storing them in a way that we can attach volumes for certain block heights could be useful over an extended period of time.
ADR for Node Pruning: https://github.com/rollkit/rollkit/blob/feature/exec_api/specs/lazy-adr/adr-017-node-pruning.md
I think prior to pruning we should enable light nodes and then the second part of this request which is the more flexible storage options.
What are the user flows that would want pruning of a rollup block.
we should enable light nodes
can you touch on what this means?
more flexible storage options.
also this? we dont want to support many DBs, one is enough
Can i pick up this one? @Manav-Aggarwal
Hey @Eoous of course, assigned to you
I read adr. I don't know whether got points for volume-based strategy. Looks like the strategy is best for full or archive node, not for pruned node.
lets leave out volume based storage as it wont be needed for a while. Ill review your pr later today
we need to revert this pr once we work on pruning https://github.com/evstack/ev-node/pull/2718
Still need #2208?
ref https://github.com/evstack/ev-node/issues/2111