Validators process transactions and receive transactions fees (supply-side fees).

Injective is a smart contract platform for decentralized finance applications (a blockchain) and an orderbook exchange protocol. Injective was founded by Eric Chen, Albert Chon etc. and launched in 2020. Note that this dashboard only tracks Injective's blockchain business.

INJ holders own and govern the protocol. They currently take a cut of the total transaction fees paid by users (revenue) via Burn Auctions. Injective's investors include Binance, Jump Crypto, Mark Cuban, etc.

github

twitter

discord

website

Blockchains (L1)

Injective

# Injective Contract deployers Methodology

## 1. Overview

The Injective contract deployers metric measures the daily number of unique addresses that deploy smart contracts on the Injective Cosmos network. This metric tracks developer activity and smart contract adoption by counting distinct deployer addresses per day. The calculation focuses specifically on Injective Cosmos contract creations, providing insight into the platform's development ecosystem growth and deployment activity.

## 2. Data sources

- **Injective Cosmos contract creation data**: Contract deployment records from the Injective Cosmos blockchain containing creation timestamps, deployed contract addresses, and deployer addresses
- **Blockchain transaction data**: Injective Cosmos network transaction logs that capture contract instantiation events and deployment activities

## 3. Step-by-step calculation

### Component A: Contract creation extraction
- **Purpose**: Extract and prepare contract deployment data from the Injective Cosmos network
- **Logic**: Retrieve all contract creation records from Injective Cosmos blockchain data, capturing the creation timestamp when each contract was deployed, the deployed contract address, and the deployer address that initiated the deployment. Apply distinct filtering to ensure each unique contract creation event is counted only once.
- **Key fields**: `creation_timestamp` (when contract was deployed), `contract_address` (deployed contract identifier), `deployer_address` (address that deployed the contract)

### Component B: Daily aggregation
- **Purpose**: Group contract deployments by day and count unique deployers
- **Logic**: Truncate the creation timestamps to daily boundaries to group all deployments within each calendar day. Count distinct deployer addresses within each day to identify unique contract deployers, ensuring that addresses deploying multiple contracts on the same day are counted only once. Add standardized metadata fields including chain identifier, market sector classification, business segment, and product identifier.
- **Key fields**: `timestamp` (daily boundary), `contract_deployers` (count of distinct deployer addresses per day)

### Final aggregation
- **Combining components**: The daily aggregation directly produces the final metric values without additional combining steps
- **Currency conversion**: Not applicable for this address-based metric
- **Time aggregation**: Contract creation timestamps are truncated to daily boundaries, with all deployments within a calendar day grouped together
- **Final calculation**: The final metric value represents the count of distinct addresses that deployed at least one contract on each given day. The finalization macro applies a fill zeros strategy to ensure continuous time series data, and chain availability filtering ensures data quality standards are maintained across the reporting period.

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

Unique addresses that deployed at least one smart contract.

InjectiveINJ

Contract deployers

Contract deployers

Competitive landscape

Chain breakdown