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

Thruster is a non-custodial exchange protocol built on Blast. Thruster was launched in 2024.

Thruster team and investors own and govern the protocol. They currently take a cut of the total trading fees paid by traders, and earn native yield (revenue). Thruster's investors include Mirana Ventures, Manifold, OKX Ventures, etc.

twitter

discord

website

Exchanges (DEX)

Thruster

# Thruster Active users (daily) Methodology

## 1. Overview

The Thruster daily active users (DAU) metric measures the number of unique addresses that interact with the Thruster protocol on any given day. This metric captures trading-related activity by counting users who perform either traditional AMM trades or flash loans. The calculation aggregates activity across Thruster's Classic AMM and CLAMM (concentrated liquidity) products on the Blast blockchain, providing a comprehensive view of daily protocol engagement.

## 2. Data sources

- **Blast blockchain transaction records**: Transaction data containing `from_address` fields that identify the actual users initiating transactions
- **Thruster flash loan events**: Parsed `Flash` event logs from Thruster v1 Pool contracts on Blast, containing flash loan parameters and contract addresses
- **Thruster Classic AMM swap events**: Parsed `Swap` event logs from Thruster v1 Pair contracts (Pair03 and Pair1) on Blast, containing traditional AMM swap data with `amount0In`, `amount0Out`, `amount1In`, `amount1Out` fields
- **Thruster CLAMM swap events**: Parsed `Swap` event logs from Thruster v1 Pool contracts on Blast for concentrated liquidity swaps, containing `amount0` and `amount1` fields

## 3. Step-by-step calculation

### Component A: Flash loan users
- **Purpose**: Identify users who performed flash loans on Thruster
- **Logic**: Extract all `Flash` events from Thruster v1 Pool contracts on the Blast network. Join these events with Blast transaction records using the `transaction_hash` to map from the contract `sender` address in the event to the actual `from_address` from the transaction record. This resolves the true user address that initiated the flash loan transaction. Apply daily timestamp truncation to group activity by day.
- **Key fields**: `block_timestamp` for timing, `transaction_hash` for joining, `sender` from the flash event, `from_address` from transaction data as the user identifier, `amount0` and `amount1` flash loan amounts

### Component B: Trading users
- **Logic**: Extract swap events from multiple Thruster contract types. For Classic AMM swaps, query `Swap` events from Pair03 and Pair1 contracts, calculating net token changes by subtracting `amount0Out` from `amount0In` and `amount1Out` from `amount1In`. For CLAMM swaps, query `Swap` events from Pool contracts using direct `amount0` and `amount1` values. Join all swap events with Blast transaction records to resolve the actual user addresses from transaction `from_address` fields. Distinguish between product types by assigning 'thrusterclassic' to Classic AMM trades and 'thrusterclamm' to CLAMM trades.
- **Key fields**: `block_timestamp` for timing, `transaction_hash` for joining, swap amount fields (`amount0In`, `amount0Out`, `amount1In`, `amount1Out` for Classic; `amount0`, `amount1` for CLAMM), `from_address` as the user identifier, `product_id` for product categorization

### Final aggregation
- **Combining components**: Union the flash loan users and trading users using UNION DISTINCT to eliminate duplicate users who performed both activities on the same day
- **Time aggregation**: Truncate all timestamps to day granularity using `timestamp_trunc(block_timestamp, day)` to create daily boundaries
- **User categorization**: Label all users as 'Trader' type since both flash loans and trades represent trading-related protocol interactions
- **Final calculation**: Count distinct user addresses per day across all activity types, with each unique address counted only once per day regardless of the number or types of transactions performed

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

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

ThrusterTHRUST

Archived

Active users (daily)

Active users (daily)

Competitive landscape