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 Contracts deployed Methodology

## 1. Overview

The Injective contracts deployed metric measures the total number of smart contracts deployed daily on the Injective Cosmos blockchain. This metric tracks developer activity and ecosystem growth by counting unique contract deployments. The calculation aggregates distinct contract creation events by day, providing insight into the development pace on Injective's Cosmos-based infrastructure.

## 2. Data sources

- **Injective Cosmos blockchain data**: Contract deployment records from the Injective protocol's Cosmos SDK implementation
- **Contract creation events**: Raw contract instantiation data including deployment timestamps, contract addresses, and deployer information
- **Blockchain infrastructure data**: Injective protocol transaction and block data containing contract deployment activities

## 3. Step-by-step calculation

### Component A: Contract creation extraction
- **Purpose**: Identifies and extracts all unique contract deployments from Injective Cosmos blockchain data
- **Logic**: Pulls distinct contract creation records to ensure each contract deployment is counted only once. Extracts the `creation_timestamp` as the deployment time, `contract_address` as the unique contract identifier, and `deployer_address` as the entity that deployed the contract
- **Key fields**: `creation_timestamp` for timing, `contract_address` for unique identification, `deployer_address` for deployment attribution

### Component B: Daily aggregation  
- **Purpose**: Groups contract deployments by day and counts the total number deployed each day
- **Logic**: Truncates deployment timestamps to day boundaries and groups all contract creations within each 24-hour period. Counts the total number of contracts deployed per day using aggregation. Adds metadata identifying this as Injective chain data categorized under L1 blockchains market sector and blockchain business segment
- **Key fields**: `timestamp` truncated to day grain, `contracts_deployed` as the daily count, chain and product identifiers

### Final aggregation
- **Combining components**: Daily contract deployment counts are processed through standard metric finalization
- **Currency conversion**: Not applicable - this is a count-based metric
- **Time aggregation**: Data is aggregated by day boundaries, with each day representing a 24-hour period of contract deployment activity
- **Final calculation**: The final metric value is the count of distinct contracts deployed on the Injective Cosmos blockchain for each day, with zero-filling applied for days with no deployments to maintain complete time series continuity

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

Unique smart contracts published onchain.

InjectiveINJ

Contracts deployed

Contracts deployed

Competitive landscape

Chain breakdown