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 Token holders Methodology

## 1. Overview

The TON tokenholders metric counts the number of unique addresses holding native TON tokens on a daily basis. This metric answers the question "How many distinct wallet addresses currently hold TON tokens?" and provides insight into the distribution and adoption of the native TON cryptocurrency. The calculation identifies all addresses with non-zero TON balances and aggregates them into daily counts.

## 2. Data sources

- **TON blockchain balance data**: Native TON token balance information for all addresses on the TON network
- **TON blockchain transaction traces**: Transaction data used to track balance changes and identify active addresses
- **Token metadata**: Native TON token specifications including decimal precision and contract details
- **Daily balance snapshots**: Aggregated balance data organized by daily time periods for consistent tokenholder counting

## 3. Step-by-step calculation

### Component A: Native TON tokenholder identification
- **Purpose**: Identifies all unique addresses holding native TON tokens and counts them by day
- **Logic**: The system processes TON blockchain balance data to identify addresses with non-zero native TON token holdings. For each daily time period, it counts the number of distinct addresses that hold any amount of native TON tokens. The calculation filters out addresses with zero balances and aggregates the unique address count by daily timestamp boundaries.
- **Key fields**: `timestamp` (daily boundary), `timestamp_grain` (aggregation level), `chain` (TON network identifier), `tokenholders` (count of unique addresses)

### Component B: Metric standardization  
- **Purpose**: Applies standard formatting and metadata enrichment to the tokenholder counts
- **Logic**: The `finalize_metric_tokenholders` macro standardizes the tokenholder data by adding consistent metadata fields, ensuring proper data types, and applying Token Terminal's standard metric formatting. This includes setting the data identifier as 'ton' and ensuring consistent field naming and structure across all tokenholder metrics.
- **Key fields**: Standard metadata fields added through the finalization process, data identifier set to 'ton'

### Final aggregation
- **Combining components**: The native tokenholder counts are processed through the standardization macro to produce the final metric values
- **Currency conversion**: Not applicable - this is a count metric, not a monetary value
- **Time aggregation**: Daily aggregation boundaries are maintained, with each day representing the count of unique tokenholders at that point in time
- **Final calculation**: The final `tokenholders` value represents the total count of unique addresses holding non-zero amounts of native TON tokens for each daily time period, cast as a high-precision numeric value to handle large tokenholder counts accurately

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

Unique addresses holding a non-zero balance of the project's native token.

TONGRAM

Token holders

Token holders

Competitive landscape