Ethereum Clients Roll Out Partial History Expiry
Ethereum clients roll out partial history expiry by mishaderidder.eth13093 🥝 • 1y • 0 views • 0 clicks | |
AI summary of the linked articleThe Ethereum Foundation announced on July 8 that major clients Geth, Besu and Nethermind are introducing an opt-in "Partial History Expiry" mode that lets node operators discard older block data, for example keeping only the most recent year. The article says this is not consensus-breaking, since all nodes still verify blocks, and that it lowers disk usage and sync times. It also notes that The Graph, analytics dashboards and some L2 rollups that rely on historical block traces will need archive nodes or third-party providers such as Infura, Alchemy or ArchiveNode. | |
Recommended by 1 curator | |
 Excited about this, I think it’s a good step forward. So another post about this, an explainer (but it’s not really difficult ;). Hope there will be a future where an Ethereum node is a standard fitting in the meter box of every house. (Or a node on every phone. Stuff like that.) What can I say, go run a node!  While this is good for daily business, I feel uneasy about delegating the history completely to third parties. (Apart from the P2P -> C/S model change.) I couldn't find any plans for open access/public domain archives. Keeping this info will only become more expensive, so individuals will probably give up after a while. Are there plans?  Not that I usually advertise where I work much, but in this case it might be warranted, especially if people are building and want the full state. At SQD we also have the complete history distributed across our set of now 2800 worker nodes. Of course, we're a third party in this sense, but at least we try our best to decentralize, and ensure much lower rates compared to places like the graph (the only constraint is bandwidth) for best access :) | |
Characters remaining: 10,000 comment guidelines | |
More from etherworld.co on Kiwi News | |