Why most Web3 products still look like smoke and mirrors, and what we (as developers) can do to solve it.
1. The Problem: Multi-million Dollar Solutions for Non-existent Problems
The biggest failure of Web3 today is that we have solutions looking for problems, or multi-million dollar infrastructures that do not resolve real needs.
A clear example is the saturation of L1 Blockchains without users. You only need to look at the data to notice the disconnect: blockchains valued at billions with minuscule on-chain activity and fee generation.
2. The Solution: Apps > Infrastructure
As developers, we must shift our focus. The market doesn't need another L1 or another L2; it needs applications.
99.9% of use cases can be perfectly resolved on the current EVM or SVM. The infrastructure already exists. Our job now is to build products that people want and can use, whether for Web3 veterans or the common user.
3. The Token Paradox: Towards "Desensitization"
Here is where I have an unpopular opinion: we need more tokens, not fewer.
We need to reach a saturation point, similar to the dot-com bubble. In the 90s, having a website absurdly inflated a company's valuation, until the bubble burst and we understood that a website is a tool, not a guarantee of value.
The same must happen with tokens. We should generate millions a day, just as we generate HTML, videos, or posts. By flooding the market, we desensitize people: a project having a token shouldn't mean it has intrinsic financial value. Only then will we cleanse the industry of empty speculation.
Last year was the turning point. If you were active in crypto, you'll remember the memecoin fever, where even the President of the US launched his own. That saturation without intrinsic value was necessary: it taught the market that having a token guarantees no value and that the barrier to entry for creating magical money is null.
Top comments (0)