Validators process transactions and receive fees from users (supply-side fees).

Celo is a smart contract platform for decentralized applications (a blockchain). Celo was founded by Rene Reinsberg and Marek Olszewski and launched in 2020.

CELO holders own and govern the protocol. They currently take a cut of the total transaction fees paid by users (revenue). Celo's investors include a16z, Greenfield, Electric Capital, etc.

governance

github

twitter

discord

etherscan

website

Blockchains (L2)

Celo

# Celo Token holders Methodology

## 1. Overview

The Celo L1 (legacy) tokenholders metric measures the total number of unique addresses that hold the native Celo L1 (legacy) token on the Celo L1 (legacy) blockchain at the end of each day. This metric provides insights into the adoption and distribution of the native token across the network's user base. The calculation identifies all addresses with non-zero Celo L1 (legacy) balances and counts them to provide a daily snapshot of token holder growth or decline.

## 2. Data sources

The calculation relies on the following data sources:
- **Celo L1 (legacy) blockchain state data**: Daily snapshots of account balances on the Celo L1 (legacy) network
- **Native token balance records**: Balance information specifically for the Celo L1 (legacy) native token across all addresses
- **Account state snapshots**: End-of-day blockchain state data that captures the balance of each address
- **Chain metadata**: Celo L1 (legacy) network identification and timestamp information

## 3. Step-by-step calculation

### Component A: Native token balance extraction
- **Purpose**: Identifies all addresses holding Celo L1 (legacy) tokens and aggregates the count
- **Logic**: The system extracts balance data for the native Celo L1 (legacy) token from daily blockchain state snapshots. It identifies all unique addresses that have non-zero Celo L1 (legacy) token balances at the end of each day. The logic filters for addresses with positive balances to exclude empty or inactive accounts.
- **Key fields**: `timestamp` for daily snapshots, `chain` for network identification, `tokenholders` for the count of unique addresses

### Component B: Data standardization and finalization  
- **Purpose**: Standardizes the tokenholder data into the final metric format
- **Logic**: The raw tokenholder count undergoes data type conversion to ensure precision using bignumeric casting. The finalization macro applies standard metadata fields, consistent formatting, and data validation rules. Chain availability filtering ensures only valid data points are included in the final output.
- **Key fields**: `timestamp_grain` for time period specification, `chain_id` for network identification, standardized `tokenholders` count

### Final aggregation
- **Combining components**: The native tokenholder data flows directly through standardization without additional aggregation, as the count is already computed at the daily level
- **Currency conversion**: Not applicable - this is a count metric measuring number of holders, not monetary value
- **Time aggregation**: Data is captured at daily intervals using end-of-day snapshots to provide consistent daily tokenholder counts
- **Final calculation**: The final metric represents the count of unique addresses holding non-zero Celo L1 (legacy) token balances on each day, standardized with proper metadata and filtered for data quality

*This methodology was automatically generated by Token Terminal's methodology analyzer.*

Unique addresses holding a non-zero balance of the project's native token.

CeloCELO

Token holders

Token holders

Competitive landscape

Chain breakdown