twitter

website

github

Exchanges (DEX)

Sun Swap

# Sun Swap Trade count Methodology

## 1. Overview

Trade count measures the number of trades executed on a decentralized exchange. It shows how frequently users are buying or selling assets through the project. For SUNSwap, trades are captured across SUNSwap V1, SUNSwap V2, SUNSwap V3, and SUNSwap V4. Each swap event emitted by a pool contract is counted as an individual trade, meaning multi-hop transactions routing through multiple pools are counted as multiple trades.

## 2. Data sources

- **Blockchain events**: `TokenPurchase` and `TrxPurchase` events from `Exchange` contracts, `Swap` events from `Pair` contracts, `Swap` events from `Pool` contracts, and `Swap` events from `PoolManager` contracts, covering Tron

## 3. Step-by-step calculation

### Component A: SUNSwap V1 trade extraction

- **Purpose**: Extraction of trade events from SUNSwap V1 contracts
- **Logic**: `TokenPurchase` and `TrxPurchase` events are parsed from `Exchange` contracts on Tron. These events are joined with native transaction data to identify the transaction sender. Only events occurring on or after August 14, 2020, are included.
- **Key fields**: `block_timestamp`, `transaction_hash`, `log_index`, `buyer` (contract user address), and transaction sender address

### Component B: SUNSwap V2 trade extraction

- **Purpose**: Extraction of trade events from SUNSwap V2 contracts
- **Logic**: `Swap` events are parsed from `Pair` contracts on Tron. These events are joined with native transaction data to identify the transaction sender. Only events occurring on or after December 14, 2021, are included.
- **Key fields**: `block_timestamp`, `transaction_hash`, `log_index`, `sender` (contract user address), and transaction sender address

### Component C: SUNSwap V3 trade extraction

- **Purpose**: Extraction of trade events from SUNSwap V3 contracts
- **Logic**: `Swap` events are parsed from `Pool` contracts on Tron. These events are joined with native transaction data to identify the transaction sender. Only events occurring on or after June 20, 2023, are included.
- **Key fields**: `block_timestamp`, `transaction_hash`, `log_index`, `sender` (contract user address), and transaction sender address

### Component D: SUNSwap V4 trade extraction

- **Purpose**: Extraction of trade events from SUNSwap V4 contracts
- **Logic**: `Swap` events are parsed from `PoolManager` contracts on Tron. These events are joined with native transaction data to identify the transaction sender. Only events occurring on or after December 29, 2025, are included.
- **Key fields**: `block_timestamp`, `transaction_hash`, `log_index`, `sender` (contract user address), and transaction sender address

### Component E: Aggregation and zero-filling

- **Purpose**: Aggregation of trade counts and application of zero-filling
- **Logic**: All extracted trade events from SUNSwap V1, SUNSwap V2, SUNSwap V3, and SUNSwap V4 are aggregated by day, chain, and product. The total number of trades is calculated by counting the unique occurrences of these events. Missing days in the time series are filled with zeros to ensure a continuous daily record.

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

Number of trades executed on a decentralized exchange.

Sun Swap

Trade count

Trade count

Competitive landscape