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) Transactions per second Methodology

## 1. Overview

Transactions per second (TPS) measures the average rate of transaction processing on the BOB blockchain. This metric provides insight into network activity and throughput by calculating the daily average number of transactions processed per second. The calculation takes daily transaction counts and divides by the number of seconds in a day (86,400) to provide a standardized rate metric that can be compared across different time periods.

## 2. Data sources

- **BOB blockchain transaction data**: Raw transaction records from the BOB blockchain containing transaction hashes, block timestamps, sender addresses (`from_address`), and recipient addresses (`to_address`)
- **Chain availability configuration**: Metadata defining when BOB blockchain data is available for processing
- **Table processing metadata**: Internal tracking data for incremental processing and partition management

## 3. Step-by-step calculation

### Component A: Transaction data extraction
- **Purpose**: Extract and standardize raw BOB blockchain transaction data
- **Logic**: Raw transaction records are extracted from BOB blockchain data and standardized by casting fields to appropriate data types. The `block_timestamp` field is converted to timestamp format, transaction hashes and addresses are cast as strings, and the chain identifier is set to 'bob'. This component serves as the foundation layer providing clean, typed transaction data for downstream processing.
- **Key fields**: `block_timestamp` for timing, `transaction_hash` for unique identification, `from_address` and `to_address` for transaction participants, `chain` identifier

### Component B: Daily transaction counting
- **Purpose**: Aggregate transaction counts by day and apply business categorization
- **Logic**: Transaction data is grouped by day using timestamp truncation of the `block_timestamp` to day granularity. For each day, distinct transaction hashes are counted to ensure no duplicates are included in the count. The aggregation includes business metadata categorization with `chain_id` set to 'bob', `market_sector_id` as 'blockchains_l2', and `business_segment_id` as 'blockchain'. Incremental processing logic ensures only recent data is processed during updates, looking back a configurable number of days from the maximum partition date.
- **Key fields**: `timestamp` (truncated to day), `timestamp_grain` set to 'day', `transaction_count` as distinct count of `transaction_hash`

### Final aggregation
- **Combining components**: Daily transaction counts from the previous component are used directly as input for the rate calculation
- **Rate conversion**: Daily transaction counts are converted to transactions per second using safe division by the number of seconds in a day (86,400). The `safe_divide` function handles potential division by zero scenarios gracefully
- **Time aggregation**: Data maintains daily granularity with each day's transactions averaged over the full 24-hour period
- **Final calculation**: The final transactions per second value equals the daily transaction count divided by 86,400 seconds, providing the average rate of transaction processing for each day. Schema validation and gap-filling with zeros ensures continuous time series data with proper metadata structure.

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

Average confirmed user transactions added per second.

BOB (Build on Bitcoin)BOB

Transactions per second

Transactions per second

Competitive landscape

Chain breakdown