We have to understand Hive is, at a technical level, a network of nodes processing transactions. If transactions are chocking nodes at any given time, they have these options:
upgrade their infrastructure (costs more money and few will do it unless there is a clear direct benefit to the node operators that will help them cover the extra costs)
limit the type of transactions or the source of transactions accessing the nodes (results in delays and failures)
take the node down or make it private if the costs become unsustainable
Also, Hive's base code reacts by increasing the resource credits cost of that type of transaction, regardless of the source. If we are talking custom JSONs, a very popular Splinterlands compared to today should increase the resource credits costs for custom JSONs for everyone using them. Likewise, a very popular Threads would likely somewhat increase the resource credits cost for posting & commenting in general. I've seen this looked at with good eyes, as it would force applications to buy and power up HIVE or rent resource credits for their users.
We have to understand Hive is, at a technical level, a network of nodes processing transactions. If transactions are chocking nodes at any given time, they have these options:
Also, Hive's base code reacts by increasing the resource credits cost of that type of transaction, regardless of the source. If we are talking custom JSONs, a very popular Splinterlands compared to today should increase the resource credits costs for custom JSONs for everyone using them. Likewise, a very popular Threads would likely somewhat increase the resource credits cost for posting & commenting in general. I've seen this looked at with good eyes, as it would force applications to buy and power up HIVE or rent resource credits for their users.