Validators process transactions and receive fees from users (supply-side fees).

BNB Chain is a smart contract platform for decentralized applications (a blockchain). BNB Chain was founded by Changpeng Zhao and launched in 2020.

BNB holders own and govern the protocol. They currently take a cut of the total transaction fees paid by users (revenue).

github

twitter

discord

etherscan

website

Blockchains (L1)

BNB Chain

# BNB Chain Average revenue per user (ARPU) Methodology

## 1. Overview

Average Revenue Per User (ARPU) measures the daily revenue generated per active user across the BSC ecosystem, including both BSC mainnet (L1) and opBNB (L2). This metric provides insight into user monetization efficiency by dividing total daily protocol revenue by the number of unique daily active users. The calculation combines fee burn revenue from BSC with gas fee revenue from opBNB to create a comprehensive view of revenue per user across the entire BSC ecosystem.

## 2. Data sources

- **BSC blockchain transaction records**: Complete transaction data from BSC mainnet including sender addresses, gas usage, and gas prices
- **opBNB blockchain transaction records**: L2 transaction data including gas metrics, L1 fee components, and user addresses  
- **BSC ValidatorSet feeBurned events**: Parsed `feeBurned` events from BSC ValidatorSet contract tracking BNB token burns
- **End-of-day token price feeds**: Daily closing prices for BNB token used in USD conversion
- **Token metadata**: Decimal place information for proper token amount normalization

## 3. Step-by-step calculation

### Component A: Daily active users calculation
- **Purpose**: Count unique transaction senders across BSC and opBNB networks using efficient HyperLogLog aggregation
- **Logic**: Extract distinct `from_address` values from BSC mainnet transactions and opBNB L2 transactions. Truncate timestamps to daily boundaries and apply HyperLogLog sketching for scalable distinct counting. Union BSC and opBNB user addresses while maintaining chain-specific tagging (`bsc` for L1, `opbnb` for L2). Generate dimensional breakdowns by chain, user type, and product identifier
- **Key fields**: `from_address` as user identifier, `block_timestamp` for daily truncation, `chain` for network identification, `user_type` set to "Transaction sender"

### Component B: BSC fee burn revenue calculation  
- **Purpose**: Calculate revenue from BNB token burns executed by BSC validators
- **Logic**: Extract `feeBurned` events from BSC ValidatorSet contract, focusing on BNB token burns. Aggregate daily burn amounts using the `amount` field from burn events. Apply daily timestamp truncation and sum all burns per day. The burns represent actual BNB tokens removed from circulation as protocol revenue
- **Key fields**: `amount` for burn quantity, `block_timestamp` for daily aggregation, `token_address` for BNB identification, `account_address` for validator identification

### Component C: opBNB gas fee revenue calculation
- **Purpose**: Calculate L1 and L2 gas fee revenue generated by opBNB transactions
- **Logic**: Process opBNB transaction data to calculate both L2 execution fees and L1 data availability fees. L2 fees calculated as `gas_used` × `gas_price` divided by 1e18 for Wei conversion. L1 fees calculated as `l1_gas_used` × `l1_gas_price` × `l1_fee_scalar` divided by 1e18. Sum L1 and L2 components for total transaction fee. Aggregate daily across all transactions
- **Key fields**: `gas_used` and `gas_price` for L2 fees, `l1_gas_used`, `l1_gas_price`, and `l1_fee_scalar` for L1 fees, `block_timestamp` for daily boundaries

### Component D: Revenue USD conversion
- **Purpose**: Convert all revenue amounts to USD using consistent pricing methodology
- **Logic**: Apply end-of-day price feeds to convert BNB-denominated revenues to USD. Use token metadata to apply proper decimal corrections ensuring accurate value representation. Handle both BSC burn amounts and opBNB gas fees through the same conversion process. Aggregate converted USD amounts across both revenue streams
- **Key fields**: `token_address` for price lookup, `amount` or calculated fees for conversion, daily price feeds for exchange rates

### Final aggregation
- **Combining components**: Union BSC fee burn revenue with opBNB gas fee revenue after USD conversion. Sum total daily revenue across both networks. Use HLL-aggregated user counts from combined BSC and opBNB user data
- **Currency conversion**: All revenue converted to USD using end-of-day BNB prices with decimal normalization applied consistently across token amounts  
- **Time aggregation**: Daily boundaries defined by timestamp truncation to day level. All metrics aggregated to same daily grain before division
- **Final calculation**: Divide total daily USD revenue (BSC burns + opBNB gas fees) by total daily active users (BSC senders + opBNB senders) to produce average revenue per user in USD. Apply zero-filling strategy for days with missing data and generate dimensional breakdowns by chain and product.

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

BNB ChainBNB

Average revenue per user (ARPU)

Average revenue per user (ARPU)

Competitive landscape