twitter

Infrastructure

RayBot

# RayBot Revenue Methodology

## 1. Overview

Revenue for Raybot represents the total fees collected by the protocol from user transactions, measured in USD on a daily basis. This metric tracks native SOL transfers to Raybot's designated fee collection address on Solana, providing insight into the protocol's fee-generating activity and overall revenue performance. The calculation converts raw SOL transfers into standardized daily USD revenue figures.

## 2. Data sources

- **Solana native transfers**: Native SOL transfer records on the Solana blockchain, specifically transfers directed to fee collection addresses
- **End-of-day price feeds**: SOL price data used for USD conversion of fee amounts
- **Token metadata**: Solana token information including the native SOL token address (`So11111111111111111111111111111111111111112`)

## 3. Step-by-step calculation

### Component A: Fee collection extraction
- **Purpose**: Identifies and extracts fee payments made to Raybot's fee collection system
- **Logic**: Filters Solana native transfer records for transfers sent to the designated Raybot fee collection address (`4mih95RmBqfHYvEfqq6uGGLp1Fr3gVS3VNSEa3JVRfQK`). Excludes self-transfers where the transaction signer is the same as the fee collection address to avoid internal movements. Captures the transfer `amount`, `block_timestamp`, `transaction_id`, and `transaction_signer` for each qualifying fee payment.
- **Key fields**: `block_timestamp` for timing, `amount` in lamports (native SOL units), `transaction_signer` to identify fee payers, `to_address` filtered to fee collection address

### Component B: Daily fee aggregation
- **Purpose**: Aggregates raw fee transfers into daily totals and converts units
- **Logic**: Groups fee transfers by day using timestamp truncation to daily boundaries. Converts amounts from lamports to SOL by dividing by 1e9 (1 billion lamports per SOL). Sums all fee amounts for each day, maintaining chain identifier as 'solana' and token address as the native SOL token address.
- **Key fields**: Daily `timestamp`, `chain_id` as 'solana', `token_address` as native SOL, aggregated `fees` in SOL units

### Component C: USD conversion
- **Purpose**: Converts daily SOL fee totals to USD values
- **Logic**: Uses end-of-day SOL price feeds to convert each day's SOL fee total to USD. The conversion applies current market rates without decimal correction since SOL amounts are already properly scaled. Maintains daily granularity and chain/token identifiers through the conversion process.
- **Key fields**: `fees` converted to USD values, `timestamp` maintained for daily boundaries, chain and token identifiers preserved

### Final aggregation
- **Combining components**: The fees data flows sequentially through extraction, daily aggregation, and USD conversion without additional joining
- **Currency conversion**: SOL amounts converted to USD using end-of-day price feeds, with amounts already properly scaled from lamports to SOL units
- **Time aggregation**: Data aggregated to daily boundaries using timestamp truncation, with zero-filling applied for missing days
- **Final calculation**: Revenue equals the daily sum of USD-converted fees collected by Raybot's fee collection address, with fees semantically relabeled as revenue in the final metric

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

RayBot

Revenue

Revenue

Competitive landscape