That’s been my impression as well, and my main hope for scalability. For all the good points of Steem scarcity listed in this article, the big problem is at current conditions we’re capped at a relatively small number of normally functional user accounts.
In a recent State of Steem forum on Discord, I was intrigued most by some of the discussion from @blocktrades. Apparently their team was the original subcontracted developers of initial RocksDB implementations (the user account history module I think it was?) He also confirmed that upcoming node efficiency and cost reductions could bring down resource costs, because they would make more resources available for everyone.
He even went on to describe a future where it could feasibly be possible to have simple node install packages for consumer hardware that even a layman could use. I envision it like most proof of stake wallets that stay open & running to secure the network while staking rewards. We could see Steem clients that basically act as nodes and help generate the network resources the end user is consuming.
All a bit pie in the sky, and I’m very much the “layman” I mention above... but I feel there are smart folks working on the technicals, and many outside of Steemit Inc. capable of taking up the tasks if need be. That keeps my interest and optimism alive... perhaps foolishly!
Yes, that’s correct. But let’s make sure not to confuse ‘Resource costs’ (RC) and ‘Resource costs’ (operational infrastructure costs).
The latter being how much it costs to host a node on a server. The specific hardware requirements for such. We’ve known for decades that they were ridiculous for such a small community as Steem currently is.
The former being the”new bandwidth” matrix introduced with HF20. And then hotfixed by applying a
10xcalculation.