github

twitter

discord

website

Blockchains (L2)

Rootstock

# Rootstock Contracts deployed Methodology

## 1. Overview

The number of unique smart contracts published onchain is measured by Contracts deployed. This metric is utilized as a proxy for the amount of new infrastructure or applications that are launched on Rootstock. Developer activity and ecosystem growth are reflected through the systematic tracking of these deployment events.

## 2. Data sources

- **Blockchain events**: Contract creation metadata and deployment traces covering Rootstock

## 3. Step-by-step calculation

### Component A: Identification of unique deployments

- **Purpose**: Identify and extract unique smart contract creation events from the blockchain.
- **Logic**: Successful contract deployments are retrieved from onchain traces. Distinct records are identified by filtering for unique combinations of contract addresses, deployer addresses, and creation timestamps. This ensures that each unique instance of a deployed contract is captured exactly once within the dataset.
- **Key fields**: `block_timestamp`, `account_address`, and `deployer_address`.

### Component B: Daily aggregation and normalization

- **Purpose**: Consolidate individual deployment records into a daily time-series format.
- **Logic**: Deployment events are grouped by truncating block timestamps to daily intervals. The total number of contracts deployed is calculated by summing the unique occurrences per day. The resulting values are cast to a standardized numeric format.
- **Key fields**: `timestamp`, `contracts_deployed`.

### Component C: Finalization and zero-filling

- **Purpose**: Ensure data continuity and filter for chain availability.
- **Logic**: The daily counts are processed through a finalization macro to align with standard market sector and business segment dimensions. A zero-filling strategy is applied to ensure that days with no deployment activity are represented as zero rather than missing values. Data is further filtered to correspond with verified chain availability periods.
- **Key fields**: `timestamp_grain`, `data_id`, and `chain_id`.

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

Unique smart contracts published onchain.

RootstockRIF

Contracts deployed

Contracts deployed

Competitive landscape