Eth2.0 Question. How to reduce storage bloat?

Sharding
1

I’m a student currently working on the problem of storage bloat in blockchain.
I have a question.

  • How to reduce storage bloat in Eth2.0?

Now, Eth1.0’s full node stored about 900GB. It will increase more.
In my research, I found super full node and single shard node.
Super full node store beacon chain data and all shard chain data.Super full node need high internet transmission speed and large SSD. On the other hand, single shard node store single shard data. So single shard node will don’t have to large SSD than super full node. But if node shuffle shard, i think ,single shard node would need to download large amounts of data about 1 shard.
So I think it’s going to be difficult to join the network immediately.

  • Is my understanding correct?

  • Do you see the data bloat of the superfluous nodes as a problem?

  • Can you tell us about any storage issues ethereum developer are currently facing?

I’d appreciate it if you could answer my questions.:slight_smile:

2

A full node isn’t 900GB, that sounds like an archive node which is a very different thing that the vast majority of people do not need.

3

That is correct, it is only 899.9 GB (source).

full node 900
full node 9001353×546 26.7 KB

4

There are lots of possible sync settings, I’m curious what settings are being used for whatever is drawing that chart? Modern fast syncs I believe are way below 900GB in disk space.

I don’t know if Geth has something like this, but I have always liked Nethermind’s chart showing different configuration options:
https://docs.nethermind.io/nethermind/ethereum-client/sync-modes

image
image749×746 54.7 KB

2 Likes
5

From the command line options:

--syncmode value Blockchain sync mode (“fast”, “full”, “snap” or “light”) (default: snap)

You can find the description of the various modes here.

I did try a sync last month and in snap sync 300GB were not enough. I wouldn’t be surprise if the 900GB figure is right.

1 Like