website

twitter

discord

github

Blockchains (L1)

Berachain

# Berachain Contracts deployed Methodology

## 1. Overview

This metric measures the number of smart contracts deployed on the Berachain blockchain per day. It provides insight into development activity and ecosystem growth by tracking when new contracts are created on the network. The calculation counts unique contract deployments aggregated by daily time boundaries, with zero-filling applied to ensure continuous daily data series.

## 2. Data sources

The metric relies on the following raw data sources:
- **Berachain transaction traces**: Blockchain transaction execution traces that capture contract creation operations
- **Berachain contract creation events**: Parsed contract deployment events containing deployment timestamps, contract addresses, and deployer information
- **Berachain block data**: Block timestamp information used to determine when contract deployments occurred

## 3. Step-by-step calculation

### Component A: Contract creation extraction
- **Purpose**: Identifies and extracts all contract creation events from Berachain blockchain data
- **Logic**: The system pulls contract creation records from Berachain blockchain traces, capturing key information about each deployment including the `creation_timestamp`, `contract_address`, `deployer_address`, `creation_trace_address`, `contract_bytecode`, and `creator_address`. A distinct clause ensures that each contract creation is counted only once, removing any potential duplicates from the raw blockchain data.
- **Key fields**: `creation_timestamp` (when the contract was deployed), `contract_address` (address of the newly deployed contract), `deployer_address` (address that deployed the contract)

### Component B: Daily aggregation
- **Purpose**: Groups contract deployments by day and counts the total number deployed
- **Logic**: The system truncates the `creation_timestamp` to daily boundaries using day-level timestamp truncation. All contract creations within the same day are grouped together and counted using a count aggregation. Standard Token Terminal metadata is added including `chain_id` set to 'berachain', `market_sector_id` set to 'blockchains_l1', and `business_segment_id` set to 'blockchain'. The `product_id` is set to null as this is a chain-level metric.
- **Key fields**: `timestamp` (truncated to day), `contracts_deployed` (count of contracts deployed that day)

### Final aggregation
- **Combining components**: The daily contract counts are processed through Token Terminal's standard metric finalization macro
- **Currency conversion**: Not applicable for this count-based metric
- **Time aggregation**: Data is aggregated to daily boundaries with a 'fill_zeros' strategy applied to ensure days with no contract deployments show zero rather than missing values
- **Final calculation**: The final metric value is the count of unique contracts deployed per day, with gaps filled using zero values and filtered based on Berachain's data availability windows

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

Unique smart contracts published onchain.

BerachainBERA

Contracts deployed

Contracts deployed

Competitive landscape