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 Active users (daily) Methodology

## 1. Overview

Daily Active Users (DAU) for the TON blockchain measures the number of unique user addresses that initiated at least one transaction on a given day. This metric identifies legitimate user activity by filtering transactions to only include those sent from recognized TON wallet contracts, ensuring the count reflects genuine user engagement rather than automated or system-generated activity.

## 2. Data sources

- **TON blockchain transaction records**: Complete transaction history including sender addresses, timestamps, and account state information
- **Wallet contract specifications**: Curated list of known TON wallet contract code hashes from official documentation and community sources, covering standard wallet versions (V1R1 through V5R1), beta versions, and specialized wallets (Lockup, Highload variants)

## 3. Step-by-step calculation

### Component A: Wallet type identification
- **Purpose**: Define which contract types constitute legitimate user wallets
- **Logic**: Maintain a reference mapping of known wallet contract code hashes to wallet types. This includes standard TON wallet versions from V1R1 through V5R1, beta versions like V5 Beta, and specialized wallet types including Lockup wallets and Highload variants (V1R1, V1R2, V2R1, V2R2). Code hashes are stored in both hexadecimal and base64 formats for matching against blockchain data.
- **Key fields**: `code_hash_hex` (original hexadecimal format), `code_hash_base64` (converted for blockchain matching), `account_type` (wallet version identifier)

### Component B: User transaction identification  
- **Purpose**: Extract all transactions sent by legitimate user wallets
- **Logic**: Join TON blockchain transaction records with the known wallet types reference table. Match transactions where the sender account's code hash corresponds to a recognized wallet type. Filter to only root-level transactions by requiring `transaction_hash` equals `trace_id`, which excludes internal transaction traces and ensures each user action is counted once. Each qualifying transaction captures the sender address as the active user.
- **Key fields**: `block_timestamp` (transaction timing), `account` (sender address), `account_state_code_hash_after` (wallet contract identifier), `transaction_hash` and `trace_id` (for root transaction filtering)

### Final aggregation
- **Combining components**: User transactions are aggregated by truncating `block_timestamp` to day boundaries using timestamp truncation
- **Time aggregation**: Daily boundaries are established by truncating timestamps to day granularity, ensuring consistent 24-hour periods
- **Final calculation**: Count distinct user addresses (`user_address`) for each day, where each unique address that sent at least one transaction from a recognized wallet type is counted as one daily active user. The metric includes metadata for chain identifier ('ton'), user type classification ('Transaction sender'), and timestamp grain ('day') for downstream analysis and reporting.

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

Unique revenue-generating users over a fixed 24-hour window.

TONGRAM

Active users (daily)

Active users (daily)

Competitive landscape