website

twitter

Infrastructure

BONKbot

# BONKbot Revenue Methodology

## 1. Overview

BonkBot revenue represents the total daily fee income generated by the BonkBot trading bot service on Solana. This metric captures all fee payments made to BonkBot's designated fee collection address, converted to USD. The calculation identifies revenue by tracking transfers to the bot's known fee collection address, including both native SOL payments and SPL token payments.

## 2. Data sources

- **Solana native transfers**: Native SOL transfer records on the Solana blockchain, specifically transfers directed to recipient addresses
- **Solana SPL token transfers**: SPL token transfer records on Solana, tracking transfers where tokens are moved to specific owner addresses
- **End-of-day token price feeds**: Daily closing prices for tokens to enable USD conversion
- **Token metadata**: Token configuration data including decimal precision information for accurate amount calculations

## 3. Step-by-step calculation

### Component A: SOL fee collection
- **Purpose**: Captures fees paid to BonkBot in native SOL
- **Logic**: Filters Solana native transfer records to identify transfers sent TO the BonkBot fee collection address `ZG98FUCjb8mJ824Gbs6RsgVmr1FhXb2oNiJHa2dwmPd`. Excludes any transfers where the transaction signer is the fee address itself to prevent counting internal transfers or withdrawals as revenue. Records the transfer `amount`, `block_timestamp`, `transaction_id`, and `transaction_signer` for each qualifying fee payment.
- **Key fields**: `block_timestamp` for timing, `amount` for fee value, `transaction_signer` to identify the fee payer, `token_address` set to SOL's canonical address

### Component B: SPL token fee collection  
- **Purpose**: Captures fees paid to BonkBot in SPL tokens
- **Logic**: Filters Solana SPL token transfer records to identify transfers where tokens are moved to accounts owned by the BonkBot fee collection address `ZG98FUCjb8mJ824Gbs6RsgVmr1FhXb2oNiJHa2dwmPd`. Excludes transfers where the transaction signer is the fee address itself to avoid double-counting internal operations. Records the token transfer `amount`, `token_address`, `block_timestamp`, and `transaction_signer` for each qualifying fee payment.
- **Key fields**: `block_timestamp` for timing, `amount` for fee value, `token_address` to identify the token type, `transaction_signer` to identify the fee payer

### Component C: Fee aggregation and conversion
- **Purpose**: Combines all fee types and converts to USD
- **Logic**: Unions the SOL and SPL token fee collections, then groups by day, chain, and token address to sum total daily fees per token type. Applies USD conversion using end-of-day token prices and corrects for token decimal precision to ensure accurate dollar amounts. Each token's fees are converted independently before being combined.
- **Key fields**: `timestamp` truncated to day boundaries, `fees` as the USD-converted amount, `token_address` for price lookup

### Final aggregation
- **Combining components**: All token-specific daily fee totals are summed together to create the total daily revenue figure
- **Currency conversion**: Uses end-of-day token prices to convert all fees to USD, with proper decimal adjustment based on each token's precision
- **Time aggregation**: Fees are aggregated by calendar day using timestamp truncation to day boundaries
- **Final calculation**: Revenue equals the sum of all USD-converted fees collected by the BonkBot service on each day, with gap filling applied to ensure complete daily time series

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

BONKbot

Revenue

Revenue

Competitive landscape