BOB batches users' transactions and submits them to Ethereum, paying a share of the transaction fees to Ethereum validators (expense).

BOB is an L2 smart contract platform for decentralized applications on Ethereum. BOB was founded by Alexei Zamyatin and Dominik Harz and launched in 2024.

BOB team & investors own and govern the protocol. BOB's investors include Castle Island Ventures, IOSG Ventures, Coinbase Ventures, etc.

github

twitter

discord

website

Blockchains (L2)

BOB (Build on Bitcoin)

# BOB (Build on Bitcoin) Active addresses (daily) Methodology

## 1. Overview

The BOB active addresses daily metric measures the number of unique addresses that initiated at least one transaction on the BOB blockchain each day. This metric serves as a key indicator of blockchain adoption and daily network activity. The calculation identifies unique transaction senders (from addresses) per day, treating each sender address as an active user of the blockchain.

## 2. Data sources

- **BOB blockchain transactions**: Raw transaction records from the BOB blockchain containing transaction metadata, timestamps, and sender addresses
- **Transaction timestamps**: Block-level timestamps indicating when each transaction was processed on the BOB blockchain  
- **Sender addresses**: The `from_address` field from each transaction, representing the address that initiated the transaction

## 3. Step-by-step calculation

### Component A: Transaction data extraction
- **Purpose**: Extract and standardize raw BOB blockchain transaction data for user activity analysis
- **Logic**: Pull transaction records from BOB blockchain data, casting timestamps and transaction hashes to appropriate data types. Each transaction sender address is classified as a blockchain user with user type "Transaction sender". The data is tagged with BOB chain identifier and categorized under "blockchains_l2" market sector and "blockchain" business segment
- **Key fields**: `block_timestamp` (when transaction occurred), `transaction_hash` (unique transaction identifier), `from_address` (transaction sender address, renamed to `user_address`)

### Component B: Daily unique user calculation  
- **Purpose**: Calculate daily active users using approximate counting methodology
- **Logic**: Group transaction data by day using timestamp truncation to daily boundaries. For each day, identify all unique sender addresses that initiated transactions. Use HyperLogLog probabilistic algorithm with precision parameter 15 to efficiently approximate the count of distinct addresses per day. This approach handles large-scale data while maintaining acceptable accuracy for unique counting
- **Key fields**: `timestamp` (truncated to daily boundary), `user_address` (unique transaction sender), `user_dau` (HyperLogLog sketch of unique users)

### Component C: Multi-dimensional aggregation
- **Purpose**: Create breakdowns of daily active users across different analytical dimensions
- **Logic**: Aggregate the HyperLogLog sketches across four different dimensions: by project tag (overall BOB ecosystem level), by chain (BOB chain level), by user type (transaction senders), and by product (null for blockchain-level metrics). Each dimension creates separate aggregation groups, and HyperLogLog partial sketches are merged within each group to maintain approximate uniqueness counting across the different analytical cuts
- **Key fields**: `dimensions` (analytical grouping: 'project_dbt_tag', 'chain', 'user_type', 'product_id'), `user_dau` (extracted count from merged HyperLogLog sketches)

### Final aggregation
- **Combining components**: Select aggregated user data specifically for 'chain' and 'project_dbt_tag' dimensions, which provide the most relevant breakdowns for active addresses reporting
- **Currency conversion**: Not applicable - this is a count-based metric measuring number of addresses
- **Time aggregation**: Data is aggregated to daily boundaries with timestamps truncated to day level. Missing days are filled with zero values to ensure continuous time series
- **Final calculation**: Rename the `user_dau` field to `active_addresses_daily` to reflect that for blockchain metrics, active users are equivalent to active addresses. Apply chain availability filters to ensure data quality standards are met for the BOB blockchain

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

Unique active addresses over a fixed 24-hour window.

BOB (Build on Bitcoin)BOB

Active addresses (daily)

Active addresses (daily)

Competitive landscape

Chain breakdown