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 Contracts deployed Methodology

## 1. Overview

The contracts deployed metric measures the daily number of smart contracts deployed across the BNB ecosystem, specifically tracking contract deployments on both BSC (BNB Smart Chain) mainnet and opBNB Layer 2. This metric provides insights into developer activity and platform adoption by counting new smart contract deployments each day. The calculation aggregates contract creation events from blockchain transaction traces across both chains and presents them as daily totals with appropriate chain classification.

## 2. Data sources

- **BSC blockchain contract deployment events**: Smart contract creation events recorded on BSC mainnet, including creation timestamps, contract addresses, deployer addresses, and transaction trace information
- **opBNB blockchain contract deployment events**: Smart contract creation events recorded on the opBNB Layer 2 network, including creation timestamps, contract addresses, deployer addresses, transaction traces, contract bytecode, and creator addresses
- **BSC transaction traces**: Detailed transaction execution traces that capture contract creation operations on BSC mainnet
- **opBNB transaction traces**: Detailed transaction execution traces that capture contract creation operations on the opBNB Layer 2 network

## 3. Step-by-step calculation

### Component A: BSC contract creations
- **Purpose**: Extract and process smart contract deployment events from BSC mainnet
- **Logic**: Query BSC blockchain data to identify contract creation events. Select distinct records to avoid double-counting, capturing the creation timestamp as `block_timestamp`, the deployed contract address as `account_address`, the address that deployed the contract as `deployer_address`, and the transaction trace address as `creation_trace_address`. Apply incremental processing to handle new deployments efficiently with a lookback period for data freshness
- **Key fields**: `block_timestamp` (contract creation time), `account_address` (deployed contract address), `deployer_address` (entity that deployed the contract), `creation_trace_address` (transaction trace reference)

### Component B: opBNB contract creations  
- **Purpose**: Extract and process smart contract deployment events from opBNB Layer 2
- **Logic**: Query opBNB blockchain data to identify contract creation events using the same approach as BSC. Select distinct records capturing creation timestamp, contract address, deployer address, and creation trace address. Additionally capture contract bytecode and creator address fields specific to opBNB. Apply incremental processing with lookback mechanism for data consistency
- **Key fields**: `block_timestamp` (contract creation time), `account_address` (deployed contract address), `deployer_address` (entity that deployed the contract), `creation_trace_address` (transaction trace reference), `contract_bytecode` (deployed contract code), `creator_address` (contract creator)

### Daily aggregation by chain
- **Purpose**: Count contract deployments per day for each blockchain network
- **Logic**: Truncate creation timestamps to daily boundaries using day-level granularity. Group contract creation events by day for each chain separately. Count the total number of contracts deployed each day. Assign chain-specific metadata: BSC deployments are classified as `bsc` chain with `blockchains_l1` market sector, while opBNB deployments are classified as `opbnb` chain with `blockchains_l2` market sector. Both chains are categorized under `blockchain` business segment with their respective product identifiers
- **Key fields**: `timestamp` (daily boundary), `timestamp_grain` (day-level aggregation), `chain_id` (bsc or opbnb), `market_sector_id` (blockchains_l1 or blockchains_l2), `business_segment_id` (blockchain), `product_id` (bsc or opbnb), `contracts_deployed` (daily count)

### Final aggregation
- **Combining components**: Union the daily aggregated contract deployment counts from both BSC and opBNB chains into a single dataset, preserving chain-specific metadata and counts
- **Currency conversion**: Not applicable as this metric counts events rather than monetary values
- **Time aggregation**: Daily boundaries are established by truncating timestamps to day level, ensuring consistent daily reporting across both chains
- **Final calculation**: Apply the finalize metric macro to standardize the output format and implement a fill zeros strategy for days with no contract deployments. Apply chain availability filtering to ensure data quality and completeness. The final metric represents the total number of smart contracts deployed per day on each respective blockchain network within the BNB ecosystem

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

Unique smart contracts published onchain.

BNB ChainBNB

Contracts deployed

Contracts deployed

Competitive landscape

Chain breakdown