opBNB is built on the OP Stack, the same underlying framework as Optimism. It extends the Ethereum Virtual Machine (EVM) to provide faster and cheaper transactions, while leveraging BNB Smart Chain (BSC) for ecosystem integration.

opBNB is an Ethereum-compatible Layer 2 scaling solution designed to improve the performance and affordability of decentralized applications on BNB Chain. It provides high throughput and low fees, making it suitable for gaming, social, and DeFi applications.

opBNB is developed by BNB Chain, which is supported by contributors from the broader Binance ecosystem.

twitter

etherscan

website

Blockchains (L2)

opBNB

# opBNB Active addresses (daily) Methodology

## 1. Overview

Daily active addresses measures the number of unique wallet addresses that conducted at least one transaction on the OpBNB blockchain each day. For blockchain protocols, active addresses are equivalent to active users since each user interacts through their wallet address. This metric provides insight into daily user engagement and adoption on the OpBNB Layer 2 network.

## 2. Data sources

- **OpBNB transaction records**: Complete transaction data from the OpBNB Layer 2 blockchain, including transaction senders (`from_address`), block timestamps, and transaction hashes
- **Chain availability data**: Configuration data that defines the operational periods when OpBNB was available and functioning properly

## 3. Step-by-step calculation

### Component A: User extraction from transactions
- **Purpose**: Identifies unique user addresses from OpBNB transaction activity
- **Logic**: Extracts the `from_address` field from each OpBNB transaction as the user address, along with the `block_timestamp`. Each transaction sender represents a user interacting with the OpBNB blockchain. Transactions are classified with chain metadata including 'opbnb' as chain identifier, 'blockchains_l2' as market sector, and 'blockchain' as business segment. User type is standardized as 'Transaction sender' since all activity stems from transaction initiation.
- **Key fields**: `user_address` (transaction sender), `block_timestamp` (when transaction occurred), `transaction_hash` (unique transaction identifier)

### Component B: Daily user aggregation
- **Purpose**: Creates daily unique user counts from transaction-level data
- **Logic**: Groups user addresses by day using timestamp truncation to day granularity. Extracts distinct user addresses for each day to identify unique daily active users. Uses incremental processing with lookback periods to handle late-arriving transaction data efficiently.
- **Key fields**: `timestamp` (truncated to day), `user_dau` (unique user address), `chain` (OpBNB identifier)

### Component C: HyperLogLog aggregation across dimensions
- **Purpose**: Efficiently aggregates unique user counts across multiple dimensional breakdowns
- **Logic**: Applies HyperLogLog probabilistic counting algorithm to handle large-scale unique address counting efficiently. Creates separate dimensional views including project-wide aggregation ('project_dbt_tag' dimension), chain-level breakdown ('chain' dimension), user-type breakdown, and product-level breakdown. Uses HyperLogLog initialization with precision parameter 15 for daily sketches, then merges and extracts final counts for each dimensional grouping. Combines all dimensional breakdowns using union operations.
- **Key fields**: `hll` (HyperLogLog sketch), `user_dau` (extracted unique count), `dimensions` (breakdown category), `chain_id` (chain identifier)

### Final aggregation
- **Combining components**: Maps the `user_dau` field directly to `active_addresses_daily` since blockchain active users and active addresses are equivalent concepts. Filters to include only 'chain' and 'project_dbt_tag' dimensional breakdowns for the final active addresses metric.
- **Currency conversion**: No currency conversion required as this is a count-based metric
- **Time aggregation**: Daily boundaries determined by timestamp truncation to day granularity in UTC timezone
- **Final calculation**: The final active addresses count represents the number of unique wallet addresses that sent at least one transaction on OpBNB during each calendar day, calculated using HyperLogLog approximation for scalability and filled with zeros for any missing days to ensure continuous time series data

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

Unique active addresses over a fixed 24-hour window.

opBNB

Active addresses (daily)

Active addresses (daily)

Competitive landscape

Chain breakdown