The protocol routes trades through Uniswap V4 and 0x Protocol, collecting a 1% fee on each transaction.

o1.exchange enables users to trade tokens on Base with features including limit orders, TWAP, sniping, and anti-MEV protection.

o1.exchange is an AI-powered trading terminal built on Base.

website

twitter

discord

Exchanges (DEX)

o1.exchange

# o1 exchange Revenue Methodology

## 1. Overview

Revenue measures the total fees retained by o1 exchange, a DEX aggregator operating on Base that routes trades through Uniswap V4 and 0x Protocol. The protocol collects a 1% fee per trade, which is captured in two fee vault contracts and fully retained as protocol revenue. Fees are collected in both ERC-20 tokens and native ETH, then converted to USD for reporting.

## 2. Data sources

- **Blockchain events**: ERC-20 token transfers to two fee vault addresses (0xc98218df72975ee1472919d2685e5bd215baaad4 and 0x1e493e7cf969fd7607a8ace7198f6c02e5ef85a4) and native ETH flows to the same addresses, covering Base
- **External data**: End-of-day price feeds for collected fee assets, token decimal metadata

## 3. Step-by-step calculation

### Component A: ERC-20 fee collection

- **Purpose**: Capture token-denominated fees flowing into protocol vaults
- **Logic**: ERC-20 token transfers are identified where the recipient address matches either of the two fee vault addresses and the sender is not a fee vault (excluding vault-to-vault transfers). The transfer amount is extracted and tagged with the token address for subsequent price conversion.
- **Key fields**: `from_address` (payer identification), `to_address` (vault identification), `value` (fee amount), `token_address` (asset identification)

### Component B: Native ETH fee collection

- **Purpose**: Capture ETH-denominated fees flowing into protocol vaults
- **Logic**: Native ETH flows are identified where the recipient account matches either fee vault address and the value is positive. ETH amounts are represented using the wrapped ETH token address for price lookup consistency.
- **Key fields**: `account_address` (vault identification), `value` (fee amount)

### Component C: USD conversion and aggregation

- **Purpose**: Normalize all fee collections to USD and aggregate to daily granularity
- **Logic**: Token amounts are normalized by decimal precision and multiplied by end-of-day asset prices. ERC-20 and native ETH fees are combined and summed by day, with all collected fees classified as protocol revenue. Daily granularity with UTC day boundaries.

*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.

o1.exchange

Revenue

Revenue

Competitive landscape

Chain breakdown