I've been researching Web3 infrastructure for almost two years, and decentralized storage is arguably the toughest challenge I can't crack. To put it simply, this matter is too critical — it directly affects the core lifeline of the data sovereignty ecosystem and determines whether we can truly break free from reliance on centralized infrastructure.

But after running through the practical process, the complaints I’ve received outweigh the highlights. Projects that emerged during the boom period, after gaining attention, saw their technology stagnate; the promises made in whitepapers were never realized; some teams are keen on using complex technical jargon to impress, sounding profound but failing to even ensure stable secure file access; and there are many that simply treat token speculation as their core business, with ecosystem applications being virtually non-existent. This system, aside from storytelling, can do nothing substantial.

I often ask myself: can decentralized storage really only stay in speeches and plans? Is there truly a project that can strike a balance among security, cost, and user experience, allowing ordinary people to use it directly?

This question has been tossing in my mind for a long time. Until half a year ago, I encountered a new approach. From the basic storage functions in practical operations, to analyzing the underlying technical design logic, and finally to actively participating in ecosystem development — this half-year of exploration has gradually helped me see through some things and gain a clear understanding of the actual value of this direction. The ideas I share today are not authoritative industry judgments, but the genuine feelings of a researcher after hands-on experience.

My initial interest in this area actually stemmed from an unexpected discovery during a user needs survey. At that time, I was sorting out various obstacles in Web3 storage usage and communicating with many users...