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 Active addresses (daily) Methodology

## 1. Overview

Active addresses daily for Celo L1 (legacy) measures the number of unique addresses that sent at least one transaction on the Celo L1 (legacy) blockchain each day. This metric answers the question "How many unique addresses were actively transacting on Celo L1 (legacy) today?" and serves as a key indicator of daily network activity and user engagement. The calculation uses a direct mapping where active addresses equals daily active users, defined as unique transaction senders per day.

## 2. Data sources

- **Celo L1 (legacy) blockchain transaction records**: Complete transaction data from the Celo L1 (legacy) blockchain including transaction metadata, timestamps, sender addresses, and transaction hashes
- **Chain availability configuration data**: Internal configuration data used to filter and validate chain-specific data availability

## 3. Step-by-step calculation

### Component A: User identification and classification
- **Purpose**: Identifies unique transaction senders from Celo L1 (legacy) blockchain transactions and classifies them by network version
- **Logic**: Extracts all transaction records from Celo L1 (legacy) blockchain data, using the `from_address` field to identify transaction senders. Applies temporal segmentation where transactions occurring before March 26, 2025 are classified as Celo L1 (legacy) L1 activities with product identifier 'Celo L1 (legacy)', while transactions on or after this date are classified as Celo L1 (legacy) L2 activities with product identifier 'Celo L1 (legacy) L2'. Each sender is categorized as a "Transaction sender" user type and assigned appropriate market sector identifiers (blockchains_l1 or blockchains_l2)
- **Key fields**: `block_timestamp` for temporal analysis, `transaction_hash` for transaction identification, `from_address` as the unique user identifier, and derived classification fields for network segmentation

### Component B: Daily active user calculation
- **Purpose**: Deduplicates user addresses within daily time boundaries to count unique active users per day
- **Logic**: Truncates transaction timestamps to day-level granularity and removes duplicate user addresses within each day. Creates distinct records for each unique combination of day, chain, user type, market sector, business segment, product identifier, and user address. Applies incremental processing logic to optimize performance by only reprocessing recent data when updating
- **Key fields**: `timestamp` (truncated to day), `user_address` for deduplication, and classification dimensions for segmentation

### Component C: HyperLogLog aggregation across dimensions
- **Purpose**: Aggregates daily active users using probabilistic counting across multiple dimensional breakdowns
- **Logic**: Creates HyperLogLog sketches for each user address to enable efficient approximate counting. Performs aggregation across four different dimensional breakdowns: project-level aggregation (project_dbt_tag) for overall Celo L1 (legacy) counts, chain-level breakdown for network-specific analysis, user type breakdown for classification analysis, and product identifier breakdown for L1/L2 segmentation. Uses HyperLogLog merge operations to combine sketches and extract final counts for each dimensional combination
- **Key fields**: `user_dau` containing the approximate distinct count of active users, `dimensions` indicating the aggregation level, and dimension-specific identifier fields

### Final aggregation
- **Combining components**: Selects only the 'chain' and 'project_dbt_tag' dimensional breakdowns from the HyperLogLog aggregation results, filtering out user type and product identifier dimensions
- **Currency conversion**: Not applicable as this is a count-based metric
- **Time aggregation**: Data is already aggregated to daily boundaries with day-level timestamp truncation
- **Final calculation**: Renames the `user_dau` field to `active_addresses_daily` to reflect the metric definition, applies finalization logic including standardized schema formatting and zero-filling for missing days in the time series, and applies chain availability filters to ensure data quality and completeness

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

Unique active addresses over a fixed 24-hour window.

CeloCELO

Active addresses (daily)

Active addresses (daily)

Competitive landscape

Chain breakdown