website

twitter

Blockchains (L1)

Plasma

# Plasma Contracts deployed Methodology

## 1. Overview

The contracts deployed metric for Plasma measures the daily count of new smart contracts deployed on the Plasma blockchain. This metric tracks blockchain development activity by counting each unique contract creation event per day. The calculation uses a straightforward aggregation approach that counts all contract deployments within daily time boundaries, providing insight into developer activity and platform growth on the Plasma network.

## 2. Data sources

The metric relies on the following raw data sources:
- **Plasma blockchain data**: Contract creation events captured from Plasma blockchain transactions and traces
- **Block timestamps**: Plasma block timestamps used for daily time boundary calculations  
- **Transaction traces**: Plasma transaction execution traces that identify contract creation operations
- **Contract metadata**: Deployed contract addresses, bytecode, deployer addresses, and creator addresses
- **Chain availability data**: Data quality filters to ensure complete blockchain data coverage

## 3. Step-by-step calculation

### Component A: Contract creation extraction
- **Purpose**: Identifies and extracts all contract creation events from Plasma blockchain data
- **Logic**: Sources contract creation data directly from Plasma blockchain records, capturing key details about each deployment including the `creation_timestamp`, `contract_address`, `deployer_address`, `creation_trace_address`, `contract_bytecode`, and `creator_address`. Applies deduplication using distinct selection to ensure each contract creation is counted only once, preventing double-counting from potential duplicate records in the source data.
- **Key fields**: `creation_timestamp` for timing, `contract_address` for unique contract identification, `deployer_address` and `creator_address` for deployment attribution

### Component B: Daily aggregation
- **Purpose**: Groups contract creations by day and counts the total deployments
- **Logic**: Takes the deduplicated contract creation data and truncates the `creation_timestamp` to daily boundaries using day-level timestamp truncation. Groups all records by the truncated timestamp and applies a count aggregation to determine the total number of contracts deployed each day. Adds standard metadata fields including `chain_id` set to plasma, `market_sector_id` set to blockchains_l1, `business_segment_id` set to blockchain, and `product_id` set to null.
- **Key fields**: `timestamp` (daily boundaries), `contracts_deployed` (daily count), classification metadata fields

### Final aggregation
- **Combining components**: The daily contract counts are processed through the finalize_metric_contracts_deployed macro which standardizes the output format and applies gap-filling logic to ensure continuous time series data with zeros for days that had no contract deployments
- **Currency conversion**: Not applicable - this is a count-based metric that does not require currency conversion
- **Time aggregation**: Uses daily time boundaries with timestamp truncation to day level, ensuring each contract deployment is attributed to the correct calendar day based on block timestamp
- **Final calculation**: The final metric value represents the total count of unique contracts deployed on the Plasma blockchain for each day, with missing days filled with zero values to maintain complete time series continuity. Chain availability filtering is applied to ensure data quality and completeness.

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

Unique smart contracts published onchain.

PlasmaXPL

Contracts deployed

Contracts deployed

Competitive landscape