Injective Opens Vote on Veyra Upgrade Proposal IIP-717

Injective opened a governance vote on proposal IIP-717 for the Veyra mainnet upgrade, with $INJ stakers able to vote until Monday and a target activation date of November 24 if the proposal passes. ChainCatcher, which reported the vote, describes Veyra as “the last major upgrade for the network in 2026.”

The sequence has two distinct dates. Monday is the voting cutoff; November 24 is a proposed activation target, not an automatic rollout. That distinction matters for operators who need to separate approval of a mainnet upgrade from the operational availability of its features.

What does Veyra change for traders and institutions?

Veyra’s first stated function is cross-chain asset movement. The proposal would let assets travel between Injective’s EVM environment and other connected chains. For practitioners, this places Veyra at the connection point between Injective and external networks rather than limiting the release to changes contained within one environment.

The proposal combines five principal components:

• Cross-chain movement: Assets could move between Injective’s EVM environment and other connected chains.
• RFQ execution: Large traders could ask for prices on sizeable deals instead of placing orders directly into an open market.
• RWA infrastructure: Veyra aims to introduce institutional-grade real-world asset infrastructure.
• Enterprise gateways: The upgrade would expand the network’s enterprise gateways.
• Privacy foundation: CypherOS would provide the foundation for native-privacy work, according to ChainCatcher.

The RFQ component inserts a quote request into the large-trade workflow. It gives a trader a way to seek a price for a sizeable deal before using direct open-market order placement, which is the operational distinction described in the report.

The source does not name quote providers, minimum sizes or settlement arrangements, so the feature set cannot yet support detailed execution planning.

The RWA and gateway elements extend the proposal beyond a trading interface. ChainCatcher describes institutional-grade RWA infrastructure and expanded enterprise gateways, pairing real-world asset support with broader gateway coverage.

The report does not identify specific assets or gateway operators. Institutional scope therefore remains a stated objective rather than a disclosed deployment list, and institutions have no named counterparties or asset set with which to model adoption.

The privacy element carries a narrower claim. ChainCatcher says Veyra lays the foundation for native privacy through CypherOS rather than establishing the full privacy specification. The report does not state which transactions, assets or user groups would receive privacy protections, leaving the scope of the November target undefined.

Taken together, Veyra links transfer availability, large-deal pricing, institutional infrastructure and privacy development within one upgrade. That combination matters because each component addresses a different operational layer: moving assets, finding a price, supporting real-world asset infrastructure or extending native-privacy functionality.

Approval path and launch watchpoints

The voting window ends Monday, while a yes result would set November 24 as Veyra’s target activation date. ChainCatcher’s 2026 designation makes IIP-717 a late-year decision for anyone monitoring Injective’s development schedule. Approval would establish the target rather than prove launch readiness.

The report gives no turnout figure, vote threshold, implementation breakdown or list of connected chains. Three uncertainties remain for users: whether participation meets the required approval standard, whether development reaches the target date and which components ship at activation. The report supports the existence of the vote and target date, not their completion.

For traders and institutions, the immediate action is to vote before Monday if they hold $INJ and seek to influence the outcome. The practical change is conditional: a yes vote advances an upgrade intended to combine cross-chain transfers, RFQ execution, RWA infrastructure, expanded enterprise gateways and CypherOS-based privacy work.

The next observable checkpoints are the Monday result and progress toward the proposed November 24 activation, when stakeholders can assess whether those five components move together from proposal status to operating infrastructure.