# X Layer Contracts deployed Methodology

## 1. Overview

Contracts deployed is measured as the number of unique smart contracts published onchain on X Layer. This metric is utilized as a proxy for the volume of new infrastructure or applications launched on the blockchain. It provides insight into developer activity and ecosystem growth on X Layer.

## 2. Data sources

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

## 3. Step-by-step calculation

### Component A: Contract creation extraction

- **Purpose**: Extract unique contract deployments on X Layer
- **Logic**: Unique contract deployments are identified from onchain contract creation records. For each deployment, the creation timestamp, contract address, deployer address, creation trace address, contract bytecode, and creator address are extracted. Duplicate records are filtered out to ensure only unique contract addresses are counted.
- **Key fields**: `block_timestamp` (creation time), `account_address` (deployed contract address)

### Component B: Daily aggregation

- **Purpose**: Aggregate the count of deployed contracts on a daily basis
- **Logic**: The extracted contract deployments are aggregated by day using the truncated block timestamp. The total number of contracts deployed is calculated by counting the unique contract addresses for each daily interval. The product and chain identifiers are assigned to represent X Layer.
- **Key fields**: `timestamp` (daily truncated time), `contracts_deployed` (count of deployments)

### Component C: Normalization and zero-filling

- **Purpose**: Standardize the metric schema and ensure continuous daily data
- **Logic**: The aggregated daily counts are cast to standardized data types and validated against active chain and project registries. To ensure data continuity, days with no recorded contract deployments are filled with zero values. Chain availability filters are applied to align the data with approved operational windows.
- **Key fields**: `timestamp` (validated time), `contracts_deployed` (final daily count)

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

Unique smart contracts published onchain.

Contracts deployed

X Layer

Contracts deployed

Contracts deployed

Chain breakdown