Collators aggregate parachain transactions block candidates and producing state transition proofs for validators based on those blocks.

Acala is a specialized stablecoin and liquidity blockchain powered by Polkadot Relay chain.

ACA holders own and govern the protocol. Acala’s investors include Pantera Capital, Coinbase Ventures, and Polychain Capital.

website

github

twitter

discord

etherscan

Blockchains (L2)

Acala Network

# Acala Network Contracts deployed Methodology

## 1. Overview

The contracts deployed metric measures the daily count of unique smart contracts deployed on the Acala blockchain. This metric tracks developer activity and platform growth by counting each contract only once, on the day it was first deployed. The calculation focuses specifically on successful EVM contract deployments within the Acala ecosystem.

## 2. Data sources

- **Acala blockchain event logs**: Parsed event data from the Acala blockchain's EVM pallet, specifically `Executed` events that indicate successful contract deployments
- **Acala extrinsic execution data**: Transaction execution records that provide success status and execution context
- **Block metadata**: Block timestamps and numbers from the Acala blockchain for temporal ordering and daily aggregation

## 3. Step-by-step calculation

### Component A: Contract creation event extraction
- **Purpose**: Identifies and extracts successful contract deployment events from Acala blockchain data
- **Logic**: Filters blockchain event logs for events from the `evm` pallet with method `Executed` where the execution was successful (`success` is true) and the extrinsic identifier exists. Extracts the deployed contract address from the second element of the event data array and the deployer address from the first element. Captures block timestamp, block number, extrinsic hash, and event index for context.
- **Key fields**: `contract_deployed` (the address of the newly deployed contract), `contract_deployer` (the address that deployed the contract), `block_timestamp` (when the deployment occurred)

### Component B: First occurrence identification  
- **Purpose**: Ensures each contract is counted only once by finding its first deployment date
- **Logic**: Groups all contract deployment records by the `contract_deployed` address and selects the minimum `block_timestamp` truncated to day level for each unique contract. This deduplication step prevents double counting if the same contract appears in multiple events or blocks.
- **Key fields**: `contract_deployed` (unique contract address), `timestamp` (the day the contract was first deployed)

### Component C: Daily aggregation
- **Purpose**: Counts the number of unique contracts deployed per day with proper metadata
- **Logic**: Groups the first occurrence data by day and counts the distinct number of contracts deployed on each date. Assigns static identifiers including `product_id` as 'Acala EVM' to indicate the Acala EVM environment and `chain_id` as 'acala' for chain identification. Sets `timestamp_grain` to 'day' to indicate daily aggregation.
- **Key fields**: `timestamp` (daily date), `contracts_deployed` (count of unique contracts deployed that day), `product_id`, `chain_id`, `timestamp_grain`

### Final aggregation
- **Combining components**: The daily aggregated data flows through the `finalize_metric_contracts_deployed` macro which applies standardized formatting and implements a zero-fill strategy for missing dates
- **Time aggregation**: Data is aggregated at daily boundaries using timestamp truncation to day level, ensuring consistent daily reporting periods
- **Data quality**: Chain availability filter is applied to ensure only valid time periods with reliable data are included in the final output
- **Final calculation**: The metric represents the count of distinct smart contracts that had their first successful deployment on each given day on the Acala blockchain

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

Unique smart contracts published onchain.

Acala NetworkACA

Archived

Contracts deployed

Contracts deployed

Competitive landscape

Chain breakdown