6ba8d419-8
Injective’s Veyra Upgrade Clears Vote Before Nov. 24 Chain Halt
Injective says Proposal 717 passed with 99.51% support. The Veyra v1.21.0 upgrade targets block 193,145,000 on Nov. 24 for privacy, real-world assets and RFQ perpetuals.

Outputs
99.51% of INJ stakers voted in favor of the Veyra mainnet upgrade.
Proposal 717, version 1.21.0, targets a chain halt at block 193,145,000 on Nov. 24.
The Nov. 13 snapshot showed 33.03% participation, below the 33.40% quorum threshold, and 70.91% support.
The interim tally listed 13,162,188 INJ in favor, 5,318,011 abstaining and 80,500 against.
Veyra covers real-world-asset infrastructure, CypherOS privacy, RFQ perpetuals, institutional finance, atomic swaps and IBC.
“99.51% of INJ stakers voted in favor,” Injective said of the Veyra mainnet upgrade, which passed governance as Proposal 717. Injective scheduled a chain halt at block 193,145,000 on Tuesday, Nov. 24. The proposal carries version 1.21.0.
What did voters approve?
Proposal 717 bundles network capability, privacy and market-structure changes into one release, giving the scheduled halt a defined technical purpose.
- Real-world-asset infrastructure, paired with an expanded enterprise gateway.
- Native privacy through CypherOS.
- Request-for-quote, or RFQ, perpetual contracts.
- Institutional-finance features.
- Expanded atomic swaps.
- Inter-Blockchain Communication (IBC) between Injective’s EVM environment and connected networks.
The vote approves a broad release rather than a single market change. Its scope connects protocol-level privacy, perpetual contracts and cross-network operation, while the enterprise gateway and real-world-asset infrastructure address a distinct institutional use case.
The naming matters because the proposal does not confine the upgrade to one chain or one product. Native privacy and perpetual contracts sit at the application layer, while atomic swaps and IBC concern cross-network operation. The enterprise gateway and institutional-finance label point to a separate route for larger users, even though the disclosure names no counterparties.
How did the vote clear quorum?
The early figures explain why the result was not a foregone conclusion. The vote opened Thursday, Nov. 12, and a Friday, Nov. 13 snapshot showed participation at 33.03%, below the 33.40% quorum threshold, with 70.91% of votes cast favoring the upgrade at that point.
The interim tally listed 13,162,188 INJ in favor, 5,318,011 abstaining and 80,500 against. The completed vote produced a far higher approval rate, though Injective’s disclosed result did not include a final token-by-token tally or a final participation figure.
Participation had not reached quorum in the first disclosed snapshot, even though a clear majority of recorded votes supported the proposal. The final 99.51% result shows that later voting carried it through, but the disclosure cannot show how many tokens ultimately abstained.
Quorum determines whether the vote can decide the proposal, not just whether supporters outnumber opponents. At the Nov. 13 snapshot, the approval share was substantial but participation remained insufficient. The later 99.51% result resolved that procedural gap, although it did not reveal final turnout.
What changes for traders and institutions?
For traders, the practical change is a planned RFQ perpetual-contract format alongside privacy through CypherOS and expanded atomic swaps. For institutions, the proposal adds real-world-asset infrastructure, an expanded enterprise gateway and institutional-finance features. IBC links those functions to connected networks through Injective’s EVM environment.
The vote does not establish immediate adoption. It names no real-world assets, institutions or connected networks, and it provides no launch time beyond the target halt. Traders, applications and infrastructure providers therefore need to treat execution at the target block, rather than the calendar date alone, as the operational condition.
Operationally, the chain halt is the immediate point to watch. Injective scheduled the halt for block 193,145,000 without specifying a time of day, and the proposal did not state how long the network would remain stopped.
The next concrete checkpoint is Nov. 24: the chain must reach and halt at block 193,145,000, then deliver v1.21.0 and the approved feature set if the upgrade proceeds as scheduled.
via tokenpost.com (Source)
More from Marcus Bennett
Show full bio
Senior reporter covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.
1,512 articles