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 Supply-side fees Methodology

## 1. Overview

Supply-side fees represent the portion of trading fees that flows to liquidity providers in the Ramses DEX ecosystem. This metric calculates the daily USD value of fees earned by liquidity providers across both Ramses v1 (legacy pairs) and v2 (concentrated liquidity pools) on Arbitrum. The calculation applies different supply-side fee shares based on the protocol version: v1 has 0% supply-side fees (all fees go to the protocol), while v2 allocates 20% of total fees to liquidity providers.

## 2. Data sources

- **Arbitrum event logs**: Parsed `Claim` events from Ramses v1 `LegacyPair` contracts and `FeesCollected` events from Ramses v2 `FeeCollector` contracts
- **Factory creation events**: `PairCreated` events from Ramses v1 factory contracts and `PoolCreated` events from Ramses v2 factory contracts on Arbitrum
- **End-of-day price feeds**: Daily USD price data for all tokens involved in trading pairs
- **Token metadata**: Token decimals and symbols for proper amount calculation and pair naming

## 3. Step-by-step calculation

### Component A: V1 fee collection data
- **Purpose**: Extract fee claim events from Ramses v1 legacy pairs
- **Logic**: Parse `Claim` events from `LegacyPair` contracts on Arbitrum. Each event contains the claiming address (`sender`), trading pair contract address, and fee amounts in both tokens (`amount0` and `amount1`). All v1 fees are considered protocol fees with no supply-side allocation.
- **Key fields**: `sender` (fee collector), `amount0` and `amount1` (raw token amounts), contract address (trading pair)

### Component B: V2 fee collection data  
- **Purpose**: Extract fee collection events from Ramses v2 concentrated liquidity pools
- **Logic**: Parse `FeesCollected` events from `FeeCollector` contracts on Arbitrum. Each event contains fee distribution amounts (`feeDistAmount0`, `feeDistAmount1`) and treasury amounts (`treasuryAmount0`, `treasuryAmount1`) for both tokens. The total collected fees are calculated by summing the fee distribution and treasury amounts for each token.
- **Key fields**: `pool` (trading pair address), `feeDistAmount0` + `treasuryAmount0` (total token0 fees), `feeDistAmount1` + `treasuryAmount1` (total token1 fees)

### Component C: Trading pair metadata
- **Purpose**: Enrich fee data with token information and trading pair details
- **Logic**: Join fee collection events with factory creation data to identify token addresses, decimals, and symbols. V1 pairs come from `PairCreated` events while v2 pools come from `PoolCreated` events. This provides the token0 and token1 addresses, their decimal precision, and creates readable pair names by concatenating token symbols.
- **Key fields**: `token0` and `token1` addresses, `decimals` for each token, constructed `account_name` from token symbols

### Component D: Fee amount standardization
- **Purpose**: Convert raw token amounts to decimal-corrected values and aggregate by day
- **Logic**: Truncate block timestamps to daily boundaries. Correct token amounts by dividing raw values by 10 raised to the power of each token's decimal places. This converts from the smallest token units to standard token amounts.
- **Key fields**: Daily `timestamp`, corrected `token0_amount` and `token1_amount`

### Component E: USD conversion
- **Purpose**: Convert token amounts to USD values using daily price feeds
- **Logic**: Join the decimal-corrected amounts with end-of-day price feeds for both tokens in each trading pair. Multiply each token amount by its corresponding USD price. Sum the USD values of both tokens to get the total fee value per trading pair per day.
- **Key fields**: `price_usd` for each token, calculated total `fees` in USD

### Final aggregation
- **Combining components**: All fee data from v1 and v2 is combined into a single dataset with version labels
- **Currency conversion**: Token amounts are multiplied by end-of-day USD prices and summed across both tokens in each pair
- **Time aggregation**: All data is aggregated to daily boundaries using timestamp truncation
- **Final calculation**: Supply-side fees are calculated by applying version-specific multipliers: v1 fees are multiplied by 0 (0% supply-side share), while v2 fees are multiplied by 0.2 (20% supply-side share). The result represents the daily USD value of fees flowing to liquidity providers across the Ramses ecosystem.

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

Portion of fees distributed to service providers or supply-side participants.

Ramses ExchangeRAM

Supply-side fees

Supply-side fees

Competitive landscape

Chain breakdown