github

twitter

discord

website

Blockchains (L2)

Boba Network

# Boba Network Contracts deployed Methodology

## 1. Overview

The contracts deployed metric measures the daily number of smart contracts deployed on Boba Network, an Ethereum Layer 2 scaling solution. This metric tracks ecosystem growth and developer activity by counting unique contract creation events per day. The calculation uses blockchain transaction data to identify contract deployments and aggregates them into daily counts with complete time series coverage.

## 2. Data sources

- **Boba Network contract deployment records**: Comprehensive blockchain data containing all contract creation events on Boba Network, including deployment timestamps, contract addresses, deployer addresses, transaction traces, and contract bytecode
- **Chain availability configuration**: Metadata defining operational periods when Boba Network blockchain data is considered reliable and complete for accurate historical reporting

## 3. Step-by-step calculation

### Component A: Contract creation extraction
- **Purpose**: Extract and deduplicate all contract deployment events from Boba Network blockchain data
- **Logic**: Pull contract creation records including `creation_timestamp`, `contract_address`, `deployer_address`, `creation_trace_address`, `contract_bytecode`, and `creator_address`. Apply deduplication using distinct selection to ensure each contract deployment is counted exactly once, preventing double-counting from multiple data sources or processing artifacts
- **Key fields**: `creation_timestamp` for timing, `contract_address` for unique identification, `deployer_address` and `creator_address` for deployment context

### Component B: Daily aggregation
- **Purpose**: Group contract deployments by day and count the total number deployed
- **Logic**: Truncate creation timestamps to daily boundaries using day-level time truncation. Group all contract creation events by the truncated timestamp and count the total number of contracts deployed each day. Add standard metadata fields including chain identifier as "bobanetwork", market sector as "blockchains_l2", and business segment as "blockchain"
- **Key fields**: `timestamp` truncated to day level, `contracts_deployed` as the daily count, classification metadata for reporting structure

### Final aggregation
- **Combining components**: The daily contract counts flow directly from the aggregation component without additional combination steps
- **Currency conversion**: Not applicable for this count-based metric
- **Time aggregation**: Daily boundary logic uses timestamp truncation to day level, ensuring all deployments within a 24-hour period are grouped together
- **Final calculation**: Apply finalization macro with zero-filling strategy to create complete daily time series, filling any gaps in the data with zero values for days with no contract deployments. Filter results using chain availability rules to exclude periods when Boba Network data may be incomplete or unreliable, ensuring accurate historical reporting of ecosystem activity

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

Unique smart contracts published onchain.

Boba NetworkBOBA

Contracts deployed

Contracts deployed

Competitive landscape

Chain breakdown