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 Tradeable assets Methodology

## 1. Overview

The tradeable assets metric measures the cumulative number of unique tokens that can be traded on Zyberswap over time. This metric tracks the growth of the platform's token ecosystem by counting each new token as it becomes tradeable through the creation of trading pairs or liquidity pools. The calculation identifies when new tokens first appear in trading pairs and maintains a running count of total tradeable assets.

## 2. Data sources

- **Zyberswap V2 contract events**: Parsed `SwapDeployer_NewSwapPool_event` events from Arbitrum capturing multi-token liquidity pool deployments
- **Zyberswap V2 contract events**: Parsed `Factory_PairCreated_event` events from Arbitrum capturing standard trading pair creation
- **Zyberswap V3 contract events**: Parsed `AlgebraFactory_Pool_event` events from Arbitrum capturing V3 pool deployments
- **Token metadata**: Token symbols and decimal information for enriching trading pair data

## 3. Step-by-step calculation

### Component A: Trading pair extraction
- **Purpose**: Identifies all trading pairs and liquidity pools created on Zyberswap
- **Logic**: Extracts trading pairs from multiple contract event types across Zyberswap V2 and V3 on Arbitrum. For V2 `SwapDeployer_NewSwapPool_event` events, handles multi-token pools containing up to 3 tokens by creating all possible token pair combinations (e.g., if tokens A, B, C are in a pool, creates pairs A-B, A-C, B-C). Standard `Factory_PairCreated_event` and V3 `AlgebraFactory_Pool_event` events create single token pairs. Each trading pair record includes the deployment timestamp, contract address, and both token addresses with their metadata.
- **Key fields**: `block_timestamp` for when the pair was created, `account_address` for the trading pair contract, `token0_address` and `token1_address` for the tokens in the pair, token symbols and decimals from metadata

### Component B: Token address aggregation
- **Purpose**: Creates a comprehensive list of all unique tokens that have become tradeable
- **Logic**: Unions all token addresses from both sides of trading pairs (token0 and token1) to create a deduplicated list of token addresses. Each token is associated with the timestamp of its first appearance in any trading pair, which represents when it first became tradeable on the platform. The process truncates timestamps to daily boundaries for consistent aggregation.
- **Key fields**: `timestamp` truncated to day level, `chain` identifier, `token_address` for each unique token

### Component C: First appearance tracking
- **Purpose**: Determines when each token first became tradeable
- **Logic**: Groups token addresses by chain and finds the minimum timestamp when each token first appeared in any trading pair. This establishes the "birth date" for each tradeable asset on the platform.
- **Key fields**: Minimum `timestamp` for first appearance, `token_address` for unique identification

### Component D: Daily new assets counting
- **Purpose**: Counts how many new tokens became tradeable each day
- **Logic**: Groups first appearances by day and chain, then counts the approximate distinct number of new token addresses appearing on each date. This creates a daily time series of newly tradeable assets.
- **Key fields**: Daily `timestamp`, `asset_count` representing new tokens that day

### Component E: Gap filling
- **Purpose**: Ensures complete daily time series with no missing dates
- **Logic**: Applies gap filling logic to insert zero values for any missing days between the first and last appearance dates. This creates a continuous daily series where days with no new tokens show zero rather than being absent from the dataset.
- **Key fields**: Complete daily `timestamp` series, `asset_count` with zeros filled for missing days

### Final aggregation
- **Combining components**: The daily new asset counts are processed using a cumulative window function partitioned by chain and ordered by timestamp
- **Time aggregation**: Data is aggregated at daily boundaries with timestamps truncated to day level
- **Final calculation**: Calculates running sum of `asset_count` over time within each chain partition, resulting in the total cumulative number of unique tradeable assets available on Zyberswap at each point in time. The final metric represents the total ecosystem size of tradeable tokens on the platform.

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

Number of unique tokens tradeable on the exchange.

ZyberswapZYB

Tradeable assets

Tradeable assets

Competitive landscape