Liquidity providers deposit funds into Ramses and stake their LP tokens to receive RAM tokens in proportion to their share of the votes (token incentives).

Ramses is a non-custodial exchange protocol built on Arbitrum. Ramses was founded by pseudonyms Dog and North in 2023.

RAM tokenholders own and govern the protocol. They vote which pools they wish to earn trading fees from (revenue).

github

twitter

discord

etherscan

website

Exchanges (DEX)

Ramses Exchange

# Ramses Exchange Tradeable pairs Methodology

## 1. Overview

The tradeable pairs metric measures the cumulative number of unique trading pairs created on the Ramses decentralized exchange (DEX) over time. This metric tracks the growth of available trading options on the platform by counting distinct pair addresses from both Ramses V1 (Legacy Pairs) and V2 (Concentrated Liquidity Pools) factory contracts. The metric answers the business question: "How many different token pairs can users trade on Ramses, and how has this grown over time?"

## 2. Data sources

The calculation relies on several key data sources:
- **Factory contract events**: Parsed `PairCreated` events from Ramses V1 factory contracts and `PoolCreated` events from Ramses V2 factory contracts on Arbitrum
- **Token metadata**: Token information including symbols and decimal precision for constructing human-readable pair names
- **Chain availability data**: Configuration data to ensure metric completeness across supported blockchain networks

## 3. Step-by-step calculation

### Component A: Pair creation event extraction
- **Purpose**: Identifies when new trading pairs are created on Ramses DEX
- **Logic**: Extracts distinct pair/pool creation events from Ramses factory contracts on Arbitrum. For V1, this captures `PairCreated` events containing the `pair` address, while V2 captures `PoolCreated` events containing the `pool` address. Each event includes the two token addresses (`token0` and `token1`) that form the trading pair, along with the block timestamp when the pair was created.
- **Key fields**: `account_address` (the pair/pool contract address), `token0_address`, `token1_address`, `block_timestamp`, `product_id` (Legacy Pair or Concentrated Liquidity Pool), `version` (v1 or v2), and `chain`

### Component B: Token metadata enrichment
- **Purpose**: Adds human-readable information to the raw pair data
- **Logic**: Joins the pair creation events with token metadata to retrieve symbol and decimal information for both tokens in each pair. Creates a readable pair name by concatenating the two token symbols with a hyphen separator. This enrichment allows for better identification and tracking of specific trading pairs.
- **Key fields**: `token0_decimals`, `token1_decimals`, `account_name` (formatted as "TOKEN0-TOKEN1")

### Component C: Daily aggregation and first appearances
- **Purpose**: Groups pair creation events by day and identifies new pairs
- **Logic**: Truncates block timestamps to daily boundaries and identifies the first appearance date for each unique pair address. Groups these first appearances by day and chain, counting how many new pairs were created each day. This ensures each pair is only counted once, on the day it was first created.
- **Key fields**: `timestamp` (daily), `pair_count` (new pairs created that day)

### Component D: Time series gap filling
- **Purpose**: Ensures complete daily time series with no missing dates
- **Logic**: Applies gap-filling logic to insert missing dates with zero new pair counts. This creates a continuous daily time series from the first pair creation to the present, ensuring that days with no new pairs are represented as zero rather than missing data points.
- **Key fields**: `pair_count` (filled with zeros for missing days)

### Final aggregation
- **Combining components**: The daily new pair counts are processed through a cumulative sum calculation
- **Time aggregation**: Daily boundaries are maintained throughout the calculation, with all timestamps truncated to day precision
- **Final calculation**: A running sum is calculated over the daily new pair counts, partitioned by chain and ordered by timestamp. This produces the cumulative number of tradeable pairs available on each day. The result represents the total number of unique trading pairs that have been created on Ramses DEX from inception through each given date.
- **Output formatting**: The final result applies standardized metric formatting through the `finalize_metric_tradeable_pairs` macro, which adds required schema fields, validates identifiers, and applies chain availability filtering to ensure data completeness.

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

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

Ramses ExchangeRAM

Tradeable pairs

Tradeable pairs

Competitive landscape

Chain breakdown