website

twitter

discord

github

Blockchains (L1)

Sonic

# Sonic Contract deployers Methodology

## 1. Overview

The contract deployers metric measures the daily count of unique addresses that deployed smart contracts on the Sonic blockchain. This metric provides insights into developer activity and platform adoption by tracking how many distinct entities are creating new contracts each day. The calculation aggregates contract creation events by day and counts distinct deployer addresses.

## 2. Data sources

- **Sonic contract creation data**: Contract deployment events captured from Sonic blockchain transaction traces, including deployer addresses, contract addresses, creation timestamps, and contract bytecode
- **Sonic block data**: Block timestamps used for daily time boundary aggregation
- **Chain metadata**: Sonic blockchain classification data for categorization as L1 blockchain

## 3. Step-by-step calculation

### Component A: Contract creation extraction
- **Purpose**: Identify all contract creation events on Sonic blockchain with relevant metadata
- **Logic**: Extract contract creation records from Sonic blockchain data, capturing the `creation_timestamp` for time aggregation, `deployer_address` for unique counting, `contract_address` for identification, and additional metadata like `creation_trace_address`, `contract_bytecode`, and `creator_address`
- **Key fields**: `creation_timestamp` (renamed to `block_timestamp`), `deployer_address`, `contract_address`

### Component B: Daily aggregation
- **Purpose**: Group contract creations by day and count distinct deployers
- **Logic**: Truncate `block_timestamp` to daily boundaries using timestamp truncation, then group by day and count distinct `deployer_address` values to measure unique deployers per day. Add chain categorization metadata including `chain_id` as sonic, `market_sector_id` as blockchains_l1, and `business_segment_id` as blockchain
- **Key fields**: `timestamp` (daily truncated), `contract_deployers` (distinct count), chain metadata fields

### Final aggregation
- **Combining components**: The daily aggregated data flows through the finalize metric macro which applies standardization including zero-filling strategy for days with no contract deployments
- **Time aggregation**: Daily boundaries are established by truncating block timestamps to day level
- **Final calculation**: The final `contract_deployers` value represents the count of distinct deployer addresses that created contracts on each day, with chain availability filtering applied to ensure data quality

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

Unique addresses that deployed at least one smart contract.

SonicS

Archived

Contract deployers

Contract deployers

Competitive landscape