35628595-6
Injective Veyra upgrade clears 99.51% vote before Nov. 24 halt
Injective says 99.51% of INJ stakers backed Proposal 717 for the Veyra v1.21.0 upgrade, targeting a Nov. 24 halt at block 193,145,000. Privacy and RFQ perpetuals are planned.

By Elena Vasquez
Injective said the Veyra mainnet upgrade had “passed governance,” with “99.51% of Injective (INJ) stakers” voting in favor. The upgrade scheduled for Tuesday, Nov. 24 will target a chain halt at block 193,145,000, according to the proposal details.
That approval moves the proposal toward execution, but it does not show that the planned features are already available or commercially active. Governance consent authorizes the upgrade; deployment, user adoption and institutional counterparties remain separate tests.
What did the vote actually show?
The vote opened Thursday, Nov. 12. A Friday, Nov. 13 snapshot put participation at 33.03%, roughly one in three stakers and below the 33.40% quorum threshold. At that stage, 70.91% of votes cast supported the proposal.
The interim tally listed 13,162,188 INJ in favor, 5,318,011 abstaining and 80,500 against. In reader-friendly terms, more than 13 million tokens supported the upgrade, while abstentions exceeded opposition by more than five million.
Injective’s later 99.51% approval figure was presented as the final result, but the published account gives no final participation rate, final token count or final vote breakdown. It also provides no on-chain explorer record, leaving the result attributable to Injective rather than independently documented within the cited material.
The practical conclusion is simple: Injective has a reported approval, but not enough disclosed vote data for an independent check.
What does Veyra add?
Proposal 717, identified as version 1.21.0, groups the upgrade under four headline areas: real-world assets, privacy, RFQ perpetual contracts and institutional finance. Earlier proposal details add an expanded enterprise gateway, real-world-asset infrastructure and native privacy through CypherOS.
- Real-world assets and enterprise access: The proposal includes real-world-asset infrastructure and an expanded enterprise gateway. It names no issuing assets, custody model, token standard or institutional partner.
- Privacy: Native privacy through CypherOS is planned. The source does not define the transaction scope, cryptographic mechanism or independent review, so the label alone does not establish the degree of confidentiality.
- RFQ perpetual contracts: The upgrade would add perpetual contracts using a request-for-quote format. It specifies no collateral rules, eligible venues, counterparty model or activation date.
- Cross-chain reach: The proposal includes expanded atomic swaps and Inter-Blockchain Communication between Injective’s EVM environment and connected networks. No specific destination chains or settlement assets are named.
The proposal’s business logic is to position Injective for tokenized assets and institutional trading flows. The gateway and cross-chain work target easier integration. Those are strategic directions, not signed deployments: no counterparties, assets, compliance jurisdictions, fee structures or revenue-sharing terms appear in the cited details.
Veyra broadens Injective’s product map; it does not yet establish an institutional revenue base.
What remains unproven before the halt?
Proposal 717 set the target chain halt at block 193,145,000 on Nov. 24, without specifying a time of day. The fixed height gives the network an ordered stopping point, but it does not give market participants a clear operating window.
At the target, block production is expected to stop while nodes transition to version 1.21.0, and the upgrade cannot be considered complete until blocks resume. The cited details do not say how long the halt should last or what happens if the upgrade stalls.
The materials also omit node upgrade instructions, client compatibility, test results, an audit and a rollback plan. Those omissions matter because governance approval tests authorization, not production readiness. The dates also omit the calendar year, preventing the schedule from being tied to a specific deadline without checking the proposal record.
The upgrade has a defined block target, but not a complete operating schedule.
Does the approval settle execution risk?
No. Every approval figure comes from Injective’s account, and the report cites no final on-chain record, signed release or independent validator assessment. The 99.51% result establishes staker support as reported by the company; it does not establish software quality, network uptime, liquidity or commercial demand.
The earlier 33.03% snapshot put participation below quorum, so final turnout is necessary to assess the breadth of support. The source omits that figure.
The next verifiable checkpoint is block 193,145,000 on Nov. 24. Delayed block production would expose execution risk, while resumed blocks would shift scrutiny to whether the promised RWA, privacy and RFQ features work in production.
via tokenpost.com (Source)
More from Elena Vasquez
Show full bio
Staff writer covering regulation, policy and their impact on crypto and web3 industry at Mempool Brief.
1,576 articles