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 users (weekly) Methodology

## 1. Overview

The Celo L1 (legacy) Weekly Active Users (WAU) metric measures the number of unique users who have sent at least one transaction on the Celo L1 (legacy) blockchain within any 7-day rolling window. This metric provides insights into user engagement and platform adoption over weekly periods. The calculation uses probabilistic counting with HyperLogLog algorithms to efficiently handle large-scale user data and provides breakdowns across multiple dimensions including chain, user type, and product segments.

## 2. Data sources

- **Celo L1 (legacy) blockchain transaction records**: Complete transaction history from the Celo L1 (legacy) blockchain including transaction metadata
- **Block timestamp data**: Temporal information for each transaction block used for time-based aggregations
- **Transaction hash identifiers**: Unique transaction identifiers for data integrity
- **From address data**: Transaction sender addresses representing active users on the platform

## 3. Step-by-step calculation

### Component A: User activity extraction
- **Purpose**: Identifies daily active users from Celo L1 (legacy) blockchain transaction data
- **Logic**: Extracts unique transaction sender addresses (`from_address`) for each day, treating each transaction sender as an active user. The system applies time-based product segmentation where transactions before 2025-03-26 are classified as Celo L1 (legacy) L1 activity with market sector `blockchains_l1` and product ID `Celo L1 (legacy)`, while transactions on or after this date are classified as Celo L1 (legacy) L2 activity with market sector `blockchains_l2` and product ID `Celo L1 (legacy) L2`. All users are categorized with user type `Transaction sender`
- **Key fields**: `block_timestamp` (truncated to day granularity), `transaction_hash`, `from_address` as `user_address`, `chain` (set to 'Celo L1 (legacy)'), `user_type`, `product_id`, `market_sector_id`, `business_segment_id`

### Component B: Daily user aggregation with HyperLogLog
- **Purpose**: Creates daily unique user counts using probabilistic counting methods
- **Logic**: Groups users by day, chain, user type, and product ID dimensions. Initializes HyperLogLog sketches with precision parameter 15 for each daily group to enable efficient unique user counting across time windows. The HyperLogLog algorithm provides approximate but highly accurate unique counts while using minimal memory
- **Key fields**: `timestamp` (day-truncated), `timestamp_grain` (set to 'day'), `chain`, `user_type`, `product_id`, `hll` (HyperLogLog sketch)

### Component C: Rolling window construction
- **Purpose**: Creates 7-day rolling windows for weekly active user calculation
- **Logic**: Generates a complete datespine covering all days from the earliest transaction date to current date to ensure no missing timestamps in the rolling windows. For each day in the datespine, creates associations with the current day plus the previous 6 days (total 7-day window). Joins this window structure with the daily HLL data to collect user activity data for each 7-day period
- **Key fields**: `timestamp` (target date), `joinday` (each day within the 7-day window), all dimension fields from daily aggregation

### Component D: Weekly user aggregation by dimensions
- **Purpose**: Calculates weekly active users across different analytical dimensions
- **Logic**: Merges HyperLogLog sketches within each 7-day window to count unique users who were active at any point during the week. Creates separate aggregations for four different dimensional breakdowns: project-level (all dimensions null except timestamp), chain-level (grouping by `chain_id`), user type-level (grouping by `user_type`), and product-level (grouping by `product_id`). Each breakdown uses HLL merge operations to combine daily sketches and extract final unique user counts
- **Key fields**: `timestamp`, `timestamp_grain`, `dimensions` (breakdown type), `chain_id`, `product_id`, `user_type`, `user_wau` (final weekly active user count)

### Final aggregation
- **Combining components**: Combines all dimensional breakdowns using union operations to create a single result set containing WAU metrics at project, chain, user type, and product levels
- **Currency conversion**: Not applicable for user count metrics
- **Time aggregation**: Uses 7-day rolling windows where each day represents the count of unique users active in the current day plus the previous 6 days
- **Final calculation**: The final `user_wau` value represents the approximate count of unique users who sent at least one transaction during any 7-day rolling window period, calculated by merging HyperLogLog sketches and extracting the estimated unique count. Missing days are filled with zero values to ensure complete time series coverage

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

Unique revenue-generating users over a rolling 7-day window.

CeloCELO

Active users (weekly)

Active users (weekly)

Competitive landscape

Chain breakdown