Validators process transactions and receive fees from users (supply-side fees).

Astar is a collective driving web3 adoption by connecting people through blockchain technology, business innovation, decentralized applications, and seamless digital experiences in the Polkadot ecosystem. Astar was founded by Sota Watanabe and launched in 2021.

ASTR tokenholders own and govern the protocol. Part of the transaction fees is burned (revenue). Astar’s investors include Binance, Polychain Capital, Crypto.com, etc.

website

twitter

github

discord

Blockchains (L2)

Astar

# Astar Contracts deployed Methodology

## 1. Overview

The Astar contracts deployed metric measures the daily number of smart contracts deployed on the Astar blockchain. This metric tracks new contract creations by identifying `NewAccount` events from the system pallet that are associated with contract deployments, providing insight into development activity and ecosystem growth on Astar.

## 2. Data sources

- **Astar blockchain event logs**: Raw event data from Astar's substrate-based blockchain including block timestamps, event indices, and event metadata
- **System pallet events**: Astar's system pallet `NewAccount` events that signal the creation of new accounts, including smart contracts
- **Ethereum pallet events**: Astar's ethereum compatibility layer `Executed` events that provide EVM transaction context and deployer information
- **Extrinsic data**: Transaction-level data that links related events through extrinsic identifiers

## 3. Step-by-step calculation

### Component A: Event data preparation
- **Purpose**: Extract and prepare raw Astar blockchain events for analysis
- **Logic**: Retrieve all events from Astar blockchain event logs and truncate block timestamps to daily boundaries. Filter data incrementally to process only recent days for efficiency while maintaining complete historical coverage
- **Key fields**: Daily truncated `timestamp`, `event_data` arrays, `event_method`, `event_pallet`, `extrinsic_id` for transaction linking

### Component B: Contract creation identification
- **Purpose**: Identify smart contract deployments from system events
- **Logic**: Filter events to system pallet `NewAccount` events which indicate new account creation. Extract contract addresses from the first element of the `event_data` JSON array. Only include events with valid extrinsic identifiers to ensure they represent actual transactions. Apply address normalization by converting to lowercase
- **Key fields**: `contract_address` extracted from `event_data`, `extrinsic_id` for linking, `timestamp` for daily grouping

### Component C: Deployer information enrichment
- **Purpose**: Identify who deployed each contract by linking EVM execution context
- **Logic**: Extract ethereum pallet `Executed` events that provide EVM transaction context. Parse deployer addresses from the first element and EVM transaction hashes from the third element of the `event_data` array. This connects substrate-level contract creation with EVM-level transaction execution
- **Key fields**: `signer_address` as deployer, `evm_hash` for transaction reference, `extrinsic_id` for linking to contract creations

### Component D: Contract deployment assembly
- **Purpose**: Combine contract creation events with their deployment context
- **Logic**: Perform left join between contract creations and deployer information using `extrinsic_id` as the linking key. This preserves all contract creations while enriching them with deployer information where available. Handle cases where deployer information may not be available for certain contract types
- **Key fields**: Complete contract deployment records with `contract_address`, `deployer_address`, and deployment `timestamp`

### Final aggregation
- **Combining components**: Count all contract deployment records grouped by daily timestamp, chain identifier, and product identifier
- **Currency conversion**: Not applicable for this count-based metric
- **Time aggregation**: Group by daily timestamp boundaries, applying zero-fill strategy to ensure continuous daily series even on days with no deployments
- **Final calculation**: Sum the count of contract deployments per day, standardized through the `finalize_metric_contracts_deployed` macro which handles metric formatting, zero-filling for missing days, and chain availability filtering to ensure data quality

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

Unique smart contracts published onchain.

AstarASTR

Contracts deployed

Contracts deployed

Competitive landscape

Chain breakdown