Layer 1 challengers

The throughput race

Promises of speed and cheap fees

As Ethereum gas spiked, alternative Layer 1s promised relief. Solana touted high TPS with a single global state machine; Avalanche hyped subnets and Snowball consensus; Polkadot pushed parachains and shared security; Cosmos leaned into app-chains with IBC. The pitch: cheaper, faster, friendlier UX than Ethereum’s congested base layer.

These chains launched with testnets, validator programs, and hackathons to attract builders. Token sales and foundation grants funded early apps. The message was clear: users shouldn’t accept $50 swaps or failed transactions as normal.

Different bets on decentralization

Solana required beefy hardware and high bandwidth, concentrating validators but enabling speed. Cosmos let anyone run app-chains with their own validators, trading ease for fragmented security. Polkadot and Avalanche offered shared security variants but still curated initial slots. Each chain tweaked the triangle of decentralization, throughput, and simplicity. Their docs outline the choices: Solana validators ↗, Cosmos consensus ↗, Polkadot staking ↗, Avalanche consensus ↗.

Bridges as lifelines

Because users held assets on Ethereum, bridges became the on-ramps. Wormhole, Multichain, Avalanche/Ethereum Bridge, and others locked assets on one side and minted wrapped tokens on the other. TVL accumulated quickly—bridges were the arteries of the multi-chain pitch—and also the juiciest future attack surface. Wormhole’s docs ↗ and Avalanche bridge FAQ ↗ show the trust models.

“If you’re not paying for blockspace, someone else is subsidizing you.” — Common refrain in debates about “cheap” chains

Ecosystems, outages, and funding

VC fuel and ecosystem funds

Foundations and venture funds poured billions into “ecosystem funds” to seed DEXs, NFT markets, and wallets. Solana, Avalanche, and others announced nine-figure grants. This bootstrapped apps but also drew criticism that usage was incentive-driven and might evaporate without subsidies. Examples include Solana’s fund ↗ and Avalanche Rush ↗.

Outages and reliability scars

Solana faced multiple network halts (congestion, resource exhaustion, validator coordination issues). Avalanche and others weathered smaller incidents. These events underscored the tension between pushing throughput and maintaining resilience. Status pages and postmortems became part of the brand. Solana’s status page ↗ became a regular checkpoint.

Developer experience and culture

Rust on Solana, Go/Rust in Cosmos SDK, Solidity/EVM clones on Avalanche C-Chain—all influenced what got built. EVM compatibility pulled the largest developer base; non-EVM chains offered performance but higher cognitive load. Wallet fragmentation (Phantom vs. Metamask vs. Keplr) reminded users that multi-chain UX was still rough.

Trade-offs, bridges, and legacy

Security models compared

Validator set size, hardware requirements, slashing rules, and governance speed varied. Some chains skewed toward performance at the cost of decentralization optics; others favored flexibility (app-chains) but increased coordination complexity. Users began to ask: who runs the validators? How hard is it to join? Who can pause the chain?

Bridge risk foreshadowed

Even in the early rush, security teams warned that bridges would become prime targets. Many relied on multisigs or light-client shortcuts rather than full verification. TVL piled up anyway. Later hacks (Wormhole, Ronin, etc.) would validate the fears, but the seeds were planted during this expansion.

Legacy

The L1 challenger wave made multi-chain a default assumption and pressured Ethereum to scale (rollups, EIP-1559 UX, gas optimizations). It showed that users will leave for better UX—and return if trust and liquidity follow. It also cemented that “cheap” comes with trade-offs users should understand.