Recently, I took a deep dive into the Walrus project and found that it is not about hype or promoting performance numbers, but truly addressing a long-overlooked issue—data availability and storage.

The key is that it breaks down complex underlying capabilities into modular interfaces, making it easy for developers to get started. This sounds simple, but actually doing it requires a lot of skill. Many protocols are short-lived, ultimately because their infrastructure is not robust enough, and they are abandoned after two uses.

So when I look at $WAL , my thinking is a bit different—it’s not betting on short-term hype, but laying the foundation for the next wave of applications. Which projects can last long often depends on whether this underlying reliability can be truly integrated into the ecosystem, rather than just marketing prowess.