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) Transaction count Methodology

## 1. Overview

The Bob blockchain daily transaction count measures the total number of unique transactions processed on the Bob Layer 2 blockchain each day, segmented by recipient address. This metric provides insights into network activity, user engagement, and transaction volume patterns on the Bob blockchain. The calculation aggregates raw transaction data to daily boundaries and counts distinct transaction hashes while ensuring data completeness through gap filling and availability filtering.

## 2. Data sources

- **Bob blockchain transaction records**: Raw transaction data from the Bob Layer 2 blockchain containing transaction hashes, block timestamps, sender addresses (`from_address`), and recipient addresses (`to_address`)
- **Chain availability configuration data**: Metadata defining when Bob blockchain data is considered reliable and available for analysis

## 3. Step-by-step calculation

### Component A: Transaction data preparation
- **Purpose**: Standardizes raw Bob blockchain transaction data with proper type casting and chain identification
- **Logic**: Raw transaction records from the Bob blockchain are processed by casting timestamp, transaction hash, and address fields to appropriate data types. Each record is tagged with the chain identifier 'bob' to distinguish it from other blockchain data. This creates a clean fact table of Bob transactions with standardized field types.
- **Key fields**: `block_timestamp` (when the transaction was included in a block), `transaction_hash` (unique identifier), `from_address` (sender), `to_address` (recipient), `chain` (always 'bob')

### Component B: Daily aggregation by recipient
- **Purpose**: Groups transactions by day and recipient address to calculate daily transaction counts
- **Logic**: Transaction timestamps are truncated to day boundaries using timestamp truncation. Records are grouped by the truncated timestamp, chain metadata fields (chain_id, market_sector_id, business_segment_id), and recipient address (`to_address`). For each group, distinct transaction hashes are counted to determine how many unique transactions each recipient address received on each day. Static metadata is added to categorize Bob as a Layer 2 blockchain in the 'blockchains_l2' market sector.
- **Key fields**: `timestamp` (truncated to day), `transaction_count` (distinct count of `transaction_hash`), `to_address` (transaction recipient), chain categorization fields

### Final aggregation
- **Combining components**: The daily aggregated data flows through a finalization macro that standardizes the output schema, validates chain and market sector identifiers, and ensures data completeness
- **Time aggregation**: Daily boundaries are enforced through timestamp truncation, with incremental processing logic that includes a lookback period to handle late-arriving data
- **Gap filling**: Missing days in the time series are filled with zero transaction counts using a 'fill_zeros' strategy to maintain continuity
- **Data filtering**: Chain availability filtering removes data from periods when Bob blockchain data may be unreliable or incomplete
- **Final calculation**: The final metric represents the count of distinct transaction hashes received by each address on the Bob blockchain for each day, with complete time series coverage and proper data validation

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

Confirmed transactions added to the blockchain.

BOB (Build on Bitcoin)BOB

Transaction count

Transaction count

Competitive landscape

Chain breakdown