website

twitter

Infrastructure

BONKbot

# BONKbot Active users (daily) Methodology

## 1. Overview

The BonkBot Daily Active Users (DAU) metric measures the number of unique users who interact with the BonkBot trading service on Solana each day. The calculation identifies active users by tracking fee payments to BonkBot's fee collection address, as users pay fees when executing trades through the service. This metric answers the business question: "How many distinct users are actively trading through BonkBot on a daily basis?"

## 2. Data sources

The metric relies on the following raw Solana blockchain data sources:
- **Native token transfers**: Solana native SOL transfers that capture fee payments from users to BonkBot's fee collection address
- **SPL token transfers**: Solana Program Library (SPL) token transfers that capture token-denominated fee payments to BonkBot's fee collection address  
- **Transaction metadata**: Transaction signer information that identifies the user addresses initiating the fee payments

## 3. Step-by-step calculation

### Component A: SOL fee extraction
- **Purpose**: Identifies users paying fees in SOL (Solana's native token) to BonkBot
- **Logic**: Filters Solana native token transfers to identify payments made to BonkBot's fee collection address `ZG98FUCjb8mJ824Gbs6RsgVmr1FhXb2oNiJHa2dwmPd`. The process excludes self-transfers where the transaction signer matches the fee address to avoid counting internal BonkBot operations. Each transfer record includes the transaction timestamp, signer address, and transfer amount.
- **Key fields**: `block_timestamp` for timing, `transaction_signer` as the user identifier, `to_address` for fee address filtering, `amount` for fee values

### Component B: SPL token fee extraction  
- **Purpose**: Identifies users paying fees in SPL tokens (non-native tokens) to BonkBot
- **Logic**: Filters Solana SPL token transfers to capture token-denominated fee payments made to BonkBot's fee collection address. Similar to SOL fees, this excludes self-transfers where the transaction signer matches the fee collection address. The data includes token contract addresses to identify which tokens are used for fee payments.
- **Key fields**: `block_timestamp` for timing, `transaction_signer` as the user identifier, `to_owner_address` for fee address filtering, `token_address` for token identification, `amount` for fee values

### Component C: Daily user aggregation
- **Purpose**: Combines fee data and calculates daily active users across both fee types
- **Logic**: Unions the SOL and SPL token fee data into a single dataset. Truncates all timestamps to day granularity and extracts distinct transaction signers for each day. All users are classified with `user_type` as "Trader" since fee payment indicates trading activity. The process creates daily snapshots of unique users who paid fees through BonkBot.
- **Key fields**: `timestamp` truncated to day, `chain` as "solana", `user_type` as "Trader", `signer` as the unique user identifier

### Component D: HyperLogLog aggregation
- **Purpose**: Enables efficient distinct user counting across multiple dimensional breakdowns
- **Logic**: Initializes HyperLogLog (HLL) sketches for each day's user set to enable scalable distinct counting operations. Creates separate aggregations for different dimensional breakdowns: project-level (all users combined), chain-level (by blockchain), user-type-level (by user classification), and product-level (by product identifier). HLL allows these breakdowns to be computed efficiently even with large user sets.
- **Key fields**: `hll` sketches containing compressed user sets, dimension identifiers for each breakdown type

### Final aggregation
- **Combining components**: The different dimensional breakdowns are unioned together into a single result set, with each row representing a different dimensional slice of the DAU metric
- **Currency conversion**: Not applicable - this metric counts users, not monetary values
- **Time aggregation**: Daily boundaries are established by truncating timestamps to day granularity, ensuring consistent daily user counting
- **Final calculation**: The final DAU value for each day and dimension is extracted from the merged HLL sketches, providing the count of distinct users who paid fees to BonkBot on that day. Missing days are filled with zero values to maintain continuous time series data.

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

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

BONKbot

Active users (daily)

Active users (daily)

Competitive landscape