Chapter 11

Security and Validators

Security on alt L1s is not a single knob. Validator count, stake distribution, slashing conditions, client diversity, and upgrade governance all shape how a chain fails — and alt L1s fail differently than Ethereum, often with faster finality but more concentrated stake or heavier hardware requirements.

No chain maximizes every security dimension. The table summarizes typical tradeoffs — actual numbers shift with market conditions and governance decisions.

How validator models compare

Chain	Validator model	Common risk surface
Ethereum	~1M+ validators via staking pools	L1 congestion, not liveness failures
Solana	~1,500 validators, high hardware bar	Network halts, client bugs, stake concentration
Cosmos Hub	~180 active validators, BFT	Relayer liveness, IBC misconfiguration
Avalanche	Thousands of validators, sub-sampled	Subnet security varies independently
NEAR	100-seat validator set per shard era	Smaller set, sharding coordination bugs

Outages and halts are part of the record for several alt L1s. Resilience comes from multiple independent clients, decentralized stake, and transparent incident response — not just high TPS.

Stake concentration is the metric insiders watch. When a handful of entities control one-third or more of staked tokens, censorship or coordinated reorgs become plausible even if unprofitable. Block explorers and staking dashboards publish this data — check it before treating an alt L1 as equivalently decentralized to Ethereum.

Upgrade governance adds another axis. Some chains coordinate breaking changes through on-chain votes; others rely on core team releases with social consensus. Fast iteration helps fix bugs quickly but also means the rules can change underneath deployed applications. Read the governance track record the same way you read audit reports.