Upgrades
Track Injective network upgrades, governance proposals, and activation timelines.
Latest official binary: v1.20.4-bl.2 · darwin/arm64 · linux/amd64 · SHA256SUMS
Latest version feed (JSON): https://storage.googleapis.com/injective-chain-releases/status.json
Emergency rolling patch on the v1.20.4 line. No chain halt, governance proposal, or state migration. Mandatory for all mainnet nodes including sentries, RPC nodes, and exchange infrastructure; blocklist activated at block 184,950,000.
The Meridian Mainnet Upgrade advances Injective’s position as the premier blockchain for institutional-grade tokenization. It expands support for regulated...
This point release delivers a set of targeted chain improvements focused on strengthening network operations, improving market infrastructure, and enhancing...
This point release delivers a set of targeted chain improvements focused on strengthening network operations, improving market infrastructure, and enhancing...
This point release introduces a collection of targeted improvements to the Injective protocol, focused on enhancing network security, reliability, and...
The Vulcan chain upgrade marks one of the most significant releases in Injective's history, advancing the network into the definitive settlement layer for...
This proposal introduces the latest Injective mainnet application binary, delivering targeted upgrades across the native orderbook, exchange module, and...
This proposal introduces the latest Injective mainnet upgrade, purpose built to establish Injective as the definitive settlement layer for real time stablecoin...
This proposal introduces the latest Injective mainnet application binary, delivering targeted optimizations across Injective's MultiVM infrastructure, core...
This proposal significantly advances Injective’s native EVM and MultiVM architecture. The upgrade expands EVM interoperability across the shared liquidity...
This proposal aims to optimize the key capabilities of Injective's infrastructure to drive a superior experience for users and developers. If passed, this...
This proposal aims to optimize specific parameters of Injective to enhance the user and developer experience across the chain. If passed, this proposal will...
The Altria chain upgrade marks a major milestone for Injective, introducing permissionless EVM access and advancing the MultiVM architecture into a unified,...
This proposal aims to upgrade and optimize parameters of the Injective Mainnet with a focus on enhancing the new EVM stack. These improvements will provide a...
This proposal aims to further enhance the Injective network's performance and expand its capabilities, with the potential to increase the amount of INJ staked...
This proposal seeks to optimize the performance of the Injective blockchain, enabling faster transaction throughput and data handling. If passed, this...
The proposal here outlines the parameters for the Injective Ethernia Mainnet Upgrade. This upgrade proposal introduces unprecedented capabilities, features,...
This proposal outlines the parameters for the Injective Lyora Mainnet upgrade (v1.15.0). The Lyora chain upgrade proposal introduces several new capabilities,...
This is a software upgrade proposal for the Injective Mainnet Upgrade v1.14.1. If passed, this proposal would commit the Injective Chain to halt at block...
This is a software upgrade proposal for the Injective Nivara Mainnet Upgrade. If passed, this proposal would commit the Injective Chain to halt at block height...
This is a software upgrade proposal for the Injective Mainnet Upgrade (v1.13.2). If passed, this proposal would commit the Injective Chain to halt at block...
This is a software upgrade proposal for the Injective Altaris Mainnet Upgrade. If passed, this proposal would commit the Injective Chain to halt at block...
The proposal here outlines on a high level the parameters for the Injective Volan Mainnet upgrade.\n\nThis is a software upgrade proposal for the Injective...
How upgrades work: Major versions are activated via governance software upgrade proposals. The chain halts at the specified block height; validators switch to the new binary (via cosmovisor or manual restart) and consensus resumes. Binaries are published to injective-core releases.