Liquidity providers deposit funds into Osmosis and receive trading fees from traders (supply-side fees).

Osmosis is a non-custodial exchange protocol built on Cosmos ecosystem. Osmosis was launched in June 2021.

OSMO token holders own and govern the protocol. They currently do not take a cut of the total trading fees paid by traders (revenue).

governance

github

twitter

discord

etherscan

website

Exchanges (DEX)

Osmosis

# Osmosis Revenue Methodology

## 1. Overview

This metric tracks protocol revenue for the Osmosis decentralized exchange. Osmosis is an automated market maker (AMM) on the Cosmos ecosystem. The revenue metric specifically measures the portion of trading fees that the protocol retains as revenue. Based on the implementation, Osmosis appears to follow a model where all trading fees are distributed to liquidity providers and validators, with no fees retained as protocol revenue, resulting in zero protocol revenue.

## 2. Data sources

The calculation relies on:
- **Osmosis fee collection data**: Aggregated fee information collected from the Osmosis blockchain, containing total fees spent in trading activities
- **Business classification data**: Protocol categorization information identifying Osmosis as an Exchange AMM in the dex segment
- **Time series infrastructure**: Daily timestamp boundaries and data validation systems

## 3. Step-by-step calculation

### Component A: Fee data collection
- **Purpose**: Extracts raw fee data from Osmosis blockchain and applies business classification
- **Logic**: Retrieves fee collection records from Osmosis scraper data, which aggregates fee information from blockchain transactions. Each record is classified as belonging to the Exchange AMM business line within the dex segment. The `fees_spent` field represents the total fees collected from trading activities on a daily basis.
- **Key fields**: `timestamp` for daily boundaries, `fees_spent` as the raw fee amount, business classification fields including `chain`, `business_line`, and `market_sector_id`

### Component B: Fee metric standardization  
- **Purpose**: Processes fee data through standardization and validation
- **Logic**: Takes the classified fee data and applies the fee metric finalization process, which ensures consistent schema structure, validates data quality, and fills any gaps in the time series with zero values. This creates a complete daily time series of fee collection data.
- **Key fields**: `fees` as the processed fee amount, standardized `timestamp` and `timestamp_grain`, validated `chain_id` and `product_id`

### Component C: Revenue calculation
- **Purpose**: Determines protocol revenue from the fee data
- **Logic**: References the processed fee data but explicitly sets the revenue amount to zero for all records. This indicates that Osmosis follows a business model where trading fees are not retained as protocol revenue but are instead distributed to other parties such as liquidity providers and validators.
- **Key fields**: `revenue` field set to 0, maintaining all other dimensional fields from the fee data

### Final aggregation
- **Combining components**: The revenue metric inherits the time series structure and dimensional attributes from the underlying fee data while setting revenue amounts to zero
- **Currency conversion**: No currency conversion is applied as the revenue amount is zero
- **Time aggregation**: Data is aggregated at daily boundaries with complete time series maintained through gap-filling
- **Final calculation**: The final revenue value is consistently 0 for all time periods, reflecting Osmosis's fee distribution model where no fees are retained as protocol revenue. Results are filtered to include only data through June 20, 2024.

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

fees * take_rate (illustrative — revenue is observed directly per project, not derived from take_rate)

Fee revenue retained after supply-side payouts. Before cost of revenue (e.g. L2 DA fees) and before operating expenses.

OsmosisOSMO

Archived

Revenue

Revenue

Competitive landscape