Liquidity providers deposit funds into Zyberswap and receive trading fees from traders (supply-side fees).

Zyberswap is a non-custodial exchange protocol built on Arbitrum. Zyberswap was founded by anonymous team and launched in 2023.

ZYB tokenholders own and govern the protocol. They currently take a cut of the total trading fees paid by traders (revenue).

twitter

discord

etherscan

website

Exchanges (DEX)

Zyberswap

# Zyberswap Active users (daily) Methodology

## 1. Overview

Daily Active Users (DAU) for Zyberswap measures the number of distinct users who interact with the protocol each day through trading or flash loan activities. This metric counts unique wallet addresses that initiate transactions containing Zyberswap trading or flash loan events, providing insight into daily user engagement across both core trading functionality and advanced flash loan features. Users who perform multiple activities on the same day are counted only once.

## 2. Data sources

The calculation uses several types of blockchain data from the Arbitrum network:

- **Blockchain events**: Parsed Arbitrum event logs from Zyberswap smart contracts, including `Swap` events from both V2 and V3 protocols and `Flash` events from V3 protocols
- **Transaction data**: Arbitrum transaction records that provide the actual user addresses (`from_address`) who initiated the trading and flash loan activities
- **Contract events**: 
  - Zyberswap V2 `Pair_Swap_event` logs capturing traditional AMM swaps
  - Zyberswap V3 `AlgebraPool_Swap_event` logs capturing concentrated liquidity swaps  
  - Zyberswap V3 `AlgebraPool_Flash_event` logs capturing flash loan transactions
  - Zyberswap V2 `SwapFlashLoan_TokenSwap_event` logs capturing flash loan swaps

## 3. Step-by-step calculation

### Component A: Flash loan user extraction
- **Purpose**: Identifies users who executed flash loan transactions on Zyberswap
- **Logic**: Extracts user activity from two flash loan event types. For V3 protocols, queries `AlgebraPool_Flash_event` logs that contain flash loan parameters like `sender`, `amount0`, and `amount1`. For V2 protocols, queries `SwapFlashLoan_TokenSwap_event` logs that capture flash loan swaps with fields like `buyer`, `soldId`, `boughtId`, `tokensSold`, and `tokensBought`. Both event types are joined with Arbitrum transaction records to map contract-level events to actual user wallet addresses. Timestamps are truncated to daily granularity using day-level truncation
- **Key fields**: `user_address` extracted from transaction `from_address`, `block_timestamp` truncated to day level, `chain` set to arbitrum, `user_type` classified as Trader

### Component B: Trading user extraction  
- **Purpose**: Identifies users who executed swap transactions on Zyberswap
- **Logic**: Extracts user activity from swap events across both protocol versions. For V2, queries `Pair_Swap_event` logs and calculates net token flows by subtracting `amount0Out` from `amount0In` and `amount1Out` from `amount1In`. For V3, queries `AlgebraPool_Swap_event` logs that directly provide `amount0` and `amount1` values. Both swap types are joined with Arbitrum transaction records to extract the actual user addresses who initiated the swaps. Timestamps are truncated to daily granularity
- **Key fields**: `user_address` from transaction `from_address`, `block_timestamp` truncated to day level, calculated `token0_amount` and `token1_amount`, `chain` set to arbitrum

### Final aggregation
- **Combining components**: Flash loan users and trading users are combined using a union distinct operation, which automatically deduplicates users who perform both activities on the same day. This ensures each unique user address is counted only once per day regardless of activity type
- **Currency conversion**: No currency conversion is applied as this is a user count metric rather than a value-based metric
- **Time aggregation**: Daily boundaries are established through timestamp truncation to day level, with all activity within a 24-hour period aggregated to a single daily count
- **Final calculation**: The result is a dataset containing one record per unique user address per day, with each record representing one daily active user. The actual DAU count would be derived by counting distinct `user_address` values grouped by `timestamp` (day)

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

Unique revenue-generating users over a fixed 24-hour window.

ZyberswapZYB

Active users (daily)

Active users (daily)

Competitive landscape