twitter

etherscan

website

Blockchains (L2)

Unichain

# Unichain Contracts deployed Methodology

## 1. Overview

The Unichain contracts deployed metric measures the daily number of smart contracts deployed on the Unichain blockchain. This metric tracks blockchain development activity by counting unique contract creation events that occur each day. The calculation aggregates contract deployment transactions by day and applies standardized formatting for consistent time series reporting.

## 2. Data sources

The metric uses the following raw data sources:
- **Unichain contract creation events**: Parsed blockchain transaction traces that capture contract deployment transactions, including creation timestamps, contract addresses, deployer information, and bytecode
- **Unichain transaction traces**: Detailed execution traces from Unichain blocks that identify contract creation operations
- **Block timestamp data**: Unichain block timestamps used for daily aggregation boundaries

## 3. Step-by-step calculation

### Component A: Contract creation identification
- **Purpose**: Identify and extract all unique contract creation events from Unichain blockchain data
- **Logic**: The system processes Unichain blockchain transaction traces to identify contract deployment events. Each contract creation is captured with its `creation_timestamp` (when the contract was deployed), `contract_address` (the deployed contract's address), `deployer_address` (who initiated the deployment), `creation_trace_address` (trace location), `contract_bytecode` (the deployed code), and `creator_address` (the creator). Duplicate contract creation records are removed using distinct selection to ensure each contract deployment is counted only once.
- **Key fields**: `creation_timestamp` for timing, `contract_address` for unique identification, `deployer_address` and `creator_address` for attribution tracking

### Component B: Daily aggregation
- **Purpose**: Group contract creations by day and count total deployments per day
- **Logic**: Contract creation timestamps are truncated to day boundaries using timestamp truncation. All contract creations occurring within each calendar day are grouped together and counted using simple counting aggregation. The aggregation includes standard metric metadata with `chain_id` set to 'unichain', `market_sector_id` as 'blockchains_l2' (indicating this is a Layer 2 blockchain), `business_segment_id` as 'blockchain', and `product_id` as null since this is a general blockchain metric rather than product-specific.
- **Key fields**: `timestamp` (truncated to day), `contracts_deployed` (daily count), chain and sector classification fields

### Final aggregation
- **Combining components**: The daily aggregated data flows through the finalize metric macro which applies standardized formatting and ensures data quality
- **Time series completion**: A fill-zeros strategy is applied to ensure complete daily time series, inserting zero values for any days when no contracts were deployed
- **Data quality filtering**: Chain availability filtering is applied to respect the data availability windows for Unichain, ensuring only reliable data periods are included in the final metric
- **Final calculation**: The final metric value represents the total count of unique smart contracts deployed on Unichain for each calendar day, with complete time series coverage and standardized metadata formatting

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

Unique smart contracts published onchain.

UnichainUNI

Contracts deployed

Contracts deployed

Competitive landscape

Chain breakdown