Closed jsvisa closed 1 year ago
There is an EIP for it https://eips.ethereum.org/EIPS/eip-4444, the challenge of it is how can we have a strong guarantee that the dropped historical chain data can still be retrievable. I believe this challenge is not resolved yet.
While as a short-term solution, you can specify the ancient directory to a HDD-based location, it's still performant enough (our freezer design has O(1) read/write complexity) but kind of cheaper to use HDD.
Rationale
I'm running a new snap-sync node, after the syncing progress, found the local chaindata consuming 800+GB, and half of the disk is used to store the ancient data:
The old ancient data is useless in most cases, so if we support the ancient data pruning, we can use fewer disks.
Implementation
Seems the binance smartchain has supported this feature(merged in #543) maybe we can backport this feature into go-ethereum.