Thursday, November 19, 2026

Injective Opens Veyra Upgrade Vote for November 24

Close-up of an institutional trading gateway UI with RFQ tools and on-chain tokenized assets, subtle CypherOS cue.

Injective Opens Veyra Upgrade Vote for November 24

Injective has opened governance voting on Veyra, its final major network upgrade planned for 2026, with a mainnet transition targeted for November 24 if the proposal passes. According to the official Injective upgrade tracker, Proposal 717 would move the chain to v1.21.0 at block 193,145,000. Veyra combines new institutional trading infrastructure, expanded cross-chain connectivity and groundwork for Injective’s future native privacy stack. The upgrade remains a governance proposal and none of its new components should be treated as active on mainnet yet.

The proposal builds on Injective Institutional Rail and the earlier Meridian upgrade, which introduced regulated token controls and initial privacy-oriented RFQ infrastructure. Veyra extends that architecture rather than replacing it, with the stated objective of supporting issuance, distribution, trading and settlement of tokenized financial assets. Injective describes the upgrade as infrastructure for institutional RWA markets, although those technical capabilities do not by themselves demonstrate institutional usage or asset inflows.

RFQ and Atomic Swaps Expand Trading Infrastructure

One of Veyra’s main additions is new request-for-quote infrastructure alongside expanded atomic swap functionality. RFQ systems allow counterparties to request executable pricing before committing to a transaction, a structure commonly suited to trades where participants want more control over execution than a public order book provides. Veyra adds the protocol infrastructure for more sophisticated trading and settlement workflows, but the proposal does not disclose live RFQ volumes, counterparties or institutional users.

The upgrade also expands Injective’s MultiVM architecture through additional IBC interoperability. The proposal specifically targets asset movement between Injective’s EVM environment and the wider interchain ecosystem. That direction builds on existing interoperability work, including the Cardano-Injective IBC connection currently operating on testnet. Additional IBC capabilities increase the routes available for assets and applications, but connectivity alone does not establish that significant liquidity will migrate through them.

Cross-chain liquidity has already become increasingly relevant to Injective. Circle-issued USDC on the network is being positioned as a replacement issuance standard for portions of the Cosmos ecosystem as native USDC migration advances across connected chains. Veyra’s interoperability changes could broaden the infrastructure around those flows, although stablecoin supply and available transfer routes remain separate from demonstrated trading or settlement demand.

CypherOS Remains a Future Privacy Layer

Privacy is another component of the roadmap, but Veyra does not launch CypherOS. Proposal 717 says the upgrade builds on foundations established by Meridian to prepare Injective for the future privacy platform, which is intended to support confidential trading, RWAs and financial transactions. The November upgrade should therefore be described as laying technical groundwork for CypherOS rather than activating confidential markets across Injective. No production usage metrics or launch date for CypherOS are specified in the Veyra proposal.

Governance remains the immediate constraint. Injective requires more than 33.4% participation for quorum, while at least 50% of non-abstaining voting power must support a proposal and the veto threshold must remain below 33.4%. The latest available tracker snapshot placed participation at approximately 33.03%, narrowly below quorum, despite Yes holding 70.91% of all votes already cast. About 28.65% was recorded as Abstain, 0.43% as No and none as No With Veto. Voting closes November 16.

If approved, Injective is scheduled to halt at block 193,145,000 and validators would restart the network using the v1.21.0 binary. The November 24 date is a target derived from expected block progression rather than an independently fixed activation time. The next measurable milestone is therefore governance approval, followed by successful validator coordination at the designated halt block; institutional usage of the new RWA, RFQ and privacy infrastructure would be a separate question after activation.

Satoshipick
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.