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

Aptos is a smart contract platform for decentralized applications (a blockchain). Aptos was founded by Mo Shaikh and Avery Ching and launched in 2022.

APT token holders own and govern the protocol. They currently don’t take a cut of the total transaction fees paid by users (revenue). Aptos’ investors include Binance Labs, Jump Crypto, Apollo, etc.

governance

github

twitter

discord

website

Blockchains (L1)

Aptos

# Aptos Contract deployers Methodology

## 1. Overview

The Aptos contract deployers metric measures the daily count of unique addresses that deployed smart contracts on the Aptos blockchain. This metric tracks development activity and ecosystem growth by identifying how many distinct entities are deploying new contracts each day. The calculation uses a distinct count approach to ensure deployers who create multiple contracts on the same day are only counted once.

## 2. Data sources

- **Aptos contract deployment data**: Contract creation records from the Aptos blockchain containing deployment timestamps, contract identifiers, and deployer addresses
- **Aptos transaction logs**: Blockchain transaction data that captures contract creation events and associated metadata
- **Aptos network events**: On-chain events that record when new smart contracts are deployed to the network

## 3. Step-by-step calculation

### Component A: Contract creation extraction
- **Purpose**: Extracts all contract deployment events from the Aptos blockchain
- **Logic**: Retrieves contract creation records including the `creation_timestamp`, `contract_id`, and `deployer_address` from Aptos contract deployment data. Uses distinct selection to ensure each contract creation is counted only once and removes any duplicate records
- **Key fields**: `creation_timestamp` (when the contract was deployed), `contract_id` (unique identifier for the deployed contract), `deployer_address` (the address that created the contract)

### Component B: Daily aggregation
- **Purpose**: Groups contract deployments by day and counts unique deployers
- **Logic**: Truncates the `creation_timestamp` to daily boundaries to create consistent time periods. Groups all contract creations by day and counts distinct `deployer_address` values to ensure addresses that deploy multiple contracts on the same day are only counted once. Assigns standardized metadata including chain identifier as 'aptos', market sector as 'blockchains_l1', and business segment as 'blockchain'
- **Key fields**: `timestamp` (daily boundary), `contract_deployers` (distinct count of deployer addresses per day)

### Final aggregation
- **Combining components**: The daily aggregation directly produces the final metric values without additional combination steps
- **Currency conversion**: No currency conversion required as this is a count-based metric
- **Time aggregation**: Data is aggregated at daily boundaries with consistent UTC timezone handling
- **Final calculation**: The final metric value represents the count of distinct addresses that deployed at least one smart contract on each given day. A fill-zeros strategy ensures that days with no contract deployments show zero rather than missing values. Chain availability filtering ensures only periods with complete data coverage are included in the final results.

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

Unique addresses that deployed at least one smart contract.

AptosAPT

Contract deployers

Contract deployers

Competitive landscape