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 Contracts deployed Methodology

## 1. Overview

The contracts deployed metric measures the daily number of smart contracts deployed on the Celo L1 (legacy) blockchain. This metric tracks the development activity and ecosystem growth by counting unique contract creation events that occur each day. The calculation accounts for Celo L1 (legacy)'s transition from Layer 1 to Layer 2 status in March 2025, applying different market sector classifications accordingly.

## 2. Data sources

- **Celo L1 (legacy) blockchain data**: Contract creation records from the Celo L1 (legacy) blockchain containing deployment timestamps, contract addresses, deployer information, and bytecode
- **Contract deployment traces**: Transaction trace data that captures the specific deployment events and their execution context
- **Block timestamp data**: Blockchain timestamp information used for daily aggregation boundaries
- **Contract metadata**: Bytecode, creator addresses, and deployment trace addresses associated with each contract creation

## 3. Step-by-step calculation

### Component A: Contract creation extraction
- **Purpose**: Identifies all contract deployment events on the Celo L1 (legacy) blockchain
- **Logic**: Extracts contract creation records from Celo L1 (legacy) blockchain data, capturing the `creation_timestamp`, `contract_address`, `deployer_address`, `creation_trace_address`, `contract_bytecode`, and `creator_address`. The data is deduplicated using distinct selection to ensure each contract creation is counted only once. The extraction process handles the temporal split at 2025-03-26 to accommodate Celo L1 (legacy)'s blockchain classification changes.
- **Key fields**: `creation_timestamp` for timing, `contract_address` for unique contract identification, `deployer_address` and `creator_address` for deployment attribution

### Component B: Daily aggregation with temporal classification
- **Purpose**: Groups contract deployments by day and applies appropriate market sector classifications
- **Logic**: Contract creation timestamps are truncated to day boundaries to enable daily counting. The calculation applies a temporal split at 2025-03-26, classifying deployments before this date under the `blockchains_l1` market sector with `Celo L1 (legacy)` as the product ID, and deployments on or after this date under the `blockchains_l2` market sector with `Celo L1 (legacy) L2` as the product ID. Each day's contract deployments are counted using aggregation, maintaining chain ID as `Celo L1 (legacy)` and business segment as `blockchain` throughout.
- **Key fields**: `timestamp` truncated to day grain, `contracts_deployed` as the count of daily deployments, market sector and product ID classifications

### Final aggregation
- **Combining components**: The two temporal periods (pre and post March 26, 2025) are combined using union all to create a complete time series while maintaining the distinct market sector classifications
- **Currency conversion**: No currency conversion required as this is a count-based metric
- **Time aggregation**: Daily boundaries are established by truncating timestamps to day level, ensuring consistent 24-hour periods for counting
- **Final calculation**: The metric applies the finalize contracts deployed macro with a fill zeros strategy to ensure complete daily coverage, filling any missing days with zero values. Chain availability filtering is applied to the final results to ensure data quality and consistency with Celo L1 (legacy) blockchain availability periods.

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

Unique smart contracts published onchain.

CeloCELO

Contracts deployed

Contracts deployed

Competitive landscape

Chain breakdown