twitter

website

github

Exchanges (DEX)

Sun Swap

# Sun Swap Trading volume Methodology

## 1. Overview

Trading volume measures the total value of trades executed on SUNSwap V1, SUNSwap V2, SUNSwap V3, and SUNSwap V4. Since trading fees are paid by users on their trades, this metric tends to correlate with the decentralized exchange's ability to generate fees and revenue. By analyzing trading volume across different protocol versions, the overall liquidity and trading activity of the platform can be assessed. The metric is calculated by valuing each swap transaction and converting the volume to USD.

## 2. Data sources

- **Blockchain events**: `NewExchange`, `TokenPurchase`, and `TrxPurchase` events from `Factory` and `Exchange` contracts for SUNSwap V1; `PairCreated` and `Swap` events from `Factory` and `Pair` contracts for SUNSwap V2; `PoolCreated` and `Swap` events from `Factory` and `Pool` contracts for SUNSwap V3; and `Initialize` and `Swap` events from `PoolManager` contracts for SUNSwap V4, covering the Tron blockchain
- **External data**: End-of-day price feeds and asset metadata

## 3. Step-by-step calculation

### Component A: SUNSwap V1 trade extraction

- **Purpose**: Extract swap amounts from SUNSwap V1 contracts
- **Logic**: `TokenPurchase` and `TrxPurchase` events are parsed from `Exchange` contracts. For `TokenPurchase` events, the TRX sold is mapped to the first asset amount, and the tokens bought (represented as a negative value) are mapped to the second asset amount. For `TrxPurchase` events, the TRX bought (represented as a negative value) is mapped to the first asset amount, and the tokens sold are mapped to the second asset amount.
- **Key fields**: `trx_sold`, `tokens_bought`, `trx_bought`, and `tokens_sold`

### Component B: SUNSwap V2 trade extraction

- **Purpose**: Extract swap amounts from SUNSwap V2 contracts
- **Logic**: `Swap` events are parsed from `Pair` contracts. The net asset amounts are calculated by subtracting the outgoing asset amount from the incoming asset amount for both assets in the pool (asset 0 and asset 1).
- **Key fields**: `amount0In`, `amount0Out`, `amount1In`, and `amount1Out`

### Component C: SUNSwap V3 trade extraction

- **Purpose**: Extract swap amounts from SUNSwap V3 contracts
- **Logic**: `Swap` events are parsed from `Pool` contracts. The signed delta amounts for both assets in the pool are extracted directly from the event parameters.
- **Key fields**: `amount0` and `amount1`

### Component D: SUNSwap V4 trade extraction

- **Purpose**: Extract swap amounts from SUNSwap V4 contracts
- **Logic**: `Swap` events are parsed from `PoolManager` contracts. The asset amounts are extracted and negated to represent the trade direction.
- **Key fields**: `amount0` and `amount1`

### Component E: Asset normalization and USD conversion

- **Purpose**: Normalize asset quantities and convert trade values to USD
- **Logic**: Raw asset amounts are normalized by their respective decimal precision. Normalized amounts are multiplied by end-of-day price feeds to determine the USD value of each trade leg. To prevent distortion from unpriced or illiquid assets, the trade is valued at the lesser of the two legs. However, if exactly one leg consists of a tokenized stock asset, the trade is valued solely on that tokenized stock leg. Daily trading volumes are aggregated by pool and product using UTC day boundaries.
- **Key fields**: `token0_decimals` and `token1_decimals`

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

Total value of spot trades executed on the exchange.

Sun Swap

Trading volume

Trading volume

Competitive landscape