EOS has grown to 4 tb in 8 months. Only 5 BPs are storing historic state, and none of them being compensated for this on standby, leading to downtimes for apps across the network. vvvvv Informative video below vvvvvhttps://twitter.com/EOSWeekly/status/1096549302804074501 …
-
-
The problem is that's grown to 4 TB in only 8 months. That's an unsustainable long-term growth model for such a young project. Bitcoin, that has been around for over 10 years, can still comfortably run on a 500 GB hard drive for a many more years, still.
-
So nodes have to buy a new $300 8TB hard drive every 16 months? Why is this a problem? Usenet was growing 1TB/day more than a decade ago...
- 10 more replies
New conversation -
-
-
The problem isn’t just diskspace, it’s bandwidth required to flood-fill the network with these transactions. Bandwidth demands centralise nodes, first by excluding countries where the requisite bandwidth is expensive, and then by forcing nodes out of homes & into datacenters.
-
fortunately EOS sidesteps this problem by not having anyone run nodes at home

- 1 more reply
New conversation -
-
-
The actual state file for a full node is much less. More like 2 TB. The 4TB refers to history API nodes, not critical to the network functioning. It’s useful if you want to do off chain stuff. That’s why we built our own indexing / search engine (http://dfuse.io )
-
hmm. I've heard several numbers for this, also terminology btwn BTC, ETH and other chains is often different which makes understanding more challenging. is there somewhere I can see all the EOS node sizes and types in one place?
End of conversation
New conversation -
-
-
Happy to see you in this discussion! Worth repeating this clarification: EOS ledger size itself is only 200gb (needed to validate chain and execute transactions). 4tb is when you index the data on different search terms (needed for apps). App devs could implement their own index.
-
yes - my phrase "historic state" got lost in the frenzy. this is equivalent to an archive node on ETH. similar fragility in centralised servers providing apps historic data though. major unresolved prob is the rate of growth. if 4 tb in 8 months is a challenge, wait 2 years

- 1 more reply
New conversation -
-
-
Hi Tim - it's been a while, and there have been some big strides in EOSIO software. Leading the way is the WAX blockchain, and I'm sure you're familiar with the team at Opskins, which built WAX. Wondering if you are considering dipping your toes into the NFT space via
$WAX? -
I don’t know any of those acronyms...
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.