Last year, when managing NFT assets, storage costs directly crushed the entire project economic model. I wanted to put thumbnails on the chain, but once I did the math, I was stunned—costs were simply not feasible. In the end, I had to compromise and use a centralized solution. Many people have probably experienced that feeling of knowing there's a risk but being forced to accept it.

Recently, I came across an interesting idea. Instead of storing all data on-chain, why not divide the responsibilities this way: handle core logic and rights confirmation on the Sui chain, and delegate data storage to a specialized protocol. This approach can ensure data immutability while significantly reducing costs.

The core technology used is erasure coding—splitting a file into 100 parts, and only 30 are needed to fully recover it. Compared to traditional multi-backup methods, this is a real dimension-reduction attack. Node operators need to stake tokens to participate; there are both rewards and penalties. This incentive design can effectively enforce honesty.

What impacted me the most is the application scenario: NFT images will never turn into 404 errors, allowing creators and collectors to trust long-term. This is a genuine demand for the entire digital asset ecosystem.

Of course, it's not perfect. Balancing node rewards, storage costs, and system scale still needs to be refined through practice. But one thing is clear—Web3 lacks this kind of reliable and affordable storage infrastructure, and now someone is seriously working on it.

Have you ever given up on ideas because of storage issues? Do you think this kind of solution has potential?