Injective Governance Proposal 717 Hits Quorum, Vote Ends Nov 16
Injective governance proposal 717 reached 39.11% turnout against 33.40% quorum. Voting on the Veyra v1.21.0 upgrade ends Nov 16, 2026. See the tally and plan.

Injective governance proposal 717, the Veyra Mainnet Upgrade to v1.21.0, has already reached quorum, with turnout of 39.11% against the required 33.40%. Voting continues until 16:53 UTC on November 16, 2026.
Injective governance proposal tally on November 15
This proposal has been submitted on November 12, 2026, with 100 INJ deposit, and the voting period is for four days. Quorum is 33.4% for chain parameters, so the vote is valid once turnout is above that level.
The Injective chain has 14,528,766 INJ saying Yes, 7,364,446 INJ Abstain, and 80,589 INJ saying No. Less than 1 INJ is being voted in the form of a veto. The proposal's page on Mintscan also reflects these figures and indicates the outcome as "Will PASS."
The yes share is 66.12%, calculated by Mintscan, as it takes into account the abstentions in the calculation as well. Considering the passing criteria of yes/no/veto, the yes share is almost 99.4%. The chain parameters set the pass threshold at 50% for yes and the veto threshold at 33.4%.
What the Injective governance proposal contains
The Injective governance proposal summary covers several topics. First, the new IBC interoperability to facilitate asset transfer from Injective's EVM to the entire interchain is discussed. There is an intention to develop the infrastructure for request for quote as well as expanding atomic swaps.
Moreover, it is an extension of the last Meridian update, which paves the way for CypherOS, which, according to the summary, is Injective's next native privacy platform.

Mintscan page of Injective proposal 717 (Veyra Mainnet Upgrade, v1.21.0), with turnout of 39.11% against quorum of 33.40% and 14,528,765 INJ voting yes. Source: Mintscan, Injective proposal 717.
The halt planned for November 24
In this proposal, the chain is expected to halt at block height 193,145,000. This is expected to take place on November 24, 2026. After this date, the chain will continue running under the v1.21.0 version of the Injective chain.
The time when this occurs is dictated by the block height, with the date merely being a target. The validators have to be running the updated code by that particular block height, hence the precise timing will depend on block generation.
Why the turnout figure matters
Only staked INJ can participate in voting. There are about 56.18 million INJ in staking pool on the network, and out of those only 21.97 million have voted, making it 39.11% of the staking pool. Quorum for the vote is set to 33.4%, hence the vote has passed with a margin of about 5.7 points.
Votes can still change until the window closes. A no vote would decide the result only if it grew large enough to push the yes share below 50%, and a veto would need 33.4%. At the percentages read on November 15, both are insignificant compared to the yes votes.
The data were taken from the Injective blockchain and Mintscan at the morning of November 15, 2026 (UTC) and will be continually updated until the end of the voting. The current document provides an overview of the governance history and is not investment advice for INJ.
Related News

WLD Flush Takes Price Into A $0.5375 Gap After 180M Volume Day
The WLD flush on October 22 followed a 180M-token volume day and broke the 4h structure at $0.5655. Closed-candle levels and two 4h-close paths inside.

Binance Hack: $2.84B Frozen, $3.33B Out Of Issuers' Reach
Binance hack update: Elliptic counts $2.84B frozen and $3.33B beyond issuers' reach, and we verified the 1.615B USDT Ethereum leg on the chain itself.

Memecoin Market Share Sinks Below 3% Of Altcoin Value
Memecoin market share fell below 3% of altcoin market cap, CryptoQuant's Darkfost says, and Binance selling hit $1.4B. CoinGecko data shows about 2.6%.

Lighter Exchange Pauses Withdrawals After Security Incident
The Lighter exchange paused all withdrawals and pool creation on Nov 16, 2026 after a security incident. See what it confirmed and what its docs say on exits.