# SUNSwap V3 Trade count Methodology

## 1. Overview

Trade count is defined as the number of trades executed on SUNSwap V3. This metric is used to indicate how frequently assets are swapped through the protocol's concentrated liquidity pools. Each individual swap event emitted by a pool contract is counted as a single trade, meaning multi-hop swaps routing through multiple pools are counted as multiple trades. Insight into the overall transaction activity and liquidity utilization of SUNSwap V3 is provided by this metric.

## 2. Data sources

- **Blockchain events**: `Swap` events from `Pool` contracts, covering Tron

## 3. Step-by-step calculation

### Component A: Swap event extraction

- **Purpose**: Extract individual swap transactions executed on SUNSwap V3
- **Logic**: `Swap` events from `Pool` contracts on Tron are parsed and joined with native transaction data. For each event, the transaction hash, block timestamp, log index, pool address, and sender address are extracted. The swap amounts for both assets in the pool are captured as `amount0` and `amount1` by casting the raw event parameters to numeric values. Only events occurring on or after June 20, 2023, are included to align with the launch of SUNSwap V3.
- **Key fields**: `block_timestamp`, `transaction_hash`, `log_index`, `amount0`, `amount1`

### Component B: Trade aggregation

- **Purpose**: Aggregate the total number of trades on a daily basis
- **Logic**: The extracted swap events are grouped by day, chain, and product ID. A simple count of all records is performed to determine the daily trade count. Multi-hop swaps that route through multiple pools emit multiple events and are consequently counted as multiple trades.
- **Key fields**: `block_timestamp`, `product_id`, `chain_id`

### Component C: Finalization and zero-filling

- **Purpose**: Ensure data continuity and schema consistency
- **Logic**: The aggregated daily trade counts are processed to ensure correct data types and valid chain identifiers. A zero-filling strategy is applied to insert a value of zero for any days where no trading activity is recorded. Finally, a chain availability filter is applied to align the output with the active status of the underlying blockchain.
- **Key fields**: `timestamp`, `trade_count`

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

Number of trades executed on a decentralized exchange.

Trade count