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 Contract deployers Methodology

## 1. Overview

The contract deployers metric measures the daily number of unique addresses that deployed smart contracts on the Ink blockchain. This metric provides insights into developer activity and ecosystem growth by tracking how many distinct entities are creating new contracts each day. The calculation counts unique deployer addresses per day to avoid double-counting scenarios where a single address deploys multiple contracts within the same day.

## 2. Data sources

- **Ink blockchain contract creation events**: Raw contract deployment transaction data from the Ink Layer 2 blockchain, including deployer addresses, contract addresses, creation timestamps, and deployment transaction details
- **Contract deployment transaction traces**: Transaction trace data that captures the specific addresses and bytecode involved in contract creation processes
- **Blockchain metadata**: Chain-specific information for categorizing Ink as an L2 blockchain in the blockchains sector

## 3. Step-by-step calculation

### Component A: Contract creation data extraction
- **Purpose**: Extract and prepare all contract creation events from the Ink blockchain
- **Logic**: Pull contract creation records from Ink blockchain data, selecting distinct records to eliminate any potential duplicates. Extract key fields including creation timestamps, contract addresses, deployer addresses, trace addresses, contract bytecode, and creator addresses from raw contract deployment data.
- **Key fields**: `creation_timestamp` for timing, `contract_address` for the deployed contract, `deployer_address` for the entity creating the contract, `creation_trace_address` for transaction trace identification, `contract_bytecode` for the deployed code, and `creator_address` for the initiating address

### Component B: Daily aggregation and counting
- **Purpose**: Count unique contract deployers per day
- **Logic**: Truncate creation timestamps to daily boundaries to establish consistent time periods. Group all contract creation records by day and count distinct deployer addresses within each day. This approach ensures that if a single address deploys multiple contracts on the same day, it is counted only once as a unique deployer for that day.
- **Key fields**: `timestamp` truncated to day level, `deployer_address` for distinct counting, `contract_deployers` as the final count of unique deployers per day

### Final aggregation
- **Combining components**: The daily aggregated data is enhanced with standard metadata fields including chain identifier set to 'ink', market sector classification as 'blockchains_l2', and business segment designation as 'blockchain'
- **Currency conversion**: Not applicable for this count-based metric
- **Time aggregation**: Daily boundaries are established using timestamp truncation to day level, ensuring consistent 24-hour periods for counting
- **Final calculation**: Apply the finalize metric macro with a 'fill_zeros' strategy to ensure complete daily coverage, filling any missing days with zero values to maintain continuous time series data. Apply chain availability filtering to ensure data quality and completeness across the time range.

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

Unique addresses that deployed at least one smart contract.

Ink

Contract deployers

Contract deployers

Competitive landscape

Chain breakdown