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

The Open Network (TON) is a smart contract platform for decentralized applications (a blockchain). The Open Network was founded by Telegram and launched in 2019.

GRAM holders own and govern the protocol. They currently take (burn) a cut of the total transaction fees paid by users (revenue). The Open Network's investors include KuCoin Ventures, MEXC Ventures, DWF Labs, etc.

governance

github

twitter

etherscan

website

Blockchains (L1)

# TON Contracts deployed Methodology

## 1. Overview

The contracts deployed metric measures the daily count of new smart contracts deployed on the TON blockchain. This metric provides insight into developer activity and ecosystem growth by tracking when new contracts are created. The calculation uses a simple aggregation approach that counts distinct contract deployments per day based on contract creation timestamps.

## 2. Data sources

The metric relies on the following raw data sources:

- **TON blockchain contract records**: Core dataset containing information about all contracts deployed on the TON network, including creation timestamps and contract addresses
- **Contract deployment events**: Blockchain events that capture when new contracts are successfully deployed to the TON network
- **TON transaction data**: Underlying transaction records that contain contract creation activities

## 3. Step-by-step calculation

### Component A: Contract creation data extraction
- **Purpose**: Identifies and extracts all contract deployment events from TON blockchain data
- **Logic**: Extracts contract creation records from TON blockchain data, selecting the `creation_timestamp` and `contract_address` fields. Applies deduplication using DISTINCT to ensure each contract deployment is counted only once, preventing any potential double-counting from data processing
- **Key fields**: `creation_timestamp` provides the exact time when each contract was deployed, `contract_address` serves as the unique identifier for each deployed contract

### Component B: Daily aggregation
- **Purpose**: Groups contract deployments by day and counts the total deployments per day
- **Logic**: Truncates contract creation timestamps to day boundaries to group all deployments within each 24-hour period. Counts all contract deployments for each day using a simple count aggregation. Assigns standard metadata fields including chain identifier as TON, market sector as layer-1 blockchains, and business segment as blockchain
- **Key fields**: `timestamp` represents the day boundary, `contracts_deployed` contains the daily count of new contract deployments

### Final aggregation
- **Combining components**: The daily aggregation directly produces the final metric values without requiring additional combination steps
- **Currency conversion**: Not applicable for this count-based metric
- **Time aggregation**: Uses day-level boundaries with timestamp truncation to ensure consistent daily reporting periods
- **Final calculation**: The final metric value represents the total number of unique contracts deployed on the TON blockchain for each day, calculated as a simple count of contract creation events grouped by day with deduplication applied to prevent double-counting

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

Unique smart contracts published onchain.

TONGRAM

Contracts deployed

Contracts deployed

Competitive landscape