@Walrus 🦭/acc
Idle storage never lacked a place in maise Murano in decentralized infrastructure. During most periods, the capacity that has been developed is idle, yet systems still collapse during peak periods. It is not that there is no storage problem. It is a lack of coordination of when and how that capacity is utilized in actuality.
This is where @Walrus 🦭/acc transforms the equation. It does not see storage as something inert that waits to be accessed but availability and bandwidth is an active resource requiring coordination in real-time. Idle capacity is not there to exist but rather to act when it is required by the execution.
@Walrus 🦭/acc incentivizes such that nodes have incentive to serve data when the demand increases and not when the data is merely held. That will reduce idle storage capacity to infrastructure that is able to scale under load, instead of becoming a bottleneck.
This difference is important as more data is forced through the execution-centric chains. There is no breakdown of systems due to lack of storage. They fail to work since capacity is not brought to bear at the time it is most required. Walrus is created on the basis of that fact.
