Validators process transactions and receive validator rewards (supply-side fees).

AVAX is a smart contract platform for decentralized applications (a blockchain). Avalanche was founded by Emin Gün Sirer and launched in 2019.

AVAX holders own and govern the protocol. They currently take (burn) all of the total transaction fees paid by users (revenue). AVAXs investors include a16z, Polychain, Galaxy Digital, etc.

github

twitter

discord

etherscan

website

Blockchains (L1)

Avalanche

# Avalanche Contract deployers Methodology

## 1. Overview

Contract deployers measures the daily count of unique addresses that deployed smart contracts on the Avalanche blockchain. This metric tracks developer activity and smart contract creation patterns by identifying distinct deployer addresses per day. The calculation uses an approximate distinct count to efficiently handle large volumes of contract creation data while maintaining accuracy for analytics purposes.

## 2. Data sources

The calculation relies on the following data sources:
- **Avalanche contract creation records**: Blockchain data capturing all smart contract deployments on the Avalanche network, including deployer addresses, contract addresses, creation timestamps, and transaction trace information
- **Avalanche block timestamp data**: Timestamp information for when contract creation transactions were included in blocks
- **Avalanche transaction traces**: Detailed execution traces showing the specific addresses and operations involved in contract deployment transactions

## 3. Step-by-step calculation

### Component A: Contract creation data extraction
- **Purpose**: Extracts and standardizes contract creation events from the Avalanche blockchain
- **Logic**: Retrieves all contract deployment records from Avalanche blockchain data, capturing the timestamp when each contract was created (`creation_timestamp`), the address of the deployed contract (`contract_address`), the address that deployed the contract (`deployer_address`), and the trace address showing the specific execution context (`creation_trace_address`). The data is deduplicated using distinct selection to ensure each contract creation is counted only once.
- **Key fields**: `creation_timestamp`, `contract_address`, `deployer_address`, `creation_trace_address`

### Component B: Daily aggregation and counting
- **Purpose**: Groups contract creations by day and counts unique deployers
- **Logic**: Truncates the `block_timestamp` field to day-level precision to establish daily boundaries. Groups all records by the truncated timestamp and applies an approximate distinct count on `deployer_address` to calculate the number of unique addresses that deployed contracts each day. The approximate count function provides computational efficiency while maintaining high accuracy for large datasets.
- **Key fields**: Daily truncated `timestamp`, `contract_deployers` count

### Final aggregation
- **Combining components**: The daily aggregated data is enhanced with standardized metadata fields including `chain_id` set to 'avalanche', `market_sector_id` set to 'blockchains_l1', `business_segment_id` set to 'blockchain', and `product_id` set to null
- **Currency conversion**: Not applicable for this count-based metric
- **Time aggregation**: Daily boundaries are established using timestamp truncation to day level, ensuring consistent 24-hour periods in UTC timezone
- **Final calculation**: The final metric value represents the approximate distinct count of deployer addresses that created smart contracts on each day, processed through a standardization macro that applies fill-zeros strategy for missing days and chain availability filtering for data quality assurance

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

Unique addresses that deployed at least one smart contract.

AvalancheAVAX

Contract deployers

Contract deployers

Competitive landscape