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 Contracts deployed Methodology

## 1. Overview

The Avalanche contracts deployed metric measures the daily count of smart contracts deployed on the Avalanche C-Chain. This metric tracks blockchain development activity by counting unique contract creation events that occur each day. It provides insight into developer activity and ecosystem growth on the Avalanche network.

## 2. Data sources

The calculation uses the following raw data sources:
- **Avalanche transaction traces**: Execution traces from Avalanche C-Chain transactions that capture contract deployment operations
- **Block timestamp data**: Avalanche network block timestamps to determine when contract creations occurred
- **Contract metadata**: Information about newly created contracts including their addresses and deploying accounts

## 3. Step-by-step calculation

### Component A: Contract creation event extraction
- **Purpose**: Identify and standardize all contract creation events from Avalanche blockchain data
- **Logic**: Extract contract creation records from Avalanche transaction traces, capturing the `creation_timestamp` (when the contract was deployed), `contract_address` (address of the newly created contract), `deployer_address` (account that deployed the contract), and `creation_trace_address` (execution context within the transaction). Apply distinct filtering to remove any potential duplicate records from the raw blockchain data.
- **Key fields**: `creation_timestamp` for timing, `contract_address` for unique contract identification, `deployer_address` for creator tracking

### Component B: Daily aggregation
- **Purpose**: Group contract creations by day and count the total deployments per day
- **Logic**: Truncate the `creation_timestamp` to day boundaries to create daily time buckets. Group all contract creation events by the truncated day timestamp and count the total number of contracts deployed each day using count aggregation. Add standardized metadata fields including `chain_id` as 'avalanche', `market_sector_id` as 'blockchains_l1', and `business_segment_id` as 'blockchain'.
- **Key fields**: `timestamp` (daily boundary), `contracts_deployed` (daily count), metadata classification fields

### Final aggregation
- **Combining components**: The daily contract counts are processed through the finalize metric macro which applies time series standardization
- **Time series completion**: Apply fill zeros strategy to ensure complete daily coverage with zero values for days with no contract deployments
- **Data availability filtering**: Apply chain availability filtering to respect the data availability window for Avalanche network data
- **Final calculation**: The result is a daily time series showing the count of unique smart contracts deployed on Avalanche each day, with complete coverage and proper handling of days with zero deployments

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

Unique smart contracts published onchain.

AvalancheAVAX

Contracts deployed

Contracts deployed

Competitive landscape