Many people only look at Sui's speed, but they don't really understand what Sui aims to do. To be clear, Sui has never been about "faster financial transactions." Its target is high-frequency, complex applications like blockchain games, social media, and content platforms — this is the true future of blockchain.

This raises a question: as applications change, data structures must also adapt. Can we still use the old approach of "lightweight state + external storage"? Obviously not.

Sui's object model and parallel execution mechanism are indeed powerful. Multiple objects can be operated on simultaneously, without queuing like traditional account models. In theory, this opens the door for high-concurrency applications. But there's a hidden risk: the object model only addresses "how to update state," and cannot accommodate the massive data content that applications truly need. Imagine the advantage of high concurrency being hampered by the instability of off-chain data access — that would be pointless.

This is the real significance of Blob — it’s not optional, but a necessary condition for the ecosystem to truly take root. On-chain object references point to Blob identifiers, while the actual data is stored and distributed by the network. This way, on-chain execution remains lightweight, the data layer is independently responsible, and each part does its job. Only this combination can support the genuine expansion of the Sui ecosystem.