Peeps by @Jason_Zhou
Showing page 1 of 1 (7 peeps total)
Replying to @Jason_Zhou (0xe85e710c34091d5eaa48efb518e9c0b3ef74c947)
Layer-1 scaling method makes full node's abandon very heavy. Even now the full node of Ethereum costs 2 TB of space. With 1000~2000 TPS, the blockchain will grow much faster than before, so the counts of full node will drop dramatically, making the blockchain network vulnerable.
Apparently, all transaction are stored forever and by everyone is very ridiculous, and totally not necessary.
Replying to @jm9k (0xa7bd09daab3eb5ec96f04914d94c47681489d604)
"...not even the Ethereum Foundation keeps a full archival copy of the Ethereum chain." That's pretty scary.
Yeah, and here https://www.nodestats.org/ has a more demonstration of the data size of the 3 kinds of node: Full node, Fast node, and Archive node. The last one needs 2,374.11 GB.
Replying to @jm9k (0xa7bd09daab3eb5ec96f04914d94c47681489d604)
I see the Ethereum blockchain as under 150GB right now. https://twitter.com/ethnodesize Sharding should help a lot with L1 scaling, but L2 solutions are definitely needed. Micro and nano transactions require a system with overhead near zero; impossible with 100% on-chain.
150GB is "FULL" sync without Trie State synced.
https://blog.blockcypher.com/ethereum-woes-d9b2af62da67
Replying to @CallMeGwei (0x285bc660aa42b8effc6c60357cd4d8ca072be625)
That doesn't sound like bad news to me... Welcome to Peepeth!
Yeah, it's not bad news, but layer2 scaling methods like payment channel are more scalable, so need more concerns.
Layer-1 scaling method makes full node's abandon very heavy. Even now the full node of Ethereum costs 2 TB of space. With 1000~2000 TPS, the blockchain will grow much faster than before, so the counts of full node will drop dramatically, making the blockchain network vulnerable.
The ability of the 4 methods of scaling in layer1 are all very limited:
- sharding(Ethereum 2.0, zilliqa)
- DPoS(EOS)
- DAG(Conflux)
- VRF(Algorand)
They are all about 1000~3000 TPS, only enough to play games that are already existed on EOS. But not enough to more general uses.
Sharding's scalability is still very limited, about several thousand transactions per second, the same level of EOS with DPoS.