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 Contract deployers Methodology

## 1. Overview

The BSC contract deployers metric measures the daily count of unique addresses that deploy smart contracts on the BSC ecosystem, including both BSC mainnet (layer 1) and opBNB (layer 2). This metric provides insights into development activity and ecosystem growth by tracking how many distinct developers or entities are actively deploying contracts each day across the BSC infrastructure.

## 2. Data sources

- **BSC blockchain contract creation records**: Raw contract deployment transactions from BSC mainnet containing deployer addresses, creation timestamps, contract addresses, and transaction trace information
- **opBNB blockchain contract creation records**: Raw contract deployment transactions from opBNB layer 2 containing deployer addresses, creation timestamps, contract addresses, transaction traces, contract bytecode, and creator address information

## 3. Step-by-step calculation

### Component A: BSC mainnet contract deployments
- **Purpose**: Extract and count unique contract deployers on BSC mainnet (layer 1)
- **Logic**: Extract all contract creation events from BSC blockchain data, filtering to get distinct records with creation timestamp, contract address, deployer address, and trace information. Group the data by day using timestamp truncation, then count the number of distinct `deployer_address` values for each day. Apply chain-specific metadata including chain identifier as 'bsc', market sector as 'blockchains_l1', and business segment as 'blockchain'
- **Key fields**: `creation_timestamp` (converted to `block_timestamp`), `deployer_address` for unique counting, `contract_address` for deployment tracking, `creation_trace_address` for transaction context

### Component B: opBNB layer 2 contract deployments  
- **Purpose**: Extract and count unique contract deployers on opBNB layer 2
- **Logic**: Extract all contract creation events from opBNB blockchain data, similar to BSC but including additional fields like contract bytecode and creator address. Group the data by day using timestamp truncation, then count the number of distinct `deployer_address` values for each day. Apply chain-specific metadata including chain identifier as 'opbnb', market sector as 'blockchains_l2', and business segment as 'blockchain'
- **Key fields**: `creation_timestamp` (converted to `block_timestamp`), `deployer_address` for unique counting, `contract_address`, `creation_trace_address`, `contract_bytecode`, `creator_address`

### Final aggregation
- **Combining components**: Union the daily deployer counts from both BSC mainnet and opBNB layer 2, maintaining separate records for each chain to preserve layer-specific metrics
- **Currency conversion**: Not applicable for this count-based metric
- **Time aggregation**: Daily boundaries determined by truncating timestamps to day granularity using local timezone
- **Final calculation**: The metric represents the count of distinct deployer addresses per day per chain, with a fill-zeros strategy applied to ensure continuous time series data even for days with no contract deployments. Chain availability filtering ensures only valid data periods are included for each blockchain

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

Unique addresses that deployed at least one smart contract.

BNB ChainBNB

Contract deployers

Contract deployers

Competitive landscape

Chain breakdown