twitter

website

github

Exchanges (DEX)

Sun Swap

# Sun Swap Active users (weekly) Methodology

## 1. Overview

Active users (weekly) measures the number of unique addresses that make a revenue-generating transaction with a project, i.e. An application or a blockchain. Active users (weekly) are measured over a 7-day rolling window. For SUNSwap, this metric is calculated by identifying unique transaction senders who execute swaps across SUNSwap V1, SUNSwap V2, SUNSwap V3, and SUNSwap V4. User activity is analyzed to provide insights into protocol adoption and trading engagement.

## 2. Data sources

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

## 3. Step-by-step calculation

### Component A: SUNSwap V1 trade extraction

- **Purpose**: Extract swap transactions and user addresses from SUNSwap V1
- **Logic**: `TokenPurchase` and `TrxPurchase` events are parsed from `Exchange` contracts on the Tron blockchain. To identify the actual end-user, these events are joined with transaction-level data using the transaction hash. The transaction signer address is extracted from the transaction data and designated as the active user. This process ensures that intermediate router contracts are excluded from the user count.
- **Key fields**: `block_timestamp`, `transaction_hash`, `from_address`

### Component B: SUNSwap V2 trade extraction

- **Purpose**: Extract swap transactions and user addresses from SUNSwap V2
- **Logic**: `Swap` events are parsed from `Pair` contracts on the Tron blockchain. These events are joined with transaction-level data using the transaction hash to identify the transaction signer address. The transaction signer address is extracted and designated as the active user, ensuring that router contracts are not counted.
- **Key fields**: `block_timestamp`, `transaction_hash`, `from_address`

### Component C: SUNSwap V3 trade extraction

- **Purpose**: Extract swap transactions and user addresses from SUNSwap V3
- **Logic**: `Swap` events are parsed from `Pool` contracts on the Tron blockchain. These events are joined with transaction-level data using the transaction hash to identify the transaction signer address. The transaction signer address is extracted and designated as the active user, ensuring that only the end-user initiating the transaction is counted.
- **Key fields**: `block_timestamp`, `transaction_hash`, `from_address`

### Component D: SUNSwap V4 trade extraction

- **Purpose**: Extract swap transactions and user addresses from SUNSwap V4
- **Logic**: `Swap` events are parsed from `PoolManager` contracts on the Tron blockchain. These events are joined with transaction-level data using the transaction hash to identify the transaction signer address. The transaction signer address is extracted and designated as the active user, ensuring that only the end-user initiating the transaction is counted.
- **Key fields**: `block_timestamp`, `transaction_hash`, `from_address`

### Component E: Weekly active user aggregation

- **Purpose**: Aggregate unique user addresses per 7-day window
- **Logic**: The extracted transaction signer addresses from SUNSwap V1, SUNSwap V2, SUNSwap V3, and SUNSwap V4 are combined into a single dataset. The timestamps are analyzed using a 7-day rolling window. For each 7-day window, the number of unique transaction signer addresses is aggregated to calculate the active users (weekly) metric.
- **Key fields**: `block_timestamp`, `from_address`, `product_id`

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

Unique revenue-generating users over a rolling 7-day window.

Sun Swap

Active users (weekly)

Active users (weekly)

Competitive landscape