Well "screwed" is a difficult term. One could argue that as long as the EOS stakeholders are making money, they're not screwed. Let's put it this way; the EOS main chain is already over 5TB and it's still all in RAM. A big part of the reason why it's so big is because it produces blocks every half a second. But none of this is necessarily bad for Block.One because they don't run the chain or run an app on the chain. The people who will get screwed are the suckers who choose to build on it ;)
And growing! Rapidly! Good thing they spammed all those transactions ;). They need to produce blocks that frequently if they want to deliver the kind of performance they are claiming EOS is capable of. Imagine someone wants to string together 20 smart contracts all of which need to be executed sequentially, before funds are transferred. That one transfer is still going to take 10 seconds to occur even with .5 second block times. Had they chosen 3 second block times... well you can do the math. Not saying it's a bad solution to the problem they're choosing to tackle, but it highlights part of the reason we're so committed to application-specificity. For Steem, 3 second blocks work great and few see any reason to increase that rate, especially bearing in mind that doing so would only make the chain grow faster.
Well "screwed" is a difficult term. One could argue that as long as the EOS stakeholders are making money, they're not screwed. Let's put it this way; the EOS main chain is already over 5TB and it's still all in RAM. A big part of the reason why it's so big is because it produces blocks every half a second. But none of this is necessarily bad for Block.One because they don't run the chain or run an app on the chain. The people who will get screwed are the suckers who choose to build on it ;)
5TB !!! That's insane. I thought EOS was going to produce every 3 seconds like Steem.
And growing! Rapidly! Good thing they spammed all those transactions ;). They need to produce blocks that frequently if they want to deliver the kind of performance they are claiming EOS is capable of. Imagine someone wants to string together 20 smart contracts all of which need to be executed sequentially, before funds are transferred. That one transfer is still going to take 10 seconds to occur even with .5 second block times. Had they chosen 3 second block times... well you can do the math. Not saying it's a bad solution to the problem they're choosing to tackle, but it highlights part of the reason we're so committed to application-specificity. For Steem, 3 second blocks work great and few see any reason to increase that rate, especially bearing in mind that doing so would only make the chain grow faster.