Aleph Zero EVM is powered by Arbitrum's AnyTrust protocol which uses a data availability committee (DAC) to store raw transaction data.

Aleph Zero EVM is an Ethereum layer 2 powered by Arbitrum Orbit tech stack. This dashboard does not include Aleph Zero WASM data.

AZERO tokenholders own and govern the protocol.

github

twitter

discord

website

Blockchains (L2)

Aleph Zero EVM

# Aleph Zero EVM Contracts deployed Methodology

## 1. Overview

The AlephZero contracts deployed metric measures the daily number of smart contracts deployed on the AlephZero EVM blockchain. This metric tracks developer activity and ecosystem growth by counting unique contract creation events that occur each day. The calculation aggregates contract deployment transactions from blockchain data, groups them by daily timestamps, and applies gap-filling to ensure continuous daily coverage.

## 2. Data sources

- **AlephZero EVM contract creation data**: Raw blockchain data containing contract deployment information including creation timestamps, contract addresses, deployer addresses, and transaction trace addresses
- **AlephZero EVM block data**: Block timestamp information used to determine when contract deployments occurred
- **Transaction traces**: AlephZero EVM transaction execution traces that capture contract creation events

## 3. Step-by-step calculation

### Component A: Contract creation extraction
- **Purpose**: Identifies and extracts all contract creation events from AlephZero EVM blockchain data
- **Logic**: The system processes raw AlephZero EVM blockchain data to identify contract deployment transactions. Each record contains the `creation_timestamp` indicating when the contract was deployed, the `contract_address` of the newly created contract, the `deployer_address` of the account that initiated the deployment, and the `creation_trace_address` showing the transaction trace location. Duplicate records are removed using distinct selection to ensure each contract creation is counted only once.
- **Key fields**: `creation_timestamp` (when contract was created), `contract_address` (address of deployed contract), `deployer_address` (who deployed the contract), `creation_trace_address` (transaction trace reference)

### Component B: Daily aggregation
- **Purpose**: Groups contract creations by day and counts the total deployments per day
- **Logic**: The contract creation timestamps are truncated to daily boundaries, removing hour/minute/second components to group all deployments within the same calendar day. Each day's contract creations are counted using a simple count aggregation. The system adds standardized metadata including chain identifier as `Aleph Zero EVM`, market sector as `blockchains_l2`, and business segment as `blockchain`. The `product_id` field is set to null as this metric applies to the entire chain rather than a specific product.
- **Key fields**: `timestamp` (daily boundary), `timestamp_grain` (set to 'day'), `chain_id`, `market_sector_id`, `business_segment_id`, `contracts_deployed` (daily count)

### Final aggregation
- **Combining components**: The daily aggregation results are processed through the finalize metric macro which standardizes the output format
- **Currency conversion**: Not applicable for this count-based metric
- **Time aggregation**: Data is aggregated to daily boundaries with a fill zeros strategy applied to ensure every day shows a value, even if no contracts were deployed
- **Final calculation**: The final metric value represents the total count of unique smart contracts deployed on AlephZero EVM for each calendar day, with zero values filled for days without deployments and results filtered to exclude future dates beyond September 17, 2025

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

Unique smart contracts published onchain.

Aleph Zero EVMAZERO

Archived

Contracts deployed

Contracts deployed

Competitive landscape

Chain breakdown