Do you have an in-depth post on RCs on your blog? If not I think it would be an interesting to cover in depth.
There are some things that aren't so clear to me like the relationship between the hive blocksize and changing the RC costs of operations. For instance, can we make posting cost less RCs without changing blocksize? If so, wouldn't the blockchain just get bloated even though the RC system still shows that people can use the blockchain?
https://peakd.com/hive-167922/@taskmaster4450/hive-a-resource-credit-crunch-in-2021-2022
https://peakd.com/hive-167922/@edicted/hive-scaling-rc-burnout-open-letter-to-taskmaster4450
https://peakd.com/gaming/@edicted/creating-digital-assets-with-steem-s-resource-credits
The entire point of RCs is for the cost of operations to spike when the blocks start filling up. When RCs were launched, perhaps you remember how everyone had negative RCs and no one could do anything, we had to make RCs cheaper by x10 just so people could use the blockchain.
When blocks start filling up we are going to return to those x10 cost levels... perhaps even higher. This is going to prevent lots of users with low RCs from doing anything on Hive because it's so bloated. We need RC pools to avoid this: but that will push the cost of operations even higher.
Increasing the block size of Hive allows us to reduce RC costs, but again there is a huge cost to doing so: every node in the network becomes more expensive to run. That means many low level witnesses and new projects will drop out and go elsewhere. It's a balancing act of bandwidth and priorities.
Thanks, I needed to refresh my memory with all that info.
Long term, vertical scaling is needed. If I understand correctly what's been happening recently, modular hivemind is the first step into allowing devs to easily run their own sidechain where everything is cheaper and less secure.