github

twitter

website

Exchanges (CEX)

# OKX Contracts deployed Methodology

## 1. Overview

The number of unique smart contracts published onchain is measured by Contracts deployed. The volume of new infrastructure and applications launched on X Layer is represented by this metric. Developer activity and ecosystem growth are evaluated through the aggregation of these deployments over time.

## 2. Data sources

- **Blockchain events**: Contract creation records containing contract addresses, deployer addresses, and creation timestamps, covering X Layer

## 3. Step-by-step calculation

### Component A: Contract creation extraction

- **Purpose**: Identify unique contract deployments on the network
- **Logic**: Distinct contract creation records are retrieved from the onchain registry. For each deployment, the contract address, deployer address, creator address, and creation timestamp are extracted to establish a unique record of the deployed infrastructure.
- **Key fields**: `timestamp`, `contract_address`, `deployer_address`, `creator_address`

### Component B: Daily aggregation

- **Purpose**: Aggregate the number of deployed contracts on a daily basis
- **Logic**: The extracted contract creation timestamps are normalized to daily boundaries. The total number of unique contract deployments is calculated by counting the occurrences of unique contract addresses for each day.
- **Key fields**: `timestamp`, `contracts_deployed`

### Component C: Validation and normalization

- **Purpose**: Ensure data integrity and align with platform standards
- **Logic**: The daily counts are cast to standardized data types and validated against active chain and data identifiers. Chain availability filters are applied to ensure only approved and active historical data is presented.
- **Key fields**: `timestamp`, `chain_id`, `contracts_deployed`

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

Unique smart contracts published onchain.

OKXOKB

Contracts deployed

Contracts deployed

Competitive landscape

Chain breakdown