OP Mainnet batches users' transactions and submits them to Ethereum, paying a share of the transaction fees to Ethereum validators (expense).

OP Mainnet is an L2 smart contract platform for decentralized applications on Ethereum. OP Mainnet was founded by Jinglan Wang, Karl Floersch & Kevin Ho and launched in 2021.

Optimism team & investors own and govern the protocol. Optimism’s investors include Paradigm, a16z, IDEO CoLab Ventures, etc.

governance

github

twitter

discord

etherscan

website

Blockchains (L2)

OP Mainnet

# OP Mainnet Contracts deployed Methodology

## 1. Overview

The contracts deployed metric measures the daily number of smart contracts deployed on the Optimism network. This metric tracks blockchain development activity by counting unique contract creation events per day. It provides insight into developer activity and ecosystem growth on the Optimism Layer 2 network.

## 2. Data sources

- **Contract creation events**: Optimism blockchain transaction traces that record smart contract deployments
- **Transaction data**: Optimism network transaction records containing contract deployment information
- **Blockchain metadata**: Block timestamps and transaction trace addresses for contract creation identification

## 3. Step-by-step calculation

### Component A: Contract creation identification
- **Purpose**: Identify and extract all contract creation events from Optimism blockchain data
- **Logic**: Extract distinct contract creation records from Optimism blockchain transaction traces. Each record contains the contract deployment timestamp (`creation_timestamp`), the deployed contract address (`contract_address`), the deployer's address (`deployer_address`), and the transaction trace address (`creation_trace_address`) where the deployment occurred. The distinct clause ensures each contract creation is counted only once, preventing duplicate counting of the same deployment event.
- **Key fields**: `block_timestamp` (deployment time), `account_address` (deployed contract), `deployer_address` (creator), `creation_trace_address` (transaction location)

### Component B: Daily aggregation and standardization  
- **Purpose**: Group contract creations by day and apply metric standardization
- **Logic**: Truncate the block timestamps to daily boundaries using timestamp truncation to group all contract creations within the same day. Count the total number of contracts deployed per day using a simple count aggregation. Apply standardized metadata including chain identifier as 'optimism', market sector as 'blockchains_l2', and business segment as 'blockchain'. Set product identifier as null since this is a chain-level metric rather than a product-specific metric.
- **Key fields**: `timestamp` (daily boundary), `contracts_deployed` (daily count), chain and market classification metadata

### Final aggregation
- **Combining components**: The daily contract creation counts are processed through the finalize metric macro which applies data quality standards and formatting consistency
- **Data quality**: Apply chain availability filtering to ensure the metric meets data quality thresholds and exclude periods with incomplete or unreliable data
- **Fill strategy**: Use fill_zeros strategy to ensure missing days are represented with zero contract deployments rather than null values
- **Final calculation**: The final metric value represents the total count of unique smart contracts deployed on the Optimism network for each day, with data quality filters applied to ensure reliability

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

Unique smart contracts published onchain.

OP MainnetOP

Contracts deployed

Contracts deployed

Competitive landscape

Chain breakdown