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

## 1. Overview

This metric measures the daily number of unique addresses that deployed smart contracts on the opBNB Layer 2 blockchain. Contract deployers represent developer activity and ecosystem growth, as each unique deployer address indicates an entity (developer, team, or protocol) creating new smart contracts on the network. The calculation aggregates contract creation events by day and counts distinct deployer addresses within each 24-hour period.

## 2. Data sources

- **opBNB blockchain contract creation data**: Records of all smart contract deployments on the opBNB network, including deployer addresses, creation timestamps, contract addresses, and deployment transaction details
- **opBNB transaction traces**: Detailed execution traces that capture contract creation operations and their associated metadata
- **opBNB block data**: Block timestamps used to establish daily time boundaries for aggregation

## 3. Step-by-step calculation

### Component A: Contract creation extraction
- **Purpose**: Identifies all contract deployment events on opBNB with their associated deployer addresses and timestamps
- **Logic**: Extracts contract creation records from opBNB blockchain data, capturing the `deployer_address` (the entity that initiated the contract deployment), `creation_timestamp` (when the contract was deployed), `contract_address` (the resulting contract address), and additional deployment metadata like `creation_trace_address`, `contract_bytecode`, and `creator_address`
- **Key fields**: `creation_timestamp` for temporal grouping, `deployer_address` for distinct counting, `contract_address` for deployment identification

### Component B: Daily aggregation
- **Purpose**: Groups contract deployments by day and counts unique deployers within each daily period
- **Logic**: Truncates `creation_timestamp` values to daily boundaries, creating consistent 24-hour periods. Groups all contract creation events by the truncated daily timestamp and counts distinct `deployer_address` values within each day. This ensures that if the same address deploys multiple contracts on the same day, it is only counted once
- **Key fields**: `timestamp` (truncated to day), `contract_deployers` (distinct count of deployer addresses)

### Final aggregation
- **Combining components**: The daily aggregation directly produces the final metric values - no additional combining is needed since the calculation is straightforward distinct counting
- **Currency conversion**: Not applicable - this is a count-based metric measuring addresses, not financial values
- **Time aggregation**: Daily boundaries are established using timestamp truncation to day level, ensuring consistent 24-hour periods regardless of timezone
- **Final calculation**: For each day, the final metric value equals the count of distinct deployer addresses that created at least one smart contract on opBNB during that 24-hour period. The metric includes standard Token Terminal metadata identifying it as an opBNB blockchain metric in the Layer 2 market sector

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

Unique addresses that deployed at least one smart contract.

opBNB

Contract deployers

Contract deployers

Competitive landscape

Chain breakdown