The Rise of Web3: A New Era of Infrastructure
The Web3 ecosystem has long been hailed as the future infrastructure of the internet. With its promise of decentralization, blockchain technology, and cryptocurrency, it seems poised to reshape industries and introduce new digital experiences. However, nearly a decade after Ethereum’s whitepaper was first released, the reality looks quite different. Despite rapid innovation in Web3’s infrastructure layer, we find very few mainstream applications running on it.
As we continue to see a surge of new infrastructure building blocks—L1, L2, L3 blockchains, rollups, ZK layers, and decentralized finance (DeFi) protocols—it’s clear that Web3 is experiencing an infrastructure boom. Yet, there’s one major issue: there’s an overwhelming focus on building infrastructure, but the applications that would drive adoption and value remain scarce. This imbalance between infrastructure and application development is unique in the history of technology markets, and it poses significant risks for Web3’s future.
Why Is Web3 Overbuilding Its Infrastructure?
The Profit Motive Behind Web3 Infrastructure
So, why is this happening? Simply put, it’s profitable to build infrastructure in Web3. Unlike traditional tech industries, where infrastructure development often requires years of slow progress and capital investment, Web3 infrastructure projects can raise significant funds through token launches. These tokens are often tradable on exchanges, generating liquidity for investors, developers, and teams. This makes the Web3 space incredibly attractive to those looking to capitalize on emerging technology trends quickly.
While rapid capital formation can benefit infrastructure builders, it also creates an environment where short-term profits are prioritized over long-term value creation. This dynamic leads to an overemphasis on infrastructure development at the expense of application creation, ultimately threatening the growth and sustainability of Web3.
The Typical Infrastructure-Application Cycle in Tech Markets
To understand why this imbalance is so problematic, we must look at how value has historically been created in technology markets. In traditional tech ecosystems, there is a constant balancing act between infrastructure and application layers. In the Web1 era, infrastructure providers like Cisco and IBM powered the early internet, while applications such as Netscape and AOL captured significant value. In the Web2 era, cloud infrastructure fueled the rise of SaaS and social platforms.
More recently, trends like generative AI began with infrastructure plays like AI model builders. However, it was applications like ChatGPT and Perplexity that propelled AI into mainstream adoption, which in turn led to further development of supporting infrastructure.
In this cycle, applications typically follow infrastructure development, guiding new use cases and driving demand. But in Web3, there’s a noticeable absence of such application-driven feedback. Instead, the infrastructure keeps piling up, with very few applications to demonstrate their value.
The Risks of Overbuilding Web3 Infrastructure
1. Lack of Market Feedback
One of the most significant risks of overbuilding Web3 infrastructure is the absence of real-world adoption feedback. In traditional tech markets, infrastructure evolves based on the needs and feedback of the applications that use it. But in Web3, most of the usage comes from other infrastructure projects rather than end-user applications. Without market feedback from real-world applications, Web3 risks building infrastructure for hypothetical use cases that may not resonate with actual consumers.
2. Liquidity Fragmentation
Another challenge posed by the overbuilding of infrastructure in Web3 is liquidity fragmentation. With new blockchains emerging at a rapid pace, the capital in Web3 is becoming increasingly spread out. New blockchains require billions of dollars to bootstrap liquidity, but as the creation of L1 and L2 blockchains outpaces new capital inflows, the liquidity pool becomes more fragmented. This presents significant adoption challenges, as users and developers are faced with a divided ecosystem.
3. Increased Complexity
Web3 infrastructure naturally grows more complex over time. While applications typically abstract away this complexity for end users, in Web3, where there’s a lack of mature applications, users are left to navigate intricate wallets, decentralized apps (dApps), and bridges. This creates significant friction, making it harder for mainstream users to adopt Web3 technologies. Without user-friendly applications to simplify the experience, complexity will continue to be a barrier to entry.
4. Limited Developer Communities
For Web3 infrastructure to thrive, it needs a robust community of developers. However, most new infrastructure projects struggle to attract enough developers, as the existing talent pool is small and already stretched thin across multiple projects. With developer communities lagging behind infrastructure creation, many Web3 platforms are left with limited resources to actually build the applications that would drive adoption.
5. Widening Adoption Gap with Web2
Perhaps the most concerning consequence of overbuilding infrastructure in Web3 is the widening adoption gap between Web3 and Web2. In contrast to the Web3 ecosystem, which continues to prioritize infrastructure, the Web2 world is rapidly evolving with new technologies like generative AI. SaaS and mobile applications powered by AI are changing industries and defining the next generation of digital applications. Web3, on the other hand, remains focused on developing more blockchains, missing out on the momentum created by Web2.
Breaking the Cycle: Moving Towards a Balanced Web3 Ecosystem
To avoid the pitfalls of overbuilding infrastructure, Web3 must shift its focus toward application development. While infrastructure remains a vital component of the Web3 ecosystem, it cannot succeed without applications to drive demand and adoption. Web3 projects need to align infrastructure development with real-world use cases, ensuring that their building blocks are not only technically sound but also aligned with market needs.
Currently, the Web3 space is building infrastructure in a vacuum, with most of the usage coming from other infrastructure projects rather than actual end-users. This creates a dangerous feedback loop that risks stalling Web3’s evolution. By focusing on applications that use this infrastructure, we can create a more balanced and sustainable ecosystem that is better equipped to achieve long-term success.
