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 Fees Methodology

## 1. Overview

The Ramses fees metric measures the total daily trading fees collected across all Ramses exchange pools on Arbitrum, denominated in USD. This metric captures revenue generated from trading activities on both Ramses v1 (legacy pairs) and v2 (concentrated liquidity pools). The calculation aggregates fee collection events from both versions, applies proper decimal correction and USD conversion, then sums the total daily fee value across all trading pairs.

## 2. Data sources

The calculation relies on the following raw data sources:
- **Fee collection events**: Parsed `Claim` events from Ramses v1 legacy pair contracts and `FeesCollected` events from Ramses v2 fee collector contracts on Arbitrum
- **Factory events**: Parsed `PairCreated` events from Ramses v1 factory contract and `PoolCreated` events from Ramses v2 factory contract on Arbitrum
- **Token metadata**: Token reference data containing symbol names and decimal precision information
- **Price feeds**: End-of-day token price feeds providing USD conversion rates for all tokens

## 3. Step-by-step calculation

### Component A: Fee collection events extraction

- **Purpose**: Extract raw fee amounts from both Ramses v1 and v2 fee collection mechanisms
- **Logic**: 
  - For v1: Extract `Claim` events from legacy pair contracts, capturing `amount0` and `amount1` fields representing fees collected in each token of the pair
  - For v2: Extract `FeesCollected` events from fee collector contracts, summing `feeDistAmount` and `treasuryAmount` for each token to calculate total fees (since v2 splits fees between distribution and treasury)
  - Both event types capture the pool/pair address, fee collector address, and raw token amounts in blockchain units
- **Key fields**: `block_timestamp`, `account_address` (pool address), `token0_amount`, `token1_amount`, `fee_collector_address`

### Component B: Trading pair dimensional data

- **Purpose**: Map pool addresses to their underlying token pairs and obtain token metadata
- **Logic**: 
  - Extract pool creation events from factory contracts for both v1 (`PairCreated`) and v2 (`PoolCreated`) 
  - Join with token metadata to obtain token symbols, decimal places, and addresses for each token in every trading pair
  - Create readable pool names by concatenating token symbols (e.g., "ETH-USDC")
- **Key fields**: `account_address`, `token0_address`, `token1_address`, `token0_decimals`, `token1_decimals`, `account_name`

### Component C: Fee processing and normalization

- **Purpose**: Combine fee events with trading pair data and apply decimal correction
- **Logic**: 
  - Join fee collection events with trading pair dimensional data using pool addresses
  - Truncate timestamps to daily boundaries for aggregation
  - Apply decimal correction by dividing raw token amounts by 10 raised to the power of each token's decimal places
  - This converts blockchain units to human-readable token amounts
- **Key fields**: `timestamp` (daily), `chain`, `product_id`, `token0_amount` (corrected), `token1_amount` (corrected)

### Final aggregation

- **Combining components**: Fee events are joined with price feeds for both tokens in each pair using timestamp, token address, and chain
- **Currency conversion**: Each token amount is multiplied by its corresponding USD price from end-of-day price feeds, then both token values are summed to get total USD fee value per transaction
- **Time aggregation**: All fee transactions within each day are summed by pool address to get daily totals per trading pair
- **Final calculation**: The result is daily fee totals per pool, with standardized schema application including market sector classification (exchanges/dex) and gap filling with zeros for missing days

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

Total value users pay to use a protocol (gross fees, user-paid fees).

Ramses ExchangeRAM

Fees

Fees

Competitive landscape

Chain breakdown