Single Point of Failure Analysis

What's the ONE thing that could kill each project? Person, company, foundation, or infrastructure.

Disclaimer: This analysis is based on publicly available data and documentation. It is provided for educational purposes only and does not constitute financial advice. All assessments represent our methodology's output based on observable data, not accusations. Project structures may change. Submit corrections with evidence.

5
No SPOF
4
Limited
26
Single
8
Multiple

No SPOF Identified (5)

ProjectScoreSPOF TypePrimary DependencyDependency Scenario
Bitcoin(BTC)7.8None-Unkillable
Monero(XMR)6.6None-Unkillable
Dogecoin(DOGE)6.3None-Unkillable
Bitcoin Cash(BCH)6.4None-Unkillable
Litecoin(LTC)6.3None-Unkillable

Limited Dependency (4)

ProjectScoreSPOF TypePrimary DependencyDependency Scenario
Kaspa(KAS)6.0NoneSmall dev teamSurvivable via open source
Polkadot(DOT)5.3PersonFounderVision lost, but Substrate survives
Ethereum(ETH)5.6PersonFounder (social influence)Survives, loses direction
Ethereum Classic(ETC)5.8NoneSmall communitySurvives as zombie chain

Single Dependency (26)

ProjectScoreSPOF TypePrimary DependencyDependency Scenario
Cosmos Hub(ATOM)4.2FoundationCosmos Labs (2025) centralizedValidators: "excessive centralization". SDK survives, Hub fragile
Zcash(ZEC)4.8FoundationZF only (ECC resigned Jan 2026)Redundancy collapsed - ECC team left, now building cashZ independently
Uniswap(UNI)4.3ProtocolImmutable contractsLabs gone = frontend gone, forks possible
DAI(DAI)4.4ProtocolUSDC collateral riskIssuer freeze = DAI destabilized
Aave(AAVE)3.6PersonFounderSurvivable, governance exists
Lido(LDO)4.1ProtocolEthereum-dependentETH dies = Lido dies
Algorand(ALGO)4.1MultipleFoundation + Permissioned RelaysRelays permissioned, 63% Foundation stake until 2025. Foundation exit = dead
Filecoin(FIL)5.6CompanyProtocol LabsLabs gone = slow death
Cardano(ADA)5.4MultipleFounder + Single ClientFounder-dependent
NEAR Protocol(NEAR)4.3FoundationNEAR FoundationFoundation gone = dead
Sui(SUI)3.0CompanyMysten Labs + Halt capabilityNov 2024: 2h halt. 84% insider-staked. Labs gone = dead
TON(TON)3.6FoundationTON FoundationPost-Telegram, but fragile
Aptos(APT)3.4CompanyAptos LabsLabs gone = dead
Avalanche(AVAX)3.6CompanyAva Labs + Halt capabilityFeb 2024: 5h halt. Labs controls everything. Labs gone = dead
Chainlink(LINK)4.2MultipleFounder + LabsFounder leaves = project fragile
Injective(INJ)3.3CompanyInjective LabsLabs gone = dead
Fetch.ai(FET)3.6CompanyFetch.ai LtdASI Alliance-dependent, Labs gone = dead
Polygon(POL)3.3CompanyPolygon Labs + Halt capabilityMultiple halts (11h 2022, 1h+10h 2024). NC=4. Labs gone = dead
Stellar(XLM)2.9FoundationSDF (35% supply)SDF exit = collapse
Arbitrum(ARB)2.7InfrastructureCentralized SequencerSequencer down = L2 down
Solana(SOL)3.7MultipleFoundation + Halt capability7+ coordinated halts, 50h+ downtime since 2020
Internet Computer(ICP)3.0CompanyDFINITYDFINITY gone = instant death
XRP(XRP)2.5CompanyRipple LabsRipple gone = dead
Virtuals Protocol(VIRTUAL)2.9CompanyVirtuals TeamTeam gone = dead, Base-dependent
Render Network(RENDER)3.3FoundationRender Foundation + RenderLabsFoundation/Labs gone = network stalls
Figure / Provenance(FIGR_HELOC)3.0CompanyFigure Technologies (57.7% stake)Figure controls 57.7% HASH, 64 validators. Enterprise blockchain. Figure exit = dead.

Multiple Dependencies + Halt Capability (8)

ProjectScoreSPOF TypePrimary DependencyDependency Scenario
Bittensor(TAO)1.0MultipleOpentensor + Halt capabilityJuly 2024: Network halted ("safe mode"). Foundation-dependent.
Hedera(HBAR)1.0FoundationCouncil (39 corps)Council dissolves = dead
Hyperliquid(HYPE)1.0FoundationFoundation (58% stake)High exit risk based on stake concentration
Tron(TRX)1.0PersonFounderFounder exits = dead
BNB Chain(BNB)1.0CompanyBinanceBinance closed = dead
Tether(USDT)1.0CompanyTether Ltd (iFinex)Bank run = dead
USD Coin(USDC)1.0CompanyCircleRegulated, but centralized
USD1(USD1)1.0MultipleBitGo Trust + Trump Political RiskCan freeze addresses. BitGo custody risk. Trump regulatory risk.

Classification Criteria

5 of 43 projects show no identifiable single point of failure based on available data. Common characteristics observed:

  • 1.Proof of Work consensus - Permissionless participation
  • 2.No premine or insider allocation - Open distribution
  • 3.No centralized halt capability - No admin controls
  • 4.Multiple independent implementations - Client diversity

Disagree with an assessment? Submit a Pull Request