Having developed blockchain games for two years, I’ve truly experienced all the pitfalls in asset storage.

Looking back at the first open-world blockchain game, at that time, large files like character models and scene maps were all stored on IPFS, and I only later realized how foolish that was. Storage costs were prohibitively high; a 10GB resource pack required at least an 8-fold replication to ensure usability. Users downloading? They often had to wait dozens of seconds, sometimes even longer. The most frustrating part was that if the centralized gateway went down, players couldn’t access the game at all. And the crazier part came later—some players discovered that the metadata of NFT items had been altered, which immediately triggered a wave of players quitting. That period was truly stressful.

It wasn’t until early 2025 that I encountered a new storage solution, and I finally saw a glimmer of hope. The design concept of using WAL tokens as ecosystem utility tokens completely changed the game. From technical implementation, cost control, and ecosystem collaboration, I spent over half a year experimenting before I gradually understood what made it different. Honestly, the value of this system far exceeds “storage” itself. The underlying RedStuff 2D erasure coding technology, community-driven token mechanisms, and close integration with the Sui blockchain are reshaping the logic of asset storage and circulation in blockchain games.

What impressed me the most was the RedStuff encoding system. This isn’t just hype; it’s a real technology capable of solving the pain points of blockchain game storage. Currently, the second blockchain game I’m developing has over 200 character NFTs, 15 high-definition scene maps, and a bunch of dynamic interactive resources, totaling 85GB of data. If I had used previous solutions… just thinking about it gives me a headache.