Layer 1 blockchain
Injective ticker INJ
Summary
Cosmos SDK application chain (mainnet chain ID injective-1) using CometBFT consensus. INJ holders delegate to validators; the active set is capped at 45 by an on-chain staking parameter, and 45 validators were bonded on 2026-09-27. A block commits once validators holding more than 2/3 of voting power precommit it, assuming less than 1/3 is byzantine. Beside the usual modules the chain runs a protocol-level order-book exchange, an oracle module, CosmWasm contracts and, since 11 November 2025, an embedded EVM (chain ID 1776) that shares the same blocks and token balances. Mainnet ran node software v1.20.4 on 2026-09-27; its release notes say source code is no longer published from 9 September 2026. 34589121314
Design
- System
- Layer 1 blockchainIts own proof-of-stake chain (chain ID injective-1) secured by its own bonded validators; not a rollup and not a Cosmos Hub consumer chain. Some third-party pages still call Injective a Layer 2 application on Cosmos, which does not match the current design.
- Settlement family
- Cosmos SDK
- Scarce resource
- Stake (proof of stake)
- State model
- Accounts
- Finality
- Other
- Who makes blocks
- Validators selected round-robin in proportion to voting power, per the CometBFT consensus specification. Inside a block, a mempool lane system gives oracle transactions first priority, then transactions sent by exchange-module admins, then exchange-only transactions, then everything else.
- Fork choice
- No fork choice in the Nakamoto sense: a height is decided by +2/3 precommits. Per the CometBFT specification, two conflicting commits require more than 1/3 of voting power to double-sign or cast votes it cannot justify, and that group can be identified. On 2026-09-27 the chain's parameters set the stake penalty for double-signing to zero, so the consequence is jailing and permanent removal rather than loss of bonded stake.
Qualifications
- Ibc · Applies. IBC links Injective to other IBC chains through on-chain light clients; tokens arriving this way appear as ibc/ denominations. IBC is interchain messaging between separately secured chains, not a rollup, and is recorded under bridge support.
- Shared security · Not applicable. Injective is secured by its own bonded validator set with INJ as the bond token. It does not rent security from the Cosmos Hub, so Hub security properties do not carry over.
- Slashing · Partial. On 2026-09-27 Injective's own public endpoint and several independent ones all returned zero as the stake penalty for both double-signing and downtime. Validators that sign fewer than half of the last 100,000 blocks are jailed for 10 minutes, and double-signers are removed permanently, but bonded stake is not burned. When this setting was adopted was not found. The Ethereum bridge module also uses jailing rather than slashing.
- Finality · Partial. A block is final once validators with more than 2/3 of voting power precommit it, and blocks do not reorganise in normal operation. This profile does not count that as finality backed by stake: on 27 September 2026 the parameters took no stake for double-signing, and double-signers are removed permanently instead, so reverting a committed block would cost validators their seats, not bonded INJ.
- Settlement family · Partial. Injective is built with the Cosmos SDK, CometBFT and IBC, so it is grouped with Cosmos chains, but since November 2025 it also runs an embedded EVM (chain ID 1776) that shares the same blocks and balances, so EVM users see 0x addresses, EVM wallets and EVM contracts. It does not settle to Ethereum.
- Throughput · Unknown. No classified throughput figure from a primary source was recorded. Injective's homepage and blog report block-time figures of about 0.6 seconds, which describe block spacing, not transaction capacity.
- Source availability · Partial. The v1.20.4 release notes (18 September 2026) state that source code is no longer published from 9 September 2026, and the v1.20.4 tag on GitHub points to a commit containing only a file named to say the source is private. The newest release with published source is v1.20.3-safeharbor.2 (2 September 2026). Current mainnet releases can be run but not independently audited or rebuilt from source.
Tradeoffs
- Emphasizes
- Scalability
- Gives up
- Decentralization of who can validate and run nodes, and stake-backed security. The validator set is capped at 45, the docs ask for server-class machines (64 GB RAM or more even for a non-validating node), and from September 2026 node releases ship without published source, so operators cannot audit or rebuild what they run. Current parameters burn no stake for double-signing or downtime. Liveness also depends on more than 2/3 of voting power being online.Security is not listed as a design emphasis because current parameters take no stake for double-signing or downtime, so a safety violation costs validators their seats, not bonded INJ. Readers who count single-round BFT finality under a one-third fault assumption as a security emphasis may reasonably disagree. The liveness point is inferred from the +2/3 precommit rule.
- Full node at home
- Demanding 10111239Injective's hardware page sets a minimum for a non-validating RPC node of 64 GB RAM, 8 cores at 3.4 GHz, 1 TB NVMe or SSD and 1 Gbps networking (recommended: 128 GB, 16 cores, 2 TB); validators need 128 GB and 12 or more fast cores. The docs stress single-thread CPU speed, advise restoring from a snapshot instead of replaying from genesis, and warn that state sync does not restore contract data. New releases from 9 September 2026 ship as binaries and Docker images only; the public v1.20.4 tag holds a single placeholder file saying the source code is private.
- Throughput claims
- No classified figure recorded
Scaling layers
No scaling layer recorded in this profile.
Capabilities
| Capability | How it is provided | Notes and sources |
|---|---|---|
| Account abstraction | Structured assessment pending | Not yet assessed for any chain. |
| Atomic swaps | Built into the protocolLimited scope | Injective's exchange module runs a protocol-level order book: trades it matches between two traders settle both sides inside Injective's own state, so the swap does not rely on a custodian. Limit: same chain only; no cross-chain hash-locked swap mechanism was reviewed. 18 |
| Authenticated data publication | Unknown | Not yet assessed under this row's current definition. |
| Light clients | Built into the protocolLimited scope | CometBFT consensus produces the validator-signed commits that IBC light clients check. IBC relies on on-chain light clients that verify counterparty consensus; relayers carry proofs but are not trusted. The v1.20.1 changelog also wires in a light client for Cardano. Limited: this light verification serves IBC, where counterparty chains' on-chain light clients check Injective's commits; no light-client wallet or other user-facing light client for Injective itself was reviewed. 1320 |
| Native staking or delegation | Structured assessment pending | Not yet assessed for any chain. |
| On-chain governance | Structured assessment pending | Not yet assessed for any chain. |
| Parallel execution | Structured assessment pending | Not yet assessed for any chain. |
| Payment or state channels | Unknown | No payment or state channel layer anchored to Injective was reviewed. IBC channels are messaging paths, not payment channels. |
| Programmable spending | Native (protocol or core-team software) Earlier definition | Two contract environments share one chain. CosmWasm code uploads are restricted: Injective's guide routes them through a governance vote, and on 2026-09-27 the live parameters also allowed one listed account to upload code directly, while anyone may instantiate uploaded code. The embedded EVM (chain ID 1776) had live parameters allowing contract creation without a deployer allowlist. EVM contracts reach native balances through a bank precompile. 615161738 |
| Protocol-verified messaging | Structured assessment pending | Not yet assessed for any chain. |
| Reversible transfers or recovery | Unknown | Not yet assessed under the current definitions; the only related feature found is an issuer control: for permissioned assets the permissions module lets a token's namespace admin freeze sending or receiving and, through a super-burn role, burn balances held by other wallets. Issuer controls act on holders, not for them, so they do not count. No way for a sender to cancel or reclaim a payment, and no recovery path for ordinary INJ accounts, was verified. 19 |
| Rollups | Unknown | In March 2024 Injective announced inEVM live on mainnet: a rollup built with Caldera, using Celestia for data availability, with Hyperlane and LayerZero messaging. The announcement does not say where it settles, whether it still runs was not verified, and Hyperlane modules were deprecated from the chain in v1.20.0. The embedded EVM added in 2025 is part of the base chain, not a rollup. 131521 |
| Shielded transfers | Structured assessment pending | Not yet assessed for any chain. |
| Signed partial offers | Unknown | Not yet assessed under this row's current definition. |
Reading these values
- How this feature is provided
- Built into the protocol, core-team software or independent software says where a feature lives and who can change it. These are implementation layers, not quality: core-team software is not closer to the protocol than independent software.
- Structured assessment pending
- The shared review has not assessed this feature for any chain yet (Account abstraction, Native staking or delegation, On-chain governance, Parallel execution, Protocol-verified messaging and Shielded transfers). That does not mean it is absent, and a chain’s profile may already describe it.
- Unknown
- The review has not established this for this chain under the current definition; the note beside it says why. Unknown is not absent and not a low score. A feature reads “Not present” only when a source shows it is absent.
- Earlier definition
- Payment or state channels, Programmable spending and Rollups keep the earlier definition until the next fact-check. There, “Native” does not separate the protocol from core-team software, “Ecosystem software” does not say who publishes it, and “Partial” does not say which layer.
- Reading across rows
- The list of capabilities is incomplete. Do not read these rows as a chain leading or lagging overall.
Ecosystem & custody
| Product type | Status | Notes and sources |
|---|---|---|
| Automated market makers | UnknownAstroport (Injective mainnet contracts listed) | Injective's main trading venue is its protocol order book, which is not an automated market maker. Astroport's site lists Injective among its networks and its documentation lists Injective mainnet contracts. Liquidity and current activity were not measured, so the depth of AMM venues is unknown. 182240 |
| Issuer-native stablecoins | Established in the ecosystemUSDC (Circle) | Circle lists native USDC on Injective and CCTP V2 support (domain 29); Injective announced both live on 7 May 2026, usable from CosmWasm and the EVM. Tether's list does not include Injective, so USDT there is a bridged representation. 23242526 |
| Algorithmic stablecoins | Unknown | Algorithmic or hybrid stablecoins on Injective were not reviewed. |
| Bridges | Native to the protocolInjective Bridge (Peggy, to Ethereum), IBC, Circle CCTP (USDC), Wormhole | Peggy is a protocol module run by Injective validators with a contract on Ethereum; IBC connects IBC-enabled chains; CCTP moves native USDC. Injective's bridge page also names Wormhole, whose own listing was not verified here. Hyperlane modules were deprecated in v1.20.0. Risk: Peggy holds Ethereum-side deposits in one contract released on attestations from 2/3 of Injective voting power. The v1.17.0 changelog describes a no-slashing policy for the bridge, which jails misbehaving signers instead, and the live parameters list a single admin account, the same account allowed to upload contract code without a vote; how that admin power is used was not reviewed. IBC assets depend on the counterparty chain and client correctness. CCTP depends on Circle as issuer. 7132024272838 |
| Block explorers | Established in the ecosystemInjScan (Injective Explorer), Blockscout (Injective EVM), Mintscan | Injective's network page names injscan.com for mainnet and its EVM page names Blockscout; the Cosmos chain registry lists Mintscan and others. Listing is not a quality check; explorer data is provider-indexed. 1229 |
| Hardware wallets | Established in the ecosystemLedger, Trezor (through Injective Labs' app connector, not Trezor Suite) | See custody rows: Ledger lists Injective and its Ledger Wallet code defines an Injective account type. Trezor lists INJ only on other networks; a route for native Injective accounts runs through Injective Labs' own Trezor connector for apps and was not tested end to end. 30313537 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | Native supportSame as native: Unknown | Can: Use an Injective account in Ledger Wallet, which Ledger's code defines as a Cosmos-family chain using the Cosmos device app and Ethereum's coin type 60 Can: Stake INJ from Ledger Wallet: Ledger's Injective page mentions staking in general template wording, and Ledger's Injective code sets a 21-day unbonding period Can: Sign Injective transactions in Keplr with the Ledger Ethereum app (EIP-712 signing), per Injective's docs Cannot: Rely on gas estimation when signing through Keplr with a Ledger, per Injective's docsLedger's Injective page is a generic template that still calls Injective a Layer 2 application on Cosmos, and the Ledger Wallet integration sits behind a remotely controlled feature switch whose production setting was not checked; whether every Ledger Wallet user sees Injective today was not confirmed. 3031323334 |
| Trezor | Through an intermediaryApps using Injective Labs' Trezor connector, which signs Injective transactions through Trezor's Ethereum typed-data signingSame as native: No | Can: Sign native Injective transactions with a Trezor in apps that use Injective Labs' Trezor connector, whose published example sends INJ on Injective (not tested end to end here) Cannot: Manage native Injective (injective-1) accounts in Trezor Suite; Trezor's page lists INJ only on Ethereum, BNB Smart Chain and inEVM Cannot: Treat INJ token representations on those networks as custody of Injective-chain INJTrezor's own page does not list the Injective chain. This route rests on Injective's wallet docs, which list Trezor among the Ethereum wallets they support, and on Injective Labs' own connector package; it depends on Injective Labs' software rather than Trezor Suite and was not tested end to end. 353637 |
Public data
iKnow Blockchain has no public-data lookups for Injective yet. This is a limit of the service, not a statement about the network.
| Lookup | Status | What it covers and its limits |
|---|---|---|
| Address or account | Not available yet | Public-data lookups for this chain are not built yet. |
| Tokens and assets | Not available yet | Public-data lookups for this chain are not built yet. |
| NFTs | Not available yet | Public-data lookups for this chain are not built yet. |
| Transactions | Not available yet | Public-data lookups for this chain are not built yet. |
Sourced developments
Developments: Review overdue Reviewed Sep 27, 2026; next review was due Oct 7, 2026, 12:00 UTC.
Publication date · newest first
-
Injective node releases stopped publishing source code
The release notes for injective-core v1.20.4, a mainnet upgrade published on 18 September 2026, state that source code is no longer published starting 9 September 2026, and the v1.20.4 tag points to a placeholder commit saying the source is private. Binaries and Docker images are still provided, and a public mainnet node reported running v1.20.4 on 27 September 2026.
- Implementation:v1.20.4 binaries released without source
- Release:released 2026-09-18
- Activation:v1.20.4 reported by a public mainnet node on 2026-09-27
Sources: InjectiveFoundation/injective-core on GitHub — Injective v1.20.4 Mainnet Upgrade (release notes) (external site) · InjectiveFoundation/injective-core on GitHub — Commit behind the v1.20.4 tag (external site) · Injective Labs (public sentry node) — Node info (injective-1 public REST endpoint) (external site) · InjectiveFoundation/injective-core on GitHub — injective-core releases (external site)
-
Injective USDC announced as the successor to Noble USDC across Cosmos chains and dYdX
Injective said Noble USDC holders could migrate to Circle-issued USDC on Injective through Skip:Go from 11 September 2026, and that dYdX would adopt it as the sole eligible trading collateral on dYdX Chain. The post gives 13 October 2026 as the date Circle Mint stops new USDC minting to Noble and 13 January 2027 as the end of Circle Mint and CCTP access for Noble.
- Proposal:announced migration plan
- Implementation:migration flow announced to open on 11 September 2026
- Release:in progress according to the announcement
- Activation:Noble minting stop scheduled for 13 October 2026; not yet observed
Sources: Injective — Injective USDC Becomes the Canonical Standard Across Cosmos & dYdX (external site) · Injective — Injective USDC will be Adopted by Cosmos and dYdX as the Canonical Stablecoin Standard (external site)
-
Circle-issued USDC and CCTP went live on Injective mainnet
Injective announced that USDC issued by Circle and Circle's Cross-Chain Transfer Protocol were live on mainnet, usable from both CosmWasm and the EVM. Circle's pages list an Injective USDC address and Injective as CCTP V2 domain 29.
- Implementation:issued by Circle on Injective mainnet
- Release:announced live
- Activation:listed by Circle as of 2026-09-27
Sources: Injective — USDC and CCTP live on Injective mainnet (external site) · Circle — USDC contract addresses (external site) · Circle — CCTP supported blockchains (external site) · Injective — USDC migration guide (external site)
-
v1.17.2 mainnet patch released: fee-collector fees redirected to the auction module, plus exchange and EVM fixes
Injective published v1.17.2 as a mainnet patch upgrade on 17 December 2025. Its release notes say proposal 603 would halt the chain at block 146,295,000, around 14:00 UTC on 18 December 2025, and restart it on v1.17.2. The changelog lists one feature, sending all fees meant for the fee collector to the auction module, and fixes to futures settlement, exchange validation, Ledger signing in the command-line tool and EVM log indexes.
- Proposal:proposal 603 set the halt at block 146,295,000; its vote result was not read from a primary governance record in this review
- Implementation:v1.17.2 node and Peggo binaries published; open-source commit c7b042e dated 18 December 2025
- Release:released 17 December 2025
- Activation:scheduled for block 146,295,000 (about 14:00 UTC, 18 December 2025); activation not confirmed from a primary chain or governance record here
Sources: InjectiveLabs/injective-chain-releases on GitHub — Injective v1.17.2 Mainnet Patch Upgrade (release notes) (external site) · InjectiveFoundation/injective-core on GitHub — injective-core CHANGELOG (tag v1.20.3-safeharbor.2) (external site) · InjectiveFoundation/injective-core on GitHub — injective-core commit c7b042e: Release of new version (v1.17.2) (external site) · InjectiveLabs/injective-chain-releases on GitHub — injective-chain-releases releases (external site)
-
Native EVM went live on Injective mainnet with the v1.17.0 upgrade
Injective's embedded EVM (chain ID 1776) launched on mainnet on 11 November 2025. The v1.17.0 upgrade, approved as IIP 583, was scheduled for block 141,150,000 at 14:00 UTC that day. EVM contracts run in the same blocks as CosmWasm and the native modules and share token balances through the MultiVM Token Standard.
- Proposal:approved as IIP 583
- Implementation:shipped in injective-core v1.17.0
- Release:Released
- Activation:active on mainnet since 11 November 2025
Sources: Injective — Welcome to the Injective Era: Native EVM Mainnet Launch (external site) · Injective Docs — Upgrade to v1.17.0 (external site) · InjectiveFoundation/injective-core on GitHub — injective-core CHANGELOG (tag v1.20.3-safeharbor.2) (external site)
Topics your AI can explain
Your AI can explain these topics for Injective through the connection, with sources.
Known gaps
What this profile's review did not establish:
- When and why the stake penalties for double-signing and downtime were set to zero was not found in governance proposals or release notes.
- No classified throughput figure from a primary source was recorded; only block-time figures from Injective's own pages and a short block sample were seen.
- Whether the inEVM rollup still operates, and where it settles, was not verified.
- AMM liquidity and activity were not measured; Astroport's listing shows deployment, not use.
- Wormhole's own listing of Injective support was not verified; only Injective's bridge page names it.
- Ledger Wallet's production feature-switch setting for Injective and Ledger's support articles (which did not render) were not checked.
- The Trezor route through Injective Labs' connector was not tested end to end, and which current apps offer it was not confirmed.
- Who controls the single account that is both the Ethereum bridge admin and the only direct CosmWasm code uploader was not established.
- Algorithmic stablecoins, payment or state channels, and cross-chain hash-locked swaps were not reviewed.
- The impact of unpublished node source code on third-party audits and independent builds was not assessed beyond the release notes and the placeholder v1.20.4 tag.
Sources
Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.
- Network Information (external site)
- EVM Network Information (external site)
- Staking parameters (injective-1 public REST endpoint) (external site)
- Slashing parameters (injective-1 public REST endpoint) (external site)
- Node info (injective-1 public REST endpoint) (external site)
- EVM module parameters (injective-1 public REST endpoint) (external site)
- Peggy module parameters (injective-1 public REST endpoint) (external site)
- Byzantine Consensus Algorithm (external site)
- lanes (external site)
- Hardware Requirements (external site)
- Join a network (external site)
- Injective v1.20.4 Mainnet Upgrade (release notes) (external site)
- injective-core CHANGELOG (tag v1.20.3-safeharbor.2) (external site)
- Welcome to the Injective Era: Native EVM Mainnet Launch (external site)
- EVM Equivalence (external site)
- MultiVM Token Standard (external site)
- Mainnet Deployment Guide (CosmWasm) (external site)
- Trading (external site)
- Permissions module: Key Concepts (external site)
- IBC overview (external site)
- Injective Launches inEVM On Mainnet (external site)
- Astroport Contract Addresses (external site)
- USDC contract addresses (external site)
- CCTP supported blockchains (external site)
- USDC and CCTP live on Injective mainnet (external site)
- Supported Protocols (external site)
- Ethereum Bridge (external site)
- Bridge (external site)
- Injective chain registry record (external site)
- Injective wallet (external site)
- Ledger Wallet currency definition: injective.ts (external site)
- Ledger Wallet Cosmos-family chain class: Injective.ts (external site)
- Ledger Wallet feature switch: currencyInjective.ts (external site)
- Ledger through Keplr Wallet Transaction (external site)
- Injective (INJ) wallet (external site)
- Wallet (external site)
- Injective Protocol - Trezor Wallet Strategy (README for @injectivelabs/wallet-trezor) (external site)
- CosmWasm code-upload parameters (injective-1 public REST endpoint) (external site)
- Commit behind the v1.20.4 tag: "starting from 09-09-2026 source code is private" (external site)
- Astroport (external site)
Report an error
Found something wrong or out of date? Reporting is free, and every chain goes through the same process. Published corrections appear in the public log.
Funding disclosure
Funding disclosures appear here when an upkeep arrangement exists, in the form “Upkeep funded by [name]; verdicts unaffected.” The funder ledger has not been published yet. Neutrality & funding