# Active users (weekly) Methodology

## 1. Overview

Active users (weekly) measures the number of unique addresses that perform revenue-generating interactions with the Shadow Concentrated Liquidity product. This metric captures engagement from participants who execute trades or utilize flash loan functionality within Concentrated Liquidity pools. All activity is measured over a 7-day rolling window to provide a consistent weekly view of protocol usage.

## 2. Data sources

- **Blockchain events**: `Swap` and `Flash` events from `Pool` contracts, covering Sonic
- **Blockchain data**: Transaction metadata including transaction signers from Sonic

## 3. Step-by-step calculation

### Component A: Concentrated Liquidity trading

- **Purpose**: Identifies unique users participating in swap activities.
- **Logic**: `Swap` events are parsed from `Pool` contracts associated with the Concentrated Liquidity product. These events are linked to the underlying blockchain transactions to retrieve the transaction originator address. Data is filtered to ensure only events from relevant contract versions are processed.
- **Key fields**: `transaction_hash`, `from_address` (transaction signer), `block_timestamp`

### Component B: Concentrated Liquidity flash loans

- **Purpose**: Identifies unique users utilizing flash loan services.
- **Logic**: `Flash` events are extracted from `Pool` contracts. Each event is associated with its corresponding transaction to identify the unique address that initiated the flash loan. This ensures that the user responsible for the transaction is captured rather than the contract-level sender.
- **Key fields**: `transaction_hash`, `from_address` (transaction signer), `block_timestamp`

### Component C: Aggregation and de-duplication

- **Purpose**: Combines activity from all sources into a single weekly count of unique users.
- **Logic**: The addresses identified from both trading and flash loan activities are combined into a single dataset. A de-duplication process is applied to ensure each unique address is counted only once per 7-day window, regardless of the number of transactions or interaction types performed. Values are truncated to weekly granularity using UTC boundaries. Chain availability filters are applied to ensure data is only reported for periods where comprehensive event data is available.
- **Key fields**: `user_address`, `block_timestamp`, `chain`

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

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

Active users (weekly)