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 Contract deployers Methodology

## 1. Overview

The Celo L1 (legacy) contract deployers metric measures the daily count of unique addresses that deploy smart contracts on the Celo L1 (legacy) network. This metric tracks developer activity and network adoption by counting distinct deployer addresses per day. The calculation includes a critical business logic that accounts for Celo L1 (legacy)'s transition from L1 to L2 architecture on March 26, 2025, classifying contract deployments differently before and after this date.

## 2. Data sources

The metric is calculated using:
- **Contract creation data**: Comprehensive records of all smart contract deployments on the Celo L1 (legacy) blockchain, including deployment timestamps, deployer addresses, contract addresses, and creation traces
- **Transaction traces**: Celo L1 (legacy) blockchain transaction execution traces that capture contract creation events and their associated metadata
- **Contract metadata**: Bytecode, creator addresses, and trace addresses associated with each contract deployment

## 3. Step-by-step calculation

### Component A: Contract creation extraction
- **Purpose**: Extract and prepare all contract deployment records from Celo L1 (legacy) blockchain data
- **Logic**: Pull all contract creation records from Celo L1 (legacy) blockchain data, including `creation_timestamp`, `contract_address`, `deployer_address`, `creation_trace_address`, `contract_bytecode`, and `creator_address`. Apply distinct deduplication to handle any duplicate records in the source data. The data is processed in two separate periods based on the March 26, 2025 network transition date.
- **Key fields**: `creation_timestamp` (renamed to `block_timestamp`), `deployer_address` for counting unique deployers, `contract_address` (renamed to `account_address`)

### Component B: Temporal classification and aggregation
- **Purpose**: Classify deployments by network era and aggregate daily deployer counts
- **Logic**: Truncate timestamps to daily boundaries using `timestamp_trunc(block_timestamp, day)`. Apply temporal classification where contracts deployed before March 26, 2025 are classified under `blockchains_l1` market sector with product ID `Celo L1 (legacy)`, while contracts deployed on or after this date are classified under `blockchains_l2` market sector with product ID `Celo L1 (legacy) L2`. Group records by day, chain metadata, and classification parameters. Count distinct `deployer_address` values for each day and classification.
- **Key fields**: Daily truncated `timestamp`, `contract_deployers` count, classification metadata including `market_sector_id` and `product_id`

### Final aggregation
- **Combining components**: Union the pre-transition and post-transition deployment counts while maintaining separate classification metadata for each period
- **Currency conversion**: Not applicable - this metric counts addresses rather than monetary values
- **Time aggregation**: Data is aggregated to daily boundaries with each day containing the count of unique contract deployers
- **Final calculation**: Apply the `finalize_metric_contract_deployers` macro with `fill_zeros` strategy to ensure continuous daily time series with zero values for days without deployments. Apply chain availability filtering to ensure data quality and completeness. The final metric value represents the count of distinct addresses that deployed at least one contract on each given day, classified appropriately based on the network transition timeline.

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

Unique addresses that deployed at least one smart contract.

CeloCELO

Contract deployers

Contract deployers

Competitive landscape

Chain breakdown