github

twitter

discord

website

Blockchains (L2)

Boba Network

# Boba Network Contract deployers Methodology

## 1. Overview

The Boba Network contract deployers metric measures the daily count of unique addresses that deployed smart contracts on the Boba Network blockchain. This metric tracks developer and protocol activity by counting distinct deployer addresses per day, providing insight into the ecosystem's growth and development activity. The metric answers the business question: "How many unique entities are deploying new smart contracts on Boba Network each day?"

## 2. Data sources

The calculation relies on the following raw data sources:

- **Boba Network contract creation events**: Records of all smart contract deployments on the Boba Network blockchain, including deployer addresses, contract addresses, creation timestamps, and deployment transaction traces
- **Boba Network blockchain data**: Block-level data providing timestamps for when contract creation transactions were processed on the network
- **Transaction traces**: Detailed execution traces that capture contract deployment operations and their associated deployer addresses

## 3. Step-by-step calculation

### Component A: Contract creation data extraction
- **Purpose**: Identifies all contract deployment events on Boba Network with their associated deployer information
- **Logic**: Extracts contract creation records from Boba Network blockchain data, capturing the `creation_timestamp` when each contract was deployed, the deployed `contract_address`, and the `deployer_address` of the entity that initiated the deployment. Additional metadata includes `creation_trace_address` for transaction tracing, `contract_bytecode` of the deployed contract, and `creator_address` information. The data is deduplicated using distinct selection to ensure each contract creation is counted only once
- **Key fields**: `creation_timestamp` for timing, `contract_address` for the deployed contract, `deployer_address` for the deploying entity, `creation_trace_address` for transaction identification, `contract_bytecode` for the contract code, and `creator_address` for additional attribution

### Component B: Daily aggregation with metadata
- **Purpose**: Aggregates contract deployments by day and counts unique deployers while adding classification metadata
- **Logic**: Truncates `block_timestamp` to daily boundaries using day-level timestamp truncation to group contract deployments by calendar day. Counts distinct `deployer_address` values per day to calculate unique deployers, ensuring that addresses deploying multiple contracts on the same day are counted only once. Enriches each daily record with metadata: `timestamp_grain` set to 'day' for time series classification, `chain_id` set to 'bobanetwork' for blockchain identification, `market_sector_id` set to 'blockchains_l2' for Layer 2 classification, `business_segment_id` set to 'blockchain' for segment categorization, and `product_id` set to null as this is a chain-level metric
- **Key fields**: `timestamp` for the daily boundary, `contract_deployers` containing the count of unique deployer addresses per day, and classification metadata fields for data organization

### Final aggregation
- **Combining components**: The daily aggregated data flows directly into the finalization process without additional combining steps, as the metric represents a single time series of daily deployer counts
- **Currency conversion**: Not applicable for this count-based metric
- **Time aggregation**: Data is aggregated to daily boundaries using timestamp truncation, with each day representing a complete 24-hour period in the blockchain's timestamp
- **Final calculation**: The final metric value is the count of distinct deployer addresses per day, processed through the finalize metric macro that applies standard formatting, ensures complete time series coverage by filling missing days with zero values using the 'fill_zeros' strategy, and applies chain availability filtering to ensure data quality standards are met. The result is a daily time series showing the number of unique addresses that deployed contracts on Boba Network each day.

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

Unique addresses that deployed at least one smart contract.

Boba NetworkBOBA

Contract deployers

Contract deployers

Competitive landscape

Chain breakdown