website

twitter

Infrastructure

BONKbot

# BONKbot Fees Methodology

## 1. Overview

Bonkbot fees represents the total daily fee revenue collected by the Bonkbot trading bot protocol on Solana. The metric captures fees paid by users for trading services, calculated by aggregating all token transfers (both native SOL and SPL tokens) sent to Bonkbot's fee collection address. This metric answers the business question: "How much revenue does Bonkbot generate from trading fees on a daily basis?"

## 2. Data sources

The calculation relies on the following raw data sources:
- **Solana native token transfers**: Parsed Solana blockchain native SOL transfer events, specifically transfers directed to recipient addresses
- **Solana SPL token transfers**: Parsed Solana Program Library (SPL) token transfer events, tracking transfers to specific owner addresses
- **End-of-day token price feeds**: Daily closing prices for tokens to enable USD conversion
- **Token metadata**: Token information including decimal places for proper amount calculations

## 3. Step-by-step calculation

### Component A: SOL fee collection
- **Purpose**: Captures fees paid to Bonkbot in native SOL tokens
- **Logic**: Filters Solana native token transfer events for transfers sent TO Bonkbot's fee collection address `ZG98FUCjb8mJ824Gbs6RsgVmr1FhXb2oNiJHa2dwmPd`. Excludes any transfers where the transaction signer is the fee address itself to avoid counting internal transfers or self-transactions. Groups transfers by day and sums the `amount` values
- **Key fields**: Uses `block_timestamp` for daily grouping, `transaction_signer` for filtering, `to_address` for identifying Bonkbot fees, and `amount` for fee values. Sets `token_address` to the standard SOL token address `So11111111111111111111111111111111111111112`

### Component B: SPL token fee collection  
- **Purpose**: Captures fees paid to Bonkbot in various SPL tokens
- **Logic**: Filters Solana SPL token transfer events for transfers where the recipient owner address is Bonkbot's fee collection address. Similar to SOL fees, excludes transfers where the transaction signer matches the fee address to avoid self-transfers. Groups by day and individual token address, summing amounts for each token type
- **Key fields**: Uses `block_timestamp` for daily aggregation, `to_owner_address` to identify Bonkbot as recipient, `transaction_signer` for filtering, `token_address` to distinguish different SPL tokens, and `amount` for fee values

### Component C: Fee stream unification
- **Purpose**: Combines SOL and SPL token fees into a single dataset
- **Logic**: Unions the SOL fee data with SPL token fee data, creating a comprehensive view of all fees collected regardless of token type. Both streams are aggregated to daily grain with consistent schema including timestamp, chain identifier, and token-specific amounts

### Final aggregation
- **Combining components**: The unified fee data undergoes USD conversion and decimal correction using end-of-day token prices. Each token amount is converted to USD equivalent and adjusted for the token's decimal places to ensure accurate value representation
- **Currency conversion**: Applies end-of-day price feeds to convert all token amounts to USD, ensuring consistent valuation across different tokens (SOL, USDC, BONK, etc.)
- **Time aggregation**: Data is truncated to daily boundaries using the `block_timestamp`, with all fees within a calendar day summed together
- **Final calculation**: The metric represents the total USD value of all fees collected by Bonkbot on each day, with missing days filled with zero values to maintain continuity. Chain availability filtering ensures data completeness before final output

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

Total value users pay to use a protocol (gross fees, user-paid fees).

BONKbot

Fees

Fees

Competitive landscape