Mantra is a Decentralized Exchange (DEX), initially built on Ethereum and upgraded to the Mantra Chain, a blockchain built on the Cosmos SDK.

website

twitter

discord

github

Blockchains (L1)

MANTRA

# MANTRA Tradeable pairs Methodology

## 1. Overview

The tradeable pairs metric measures the total number of distinct liquidity pools (trading pairs) available on Mantra Zone on any given day. This metric tracks the cumulative growth of trading pairs by identifying when new pools first appear and maintaining a count of all pools that have ever been active, providing insight into the platform's liquidity diversity and market expansion over time.

## 2. Data sources

- **Mantra blockchain message events**: Raw blockchain event logs from the Mantra network containing transaction and contract execution data
- **WASM contract events**: Parsed events from smart contract executions on the Mantra blockchain, specifically from the Mantra Zone decentralized exchange contract
- **Swap execution events**: Detailed swap transaction events containing pool identifiers, reserve amounts, token addresses, and trading activity data

## 3. Step-by-step calculation

### Component A: Swap event extraction
- **Purpose**: Extract and parse swap events from the Mantra Zone contract to identify active liquidity pools and their characteristics
- **Logic**: Filter Mantra blockchain message events for WASM contract events originating from the specific Mantra Zone contract address `mantra1466nf3zuxpya8q9emxukd7vftaf6h4psr0a07srl5zw74zh84yjqagspfm` with action type `execute_swap_operations`. Parse JSON event attributes using regex patterns to extract structured data including pool identifiers, reserve amounts for both tokens in each pair, token addresses, swap amounts, and fee information
- **Key fields**: `pool_identifier` uniquely identifies each trading pair, `pool_reserves` contains reserve amounts and token addresses, `swap` contains trade execution details, `block_timestamp` and `block_height` provide timing and ordering information

### Component B: Daily pool reserves snapshots  
- **Purpose**: Create end-of-day snapshots of pool reserves to track which pools are active and maintain historical state
- **Logic**: Group swap events by day and pool identifier, then select the latest reserves state for each pool on each day using block height and event index for precise ordering. Unpivot the token pair data so each token in a pool becomes a separate record, creating individual entries for token0 and token1 reserves within each pool
- **Key fields**: `timestamp` truncated to daily boundaries, `pool_identifier` for unique pool identification, `token_address` and `reserve` amounts for each token in the pool

### Component C: Pool first appearance tracking
- **Purpose**: Determine when each liquidity pool first appeared on the platform to establish the baseline for continuous counting  
- **Logic**: Analyze all historical reserve snapshots to find the minimum timestamp when each pool identifier first appeared in the dataset, creating a registry of pool launch dates
- **Key fields**: `pool_identifier` and `first_appearance_date` marking when each pool became active

### Component D: Daily timestamp generation
- **Purpose**: Create a complete series of daily timestamps to ensure consistent metric reporting across all days
- **Logic**: Extract all distinct daily timestamps from the reserves data along with consistent metadata including timestamp grain, product identifier as 'Mantra Zone', and chain identifier as 'mantra'
- **Key fields**: `timestamp` for each day, `timestamp_grain` set to 'day', `product_id` and `chain_id` for identification

### Final aggregation
- **Combining components**: Cross join the daily timestamps with pool first appearances, filtering to include each pool only for dates on or after its first appearance date. This ensures that once a pool appears, it continues to be counted in subsequent days regardless of trading activity
- **Currency conversion**: Not applicable as this is a count metric rather than a monetary value
- **Time aggregation**: Data is aggregated to daily boundaries using timestamp truncation, with the metric representing the cumulative count of unique pools available each day
- **Final calculation**: Count the distinct number of pool identifiers for each day, timestamp grain, product, and chain combination. Apply the finalization macro to ensure proper schema structure, validate identifiers, and implement forward-filling for any missing days. The result represents the total number of tradeable pairs available on Mantra Zone each day

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

Number of unique token pairs available for trading on the exchange.

MANTRAMANTRA

Archived

Tradeable pairs

Tradeable pairs

Competitive landscape

Chain breakdown