Edited By
Olivia Smith

A significant trend is surfacing within the crypto community as new layer 1 and layer 2 blockchain projects consistently establish their own decentralized exchanges (DEXs) rather than utilizing existing shared infrastructures. Analysts are questioning the viability of this recurring practice.
Each time a new chain, such as Berachain or Sei, is launched, one of the first actions taken is deploying a Uniswap fork or creating a basic DEX for that specific network. This routine is criticized for yielding poor initial liquidity and subpar user experience, with many projects dragging their feet in terms of development.
The criticism surrounding this trend highlights several key issues:
Liquidity Struggles: It's common for new DEXs to face poor liquidity for up to six months, hampering trading activity and user confidence.
Rushed Smart Contracts: Many DEXs utilize hastily developed smart contracts with minimal audits, raising concerns about security and reliability.
Time Awareness: Teams expend considerable time and resources to recreate systems that are already established elsewhere.
As one observer aptly put it, "Itโs like every new city building its own power grid rather than connecting to an existing one.โ This sentiment echoes the frustration many within the community feel about the redundant efforts in launching similar DEXs across different chains.
Several comments support the idea that new blockchains should leverage a shared exchange infrastructure layer instead of building from scratch. The argument posits that a centralized limit order book (CLOB) could serve multiple chains, simplifying trading operations and enhancing liquidity from day one.
Sources suggest that sharing a backend could replace the months of bootstrapping new exchanges often require.
Observers note, "The innovation youโre describing is actually an argument for shared rails, not against them." This highlights the belief that shared infrastructure could optimize operations and reduce costs dramatically.
Interestingly, critics point out that venture capitalists (VCs) might resist this shift because supporting native DEXs boosts total value locked (TVL) narratives, propelling token values higher. As captured in a comment, "A shared CLOB is great for users, bad for that game. Incentives, not technical limits, are at play."
๐ DEX launches often experience poor liquidity in the first six months.
๐ฅ Security concerns arise from quick smart contract audits, introducing vulnerabilities.
๐ฐ VCs may favor native DEXs to support their financial models.
As more users express concerns, will major players in the crypto space rethink their strategy? Or will the cycle of forking existing solutions continue unchecked? The conversation around a shared infrastructure continues to gain traction, but tangible shifts remain to be seen.
As the crypto sector evolves, the demand for improved trading experiences is likely to push developers toward embracing shared infrastructures. There's a strong chance that within the next couple of years, we could see a significant shift where blockchain projects begin to combine resources for a centralized limit order book. Experts estimate around 60% of new blockchain initiatives might pursue partnerships to optimize liquidity and security if current trends continue. This collaboration could pave the way for a more robust ecosystem, enabling projects to thrive without starting from scratch.
Looking back to the late 1800s, the expansion of railroads in America offers an interesting parallel. During that time, small towns built their own railway systems, often resulting in isolated networks that stymied growth and economic integration. It wasn't until larger rail companies formed partnerships and standardized rail gauges that transportation revolutionized, leading to more interconnected and efficient trade across states. Similarly, todayโs blockchain projects could maximize growth potential by leveraging established infrastructures rather than opting for redundant systems.