github

twitter

discord

website

Blockchains (L2)

Boba Network

# Boba Network Active users (weekly) Methodology

## 1. Overview

Weekly Active Users (WAU) measures the number of distinct addresses that submitted at least one transaction on the Boba Network blockchain within a 7-day rolling window. This metric provides insight into user engagement and adoption patterns on Boba Network, an Ethereum Layer 2 solution. The calculation uses HyperLogLog probabilistic counting for efficient aggregation of large user sets across multiple dimensional breakdowns.

## 2. Data sources

- **Boba Network transaction records**: Raw blockchain transaction data including transaction metadata, sender addresses, and execution timestamps
- **Transaction sender addresses**: The `from_address` field from transactions, representing users initiating blockchain interactions
- **Block timestamps**: Transaction execution times used for daily and weekly time boundary calculations
- **Transaction identifiers**: Transaction hashes for deduplication and data integrity

## 3. Step-by-step calculation

### Component A: User identification and daily aggregation
- **Purpose**: Identify unique users and aggregate them into Daily Active Users (DAU)
- **Logic**: Extract all transaction records from Boba Network blockchain data. Each transaction's `from_address` field represents a user who actively submitted a transaction. Group these users by day using block timestamps truncated to day boundaries. Each unique address that appears on a given day counts as one daily active user, regardless of how many transactions they submitted.
- **Key fields**: `block_timestamp` for time boundaries, `from_address` as user identifier, `transaction_hash` for deduplication, `chain` set to 'bobanetwork', `user_type` classified as 'Transaction sender'

### Component B: HyperLogLog sketch creation
- **Purpose**: Convert daily user sets into probabilistic counting structures for efficient aggregation
- **Logic**: Transform each day's set of unique user addresses into a HyperLogLog sketch using `hll_count.init` with 15-bit precision. This enables efficient approximate distinct counting when combining multiple days without storing individual user addresses. Each daily user set becomes an HLL sketch that can be merged with other sketches.
- **Key fields**: `timestamp` for the day, `hll` containing the probabilistic user count sketch, dimensional attributes like `chain_id`, `user_type`, and `product_id`

### Component C: Rolling window creation
- **Purpose**: Generate 7-day rolling windows for weekly active user calculation
- **Logic**: Create a datespine covering all days from the earliest transaction date to yesterday. For each day in the spine, generate a 7-day lookback window including the current day plus the previous 6 days using timestamp arrays. This ensures every day has a complete 7-day window for WAU calculation, even if some days had no transactions.
- **Key fields**: `timestamp` for the target day, `joinday` for each day within the 7-day window

### Component D: Weekly aggregation with dimensional breakdowns
- **Purpose**: Calculate WAU across multiple dimensional views
- **Logic**: For each day and its 7-day window, merge all HyperLogLog sketches from those 7 days using `hll_count.merge_partial`, then extract the final distinct count with `hll_count.extract`. This produces the number of unique users active in that 7-day period. Calculate this across four dimensional breakdowns: project-level (overall Boba Network), chain-level, user-type-level, and product-level aggregations.
- **Key fields**: `user_wau` containing the final weekly active user count, `dimensions` indicating the breakdown level, relevant dimensional attributes set to null for aggregated views

### Final aggregation
- **Combining components**: Union all dimensional breakdowns (project, chain, user type, product) into a single result set containing WAU values for each dimensional view
- **Currency conversion**: Not applicable - this is a user count metric
- **Time aggregation**: Each row represents one day's WAU calculation based on a 7-day rolling window ending on that day
- **Final calculation**: The final `user_wau` value represents the approximate count of distinct addresses that submitted at least one transaction within the 7-day period ending on the given timestamp, calculated using HyperLogLog probabilistic counting for scalability and efficiency

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

Unique revenue-generating users over a rolling 7-day window.

Boba NetworkBOBA

Active users (weekly)

Active users (weekly)

Competitive landscape

Chain breakdown