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 Contract deployers Methodology

## 1. Overview

This metric measures the daily count of unique addresses that deployed smart contracts on the AlephZero EVM blockchain. It answers the question "How many distinct users deployed contracts each day?" by counting unique deployer addresses per day, providing insight into developer activity and smart contract deployment trends on the AlephZero network.

## 2. Data sources

- **AlephZero EVM contract creation records**: Blockchain data containing contract deployment information from the AlephZero EVM network
- **Contract metadata**: Information about deployed contracts including contract addresses, deployer addresses, creation timestamps, and trace addresses
- **Transaction traces**: AlephZero EVM transaction execution traces that capture contract creation events

## 3. Step-by-step calculation

### Component A: Contract creation data extraction
- **Purpose**: Extracts all contract creation events from AlephZero EVM blockchain
- **Logic**: Retrieves contract creation records from AlephZero EVM blockchain data, capturing each instance where a smart contract was deployed. The data includes the timestamp when the 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 of the creation transaction (`creation_trace_address`). Duplicate records are removed to ensure each contract creation is counted only once.
- **Key fields**: `creation_timestamp` for timing, `contract_address` for the deployed contract identifier, `deployer_address` for the entity that created the contract, `creation_trace_address` for transaction trace reference

### Component B: Daily aggregation and counting
- **Purpose**: Groups contract creations by day and counts unique deployers
- **Logic**: Contract creation events are grouped by day using timestamp truncation to day boundaries. For each day, the system counts distinct deployer addresses to measure unique entities that deployed contracts, ensuring that addresses which deployed multiple contracts on the same day are counted only once. Metadata fields are added to classify the data as belonging to AlephZero EVM chain (`Aleph Zero EVM`), Layer 2 blockchain market sector (`blockchains_l2`), and blockchain business segment (`blockchain`). The product identifier is set to null as this represents chain-level activity rather than specific product usage.
- **Key fields**: `timestamp` truncated to day boundaries, `contract_deployers` as the count of distinct deployer addresses, chain and sector classification metadata

### Final aggregation
- **Combining components**: The daily aggregated data flows through a finalization macro that applies additional processing
- **Time aggregation**: Data is grouped by calendar day boundaries using timestamp truncation
- **Data filling**: A fill-zeros strategy is applied to ensure days with no contract deployments show zero rather than missing values
- **Final calculation**: The final metric represents the count of unique deployer addresses per day, with data filtered to exclude records after September 17, 2025, ensuring data quality and boundary enforcement

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

Unique addresses that deployed at least one smart contract.

Aleph Zero EVMAZERO

Archived

Contract deployers

Contract deployers

Competitive landscape

Chain breakdown