Ink batches users' transactions and submits them to Ethereum, paying a share of the transaction fees to Ethereum validators (expense).

Ink is an Ethereum Layer 2 (L2) blockchain built on Optimism's Superchain, focused on providing a secure, scalable infrastructure for Web3 applications.

Kraken team owns and governs the protocol. Kraken's investors include RIT Capital Partners, Hummingbird Ventures, Money Partners Group, etc.

github

website

twitter

discord

Blockchains (L2)

# Ink Contracts deployed Methodology

## 1. Overview

The Ink contracts deployed metric measures the daily number of smart contracts deployed on the Ink blockchain. This metric provides insight into developer activity and platform adoption by counting unique contract creation events that occur each day. The calculation aggregates contract deployment transactions from Ink blockchain data, applying deduplication logic and standardized time boundaries to produce consistent daily counts.

## 2. Data sources

- **Ink blockchain transaction traces**: Transaction execution traces from the Ink blockchain that contain contract creation operations and deployment details
- **Contract creation events**: Parsed contract deployment events including creation timestamps, contract addresses, deployer addresses, and contract bytecode
- **Blockchain metadata**: Block timestamps and trace addresses for precise transaction timing and identification

## 3. Step-by-step calculation

### Component A: Contract creation extraction
- **Purpose**: Identify and deduplicate contract creation events from Ink blockchain data
- **Logic**: Extract distinct contract creation records from Ink blockchain transaction traces. Each record includes the `creation_timestamp` when the contract was deployed, the `contract_address` of the newly created contract, the `deployer_address` that initiated the deployment, the `creation_trace_address` for transaction tracing, the `contract_bytecode` of the deployed contract, and the `creator_address`. The distinct operation removes any duplicate contract creation records that might exist in the raw blockchain data due to data processing or indexing issues.
- **Key fields**: `creation_timestamp` for timing, `contract_address` for unique contract identification, `deployer_address` and `creator_address` for deployment attribution, `contract_bytecode` for contract content verification

### Component B: Daily aggregation
- **Purpose**: Group contract creations by day and count deployments per day
- **Logic**: Truncate the `creation_timestamp` to daily boundaries using day-level precision, removing hour, minute, and second components. Group all contract creation records by the truncated timestamp and apply a count operation to determine how many contracts were deployed each day. Add metadata fields including `chain_id` set to 'ink' to identify the blockchain, `market_sector_id` set to 'blockchains_l2' to categorize Ink as a Layer 2 blockchain, `business_segment_id` set to 'blockchain' for business categorization, and `product_id` set to null since this is a chain-level metric rather than a specific product metric.
- **Key fields**: `timestamp` truncated to daily boundaries, `contracts_deployed` containing the daily count of new contracts

### Final aggregation
- **Combining components**: The daily contract deployment counts are processed through a standardization macro that applies consistent formatting and fills missing days with zero values
- **Time aggregation**: Daily time boundaries are maintained throughout the calculation, with timestamps truncated to day precision to ensure consistent daily reporting
- **Data quality**: Chain availability filtering is applied to exclude time periods where Ink blockchain data may be incomplete or unreliable, ensuring the metric only includes periods with complete data coverage
- **Final calculation**: The final metric represents the total number of unique smart contracts deployed on the Ink blockchain each day, with missing days filled as zero to maintain continuous time series data

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

Unique smart contracts published onchain.

Ink

Contracts deployed

Contracts deployed

Competitive landscape

Chain breakdown