website

twitter

Infrastructure

BONKbot

# BONKbot Average revenue per user (ARPU) Methodology

## 1. Overview

Average Revenue Per User (ARPU) for bonkbot measures the average daily revenue generated per active user of the bonkbot trading protocol on Solana. This metric is calculated by dividing total daily revenue by the number of daily active users, where both metrics are derived from fee payments made to the bonkbot protocol. ARPU helps assess the monetization efficiency and user value generation of the bonkbot trading service.

## 2. Data sources

The calculation uses the following raw data sources:
- **Solana native transfers**: Native SOL transfer events on the Solana blockchain, specifically transfers directed to bonkbot's fee collection address
- **SPL token transfers**: Solana Program Library (SPL) token transfer events, capturing transfers of various SPL tokens to bonkbot's fee collection address
- **End-of-day price feeds**: Token price data used to convert fee payments in different tokens to USD values
- **Token metadata**: Information about token decimal places required for proper amount calculations

## 3. Step-by-step calculation

### Component A: SOL fee collection
- **Purpose**: Captures native SOL fees paid to bonkbot
- **Logic**: Identifies all native SOL transfers directed to bonkbot's fee collection address `ZG98FUCjb8mJ824Gbs6RsgVmr1FhXb2oNiJHa2dwmPd`. Filters out any transfers where the transaction signer is the fee address itself to avoid counting internal transfers. Records the transfer amount, transaction signer, and timestamp for each qualifying transfer.
- **Key fields**: `block_timestamp`, `transaction_id`, `transaction_signer`, `amount` for native SOL, with `token_address` set to SOL's canonical address

### Component B: SPL token fee collection  
- **Purpose**: Captures SPL token fees paid to bonkbot
- **Logic**: Identifies all SPL token transfers where the destination owner address is bonkbot's fee collection address. Similar to SOL fees, excludes transfers where the transaction signer is the fee address to avoid internal accounting transfers. Records the token address, transfer amount, signer, and timestamp for each qualifying transfer.
- **Key fields**: `block_timestamp`, `transaction_id`, `transaction_signer`, `token_address`, `amount` for various SPL tokens

### Component C: Revenue calculation
- **Purpose**: Aggregates and converts all fee payments to USD revenue
- **Logic**: Combines SOL and SPL token fee data, then groups transfers by day, chain, product, and token address. Sums the total amount for each token per day. Applies USD conversion using end-of-day price feeds matched by token address and date. Corrects token amounts for decimal places using token metadata to ensure proper value calculations. Aggregates all token revenues to produce total daily revenue in USD.
- **Key fields**: Daily aggregated `fees` converted to `revenue` in USD after decimal correction

### Component D: Daily active users calculation
- **Purpose**: Counts distinct users who paid fees each day
- **Logic**: Uses the same fee payment data (both SOL and SPL transfers) to identify unique users. Groups transaction signers by day, treating each unique signer as an active user. Uses HyperLogLog probabilistic counting to efficiently handle large user sets while supporting various dimensional breakdowns including chain, user type, and product. Applies zero-filling to ensure continuous daily metrics even on days with no activity.
- **Key fields**: Daily count of distinct `user_dau` (transaction signers who paid fees)

### Final aggregation
- **Combining components**: The ARPU calculation uses the `calculate_arpu` macro which takes the daily revenue values and daily active user counts as inputs. The macro performs a day-by-day division operation to compute average revenue per user.
- **Currency conversion**: All revenue is already converted to USD during the fee aggregation step using end-of-day price feeds, ensuring consistent currency units for the ARPU calculation
- **Time aggregation**: Both revenue and user metrics use daily time boundaries, with timestamps truncated to day precision. Missing days are filled with zeros to maintain a continuous time series.
- **Final calculation**: ARPU equals daily revenue in USD divided by daily active users, where both numerator and denominator are derived from the same underlying fee payment transactions, ensuring user and revenue alignment

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

BONKbot

Average revenue per user (ARPU)

Average revenue per user (ARPU)

Competitive landscape