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 Active users (daily) Methodology

## 1. Overview

Active users (daily) measures the number of unique addresses that execute revenue-generating transactions through o1 exchange on a given day. A user is counted as active when their transaction results in fee payments to o1 exchange's fee vault addresses, indicating meaningful platform usage. This metric captures trader activity across o1 exchange's DEX aggregation services.

## 2. Data sources

- **Blockchain data**: Token transfers to fee recipient addresses and transaction metadata, covering Base
- **Fee vault addresses**: Two designated fee collection addresses that receive protocol fees from trading activity

## 3. Step-by-step calculation

### Component A: Fee transaction identification

- **Purpose**: Identify transactions that generated protocol fees
- **Logic**: Token transfers are filtered to identify payments directed to o1 exchange's two fee vault addresses. Transfers are excluded when the sender matches either fee vault address to avoid counting internal movements. Each qualifying transfer's transaction hash is captured as a revenue-generating transaction.
- **Key fields**: `transaction_hash` (transaction identification), `to_address` (recipient validation), `from_address` (sender validation)

### Component B: User address extraction

- **Purpose**: Map fee transactions to the originating user addresses
- **Logic**: Transaction metadata is joined to fee transactions using transaction hash. The transaction signer is extracted from the `from_address` field, representing the user who initiated the trading activity. Each unique signer address represents one active user.
- **Key fields**: `from_address` (user identification), `block_timestamp` (temporal assignment)

### Component C: Daily aggregation

- **Purpose**: Count unique users per day
- **Logic**: User addresses are deduplicated within each UTC calendar day using timestamp truncation to day granularity. Each unique address is counted once per day regardless of transaction frequency.

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

Unique revenue-generating users over a fixed 24-hour window.

o1.exchange

Active users (daily)

Active users (daily)

Competitive landscape

Chain breakdown