Injective's Veyra Upgrade Vote Tracks Below Quorum at 33.03%

Injective's on-chain governance vote on the Veyra upgrade drew 33.03% participation as of a Nov. 13 snapshot, falling just short of the 33.40% quorum the network requires for a valid result, according to the dated tally.

The count showed 13,162,188 INJ tokens voting yes, 5,318,011 abstaining and 80,500 voting against. Yes votes accounted for 70.91% of all votes cast. The snapshot did not record the exact time it was captured, so the figures represent a point-in-time reading rather than a final result.

What is Proposal 717 trying to do?

The ballot, Proposal 717, covers Veyra version 1.21.0, a protocol upgrade with three technical planks:

• Request-for-quote infrastructure, which would give traders a dealer-style execution model alongside Injective's existing orderbook mechanics.
• Expanded atomic swaps, broadening the protocol's direct asset-exchange capabilities.
• Inter-Blockchain Communication (IBC) connectivity between Injective's EVM environment and connected networks, tying the chain's Ethereum-compatible layer into the broader Cosmos IBC rails.

The operational stakes are concrete. If the proposal passes, Veyra targets a chain halt at block height 193,145,000, projected for Nov. 24. The proposal specifies an activation block, not a clock time — meaning validators and infrastructure operators must track block production themselves to coordinate the halt window.

Why does the quorum gap matter?

Governance participation is the binding constraint here. At 33.03% turnout against a 33.40% quorum, the vote sits roughly 0.37 percentage points below validity — a narrow deficit, but a binary one. A proposal can carry an overwhelming share of votes cast, as this one does at 70.91% yes, and still fail if total participation doesn't clear the threshold.

Abstentions cut both ways in this tally. They count toward quorum participation, which helps the proposal's viability, but they dilute the yes share of votes cast. With 5.3 million INJ abstaining against only 80,500 voting no, the abstain bloc is the second-largest constituency in the vote — a signal that token holders aware of the proposal are largely not objecting to it, even where they decline to endorse it.

The 80,500 INJ against represents less than 0.5% of tokens voted, an unusually thin opposition figure for a major protocol upgrade.

What happens next?

Voting closes Monday, Nov. 16. The gap between current turnout and quorum is small enough that a modest increase in participation — whether from yes votes or even further abstentions — would push the proposal over the line before the deadline.

If quorum is met and the vote passes, attention shifts to execution: validators must coordinate around block 193,145,000 for the Nov. 24 chain halt, and application teams building on Injective's EVM environment will need to prepare for the new IBC capabilities. If quorum fails, the upgrade returns to governance for a revised or resubmitted proposal, delaying the RFQ rollout and the expanded cross-chain functionality with it.