Repository navigation
[EPIC]: Node Pruning #2093
Description
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
Activity
linear commentedon Mar 19, 2025
ROL-112 [Feature Request]: node pruning
MSevey commentedon Mar 20, 2025
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.
tac0turtle commentedon Mar 20, 2025
can you touch on what this means?
also this? we dont want to support many DBs, one is enough
docs: Create Node Pruning ADR (#2107)
[-][Feature Request]: node pruning[/-][+][EPIC]: Node Pruning[/+]Eoous commentedon Apr 17, 2025
Can i pick up this one? @Manav-Aggarwal
Manav-Aggarwal commentedon Apr 17, 2025
Hey @Eoous of course, assigned to you
1 remaining item
Eoous commentedon Apr 25, 2025
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.
tac0turtle commentedon Apr 25, 2025
lets leave out volume based storage as it wont be needed for a while. Ill review your pr later today
tac0turtle commentedon Oct 1, 2025
we need to revert this pr once we work on pruning #2718
Eoous commentedon Oct 9, 2025
Still need #2208?
tac0turtle commentedon Nov 18, 2025
ref #2111