Moderate risk — instant Security Council upgrade powers and EigenDA dependency create trust assumptions, balanced by a decentralized sequencer design, active governance community, and unique real-world payments adoption.
Top Risks
1
Celo L2 contracts are instantly upgradeable by a Security Council (6-of-8 multisig) with no exit window for users. In the event of an unwanted upgrade, users have no opportunity to withdraw their funds before the changes take effect.
2
Celo uses EigenDA for data availability rather than posting full data to Ethereum. While EigenDA is secured by restaked ETH, it introduces an additional trust assumption: if EigenDA operators fail or withhold data, users cannot independently reconstruct the chain state.
3
The migration from L1 to L2 (completed March 2025) is a significant architectural transition. While the existing validator set provides decentralized sequencing, the L2 architecture changes security assumptions compared to the original standalone L1. Edge cases in the migration could create unexpected vulnerabilities.
4
The Moola Market exploit on Celo (October 2022, $9.1M) demonstrated that DeFi protocols on Celo are vulnerable to standard market manipulation attacks. While this was a protocol-level vulnerability (not Celo chain-level), it affected user trust in the ecosystem.
Risk Breakdown
Frequently Asked Questions
Is Celo safe to use?
Celo receives a B risk grade (26/100) from Hindenrank, where lower scores indicate lower risk. Moderate risk — instant Security Council upgrade powers and EigenDA dependency create trust assumptions, balanced by a decentralized sequencer design, active governance community, and unique real-world payments adoption. Celo is a recently transitioned Ethereum Layer 2 (migrated from L1 in March 2025) built on the OP Stack with EigenDA for data availability. With approximately $200M in TVL and a focus on mobile-first real-world payments in emerging markets, it occupies a unique niche among L2s. Its B grade reflects strong documentation, an active governance community, and a novel decentralized sequencer design using its existing BFT validator set. The main risk factors are the Security Council's instant upgrade powers (no exit window), reliance on EigenDA for data availability, and potential edge cases from the recent L1-to-L2 migration. The 2022 Moola Market exploit ($9.1M, mostly recovered) was a DeFi protocol-level issue, not a Celo chain vulnerability.
What are the main risks of using Celo?
The key risks identified for Celo are: (1) Celo L2 contracts can be instantly upgraded by a Security Council (6-of-8 multisig) with no exit window for users. If the council is compromised, users have no opportunity to withdraw their funds before potentially harmful changes take effect. (2) Celo uses EigenDA for data availability rather than posting full transaction data to Ethereum. While EigenDA is secured by restaked ETH, this adds a trust assumption: if EigenDA operators fail or withhold data, users cannot independently verify the chain state or construct withdrawal proofs. (3) The migration from an independent L1 to an OP Stack L2 was completed in March 2025, making Celo's L2 architecture relatively new. While extensive testing was conducted, major chain migrations carry inherent risk from edge cases that may not surface until specific transaction patterns are encountered. (4) Celo's native stablecoins (cUSD, cEUR) depend on the Mento stability protocol which now operates within the L2 architecture. Any disruption to the L2 or bridge could affect the stability mechanism's ability to maintain the peg, impacting real-world payment users in emerging markets.
What is Celo's risk score breakdown?
Celo scores 26/100 across eight risk dimensions: Mechanism Novelty: 3/15, Interaction Severity: 5/20, Oracle Surface: 0/10, Documentation Gaps: 2/10, Track Record: 3/15, Scale Exposure: 5/10, Regulatory Risk: 4/10, Vitality Risk: 4/10. The highest risk area is Scale Exposure at 5/10.
How does Celo compare to other L2 protocols?
Among 37 rated L2 protocols on Hindenrank, Celo ranks #4 by safety (lowest risk score = safest). Its 26/100 risk score and B grade place it among the safer L2 protocols.
Has Celo ever been hacked or exploited?
Celo scores 3/15 on the Track Record risk dimension, indicating some history of security incidents or exploits. Higher scores reflect more severe or frequent incidents. Review the full risk report for details.