website

twitter

discord

github

Blockchains (L1)

Sonic

# Sonic Contracts deployed Methodology

## 1. Overview

The contracts deployed metric measures the daily count of new smart contracts deployed to the Sonic blockchain. This metric tracks blockchain development activity by counting each unique contract creation event that occurs on the network. The calculation aggregates contract deployment transactions by calendar day to provide a time-series view of development activity and network growth.

## 2. Data sources

The metric relies on the following raw data sources:
- **Sonic blockchain contract data**: Parsed contract creation records extracted from Sonic blockchain transaction traces and block data
- **Sonic transaction traces**: Execution traces that capture contract deployment events and their context
- **Sonic block timestamps**: Block-level temporal data used to assign deployment events to specific calendar days

## 3. Step-by-step calculation

### Component A: Contract creation extraction
- **Purpose**: Identifies and extracts all unique contract deployment events from raw Sonic blockchain data
- **Logic**: The system pulls distinct contract creation records from Sonic blockchain data to ensure each contract deployment is counted exactly once. Key fields extracted include the `creation_timestamp` from the block when the contract was deployed, the `contract_address` of the newly created contract, the `deployer_address` of the account that initiated the deployment, `creation_trace_address` showing the execution context, `contract_bytecode` of the deployed contract, and `creator_address`. The distinct operation prevents duplicate counting of the same contract deployment event.
- **Key fields**: `creation_timestamp` for temporal assignment, `contract_address` as the unique identifier for each deployed contract, `deployer_address` and `creator_address` for attribution

### Component B: Daily aggregation  
- **Purpose**: Groups contract deployments by calendar day and counts the total number of contracts deployed each day
- **Logic**: Contract creation events are grouped by calendar day using timestamp truncation on the `creation_timestamp` field from the blockchain data. The system counts all contract deployments that occurred within each 24-hour period using a simple count aggregation. Days with no contract deployments are handled through gap-filling logic that assigns zero values to maintain time-series continuity.
- **Key fields**: `timestamp` truncated to day granularity, `contracts_deployed` as the daily count, metadata fields including `chain_id` set to 'sonic', `market_sector_id` set to 'blockchains_l1', and `business_segment_id` set to 'blockchain'

### Final aggregation
- **Combining components**: The extracted contract creation events are directly aggregated by day without additional joining or combining of separate data sources
- **Currency conversion**: Not applicable for this count-based metric
- **Time aggregation**: Contract deployments are assigned to calendar days based on the block timestamp when the deployment transaction was included in a block. The system uses day-level boundaries and fills missing days with zero values
- **Final calculation**: The metric value equals the total count of distinct contracts deployed on each calendar day, filtered to only include time periods when Sonic chain data is available and reliable

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

Unique smart contracts published onchain.

SonicS

Archived

Contracts deployed

Contracts deployed

Competitive landscape