Tempo is a Layer 1 blockchain purpose-built for global payments, developed in partnership with leading fintechs and Fortune 500 companies and incubated by Stripe and Paradigm. It delivers high-throughput, low-cost global transactions with sub-second finality, predictable fees, and native stablecoin support.

website

twitter

Blockchains (L1)

Tempo

# Tempo Contract deployers Methodology

## 1. Overview

Contract deployers measures the number of unique addresses that have initiated the deployment of at least one smart contract on Tempo. This metric serves as a proxy for the volume of independent developers or entities actively publishing code onchain. By tracking the number of distinct deployers, the growth and health of the developer ecosystem within the Tempo network are monitored.

## 2. Data sources

- **Blockchain events**: Contract creation records from the Tempo chain

## 3. Step-by-step calculation

### Component A: Contract creation extraction

- **Purpose**: Identify all successful smart contract deployments and their originators
- **Logic**: Contract deployment data is retrieved from the underlying blockchain ledger. This includes the identification of the `deployer_address` responsible for the transaction, the `contract_address` of the newly created entity, and the associated `creation_timestamp`. Only successful contract creations are included in the dataset, ensuring that failed deployment attempts do not inflate the metric.
- **Key fields**: `deployer_address`, `contract_address`, `creation_timestamp`

### Component B: Unique deployer aggregation

- **Purpose**: Calculate the daily count of distinct entities publishing code
- **Logic**: The number of unique deployer addresses is aggregated on a daily basis. Each address is counted only once per day, regardless of how many individual contracts were deployed by that specific address within the 24-hour period. This ensures the metric reflects the number of active entities rather than the total volume of contracts published.

### Component C: Normalization and zero-filling

- **Purpose**: Ensure data consistency and temporal continuity
- **Logic**: Daily totals are aligned with UTC day boundaries. For days where no contract deployments are recorded, values are zero-filled to maintain a continuous time series. Data is further filtered based on chain availability and freshness to ensure only validated records are presented in the final output.
- **Key fields**: `timestamp`, `contract_deployers`

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

Unique addresses that deployed at least one smart contract.

Tempo

Contract deployers

Contract deployers

Competitive landscape