github

twitter

discord

website

Blockchains (L2)

Boba Network

# Boba Network Average transaction fee Methodology

## 1. Overview

The Boba Network average transaction fee metric measures the mean cost per transaction on the Boba Network blockchain, expressed in USD. This metric is calculated by dividing the total daily transaction fees by the total daily transaction count. The calculation accounts for Boba Network's Layer 2 architecture, where each transaction incurs both L2 execution costs and L1 data availability costs, providing insight into the network's transaction cost efficiency and user economics.

## 2. Data sources

The calculation relies on the following raw data sources:

- **Boba Network transaction records**: Complete transaction data from the Boba Network blockchain including transaction hashes, gas usage metrics, gas prices, L1-specific cost components (L1 gas used, L1 gas price, L1 fee scalar), and block timestamps
- **End-of-day token price feeds**: ETH price data used to convert transaction fees from ETH to USD at daily intervals
- **Token metadata**: Information about token decimals and addressing used during USD conversion processes

## 3. Step-by-step calculation

### Component A: Transaction fee calculation
- **Purpose**: Calculate the total fee paid for each transaction in ETH, accounting for both L2 and L1 costs
- **Logic**: For each transaction record, extract gas usage and pricing data from Boba Network transaction records. Calculate L2 gas fees by multiplying `gas_used` by `gas_price`, then divide by 1e18 to convert from wei to ETH. Calculate L1 gas fees by multiplying `l1_gas_used`, `l1_gas_price`, and `l1_fee_scalar`, then divide by 1e18 to convert from wei to ETH. Sum the L2 and L1 components to get the total transaction fee in ETH. Convert the ETH fees to USD using end-of-day exchange rates with appropriate decimal corrections.
- **Key fields**: `gas_used`, `gas_price`, `l1_gas_used`, `l1_gas_price`, `l1_fee_scalar`, `block_timestamp`, `transaction_hash`

### Component B: Daily fee aggregation
- **Purpose**: Sum all transaction fees by day to get total daily fees in USD
- **Logic**: Take the transaction-level fees calculated in Component A and group them by day using timestamp truncation to daily boundaries. Sum all fees for each day to produce daily totals. Apply gap filling with zeros for any missing days to ensure consistent time series data.
- **Key fields**: `timestamp` (truncated to day), `fees` (summed across all transactions)

### Component C: Daily transaction counting
- **Purpose**: Count the total number of unique transactions per day
- **Logic**: Using the same Boba Network transaction records, group transactions by day using timestamp truncation to daily boundaries. Count distinct transaction hashes for each day, grouping by recipient address to ensure proper aggregation. Apply the same gap filling strategy to maintain consistent daily time series.
- **Key fields**: `transaction_hash` (for distinct counting), `to_address` (for grouping), `timestamp` (truncated to day)

### Final aggregation
- **Combining components**: Join the daily fee totals from Component B with the daily transaction counts from Component C using the daily timestamp as the key
- **Currency conversion**: All fees are converted to USD using end-of-day ETH price feeds before aggregation
- **Time aggregation**: Data is aggregated using daily boundaries determined by timestamp truncation to day level
- **Final calculation**: Calculate the average transaction fee by dividing the daily total fees by the daily transaction count using safe division to handle cases where transaction count might be zero. Apply chain availability filtering to ensure data quality and consistency across the time series.

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

Boba NetworkBOBA

Average transaction fee

Average transaction fee

Competitive landscape

Chain breakdown