Injective’s Veyra upgrade clears vote ahead of Nov. 24 halt
Injective voters approved Veyra’s v1.21.0 upgrade, targeting a Nov. 24 halt at block 193,145,000 as cross-chain and trading tools move toward mainnet.
BitCurrent Newsroom2 min read
Injective’s Veyra mainnet upgrade has passed governance, setting a target of Nov. 24 for the chain to halt and resume on version 1.21.0. The proposal 717 governance record confirms the vote and outlines new cross-chain and institutional trading infrastructure.
- 42.69% turnout: 24.06 million INJ in voting power participated, above the 33.4% quorum needed for a valid result.
- 16.24 million INJ voted yes: That was 67.5% of all participating voting power. Excluding abstentions, approval was 99.51%, according to The Defiant’s report on the final tally.
- Block 193,145,000: The proposal targets the halt at this height, with Nov. 24 an estimated date tied to reaching the block.
Veyra adds routes and trading tools
The approved proposal says Veyra expands Injective’s MultiVM architecture with Inter-Blockchain Communication (IBC) capabilities. These are intended to let assets move between Injective’s Ethereum Virtual Machine environment and the wider interchain ecosystem. That adds connectivity for tokenized assets and cross-chain liquidity; it does not itself issue new assets.
The upgrade also introduces request-for-quote (RFQ) infrastructure and expands atomic-swap functionality. RFQ tools let participants request prices for trades, while atomic swaps allow trades to execute together or not at all. The proposal describes these features as groundwork for institutional trading and settlement workflows.
Privacy remains on the roadmap
Veyra supports Injective’s plans for CypherOS, a future native privacy platform, but the proposal does not describe CypherOS as part of this launch. The approved scope is connectivity and trading infrastructure. Confidential trading remains a later step in the roadmap.
At the target height, the plan is for the chain to halt and resume with the v1.21.0 application binary. The vote settles governance approval; the scheduled activation still depends on the network reaching that block. For node operators, the change means preparing compatible software for the coordinated restart.
Source material
- proposal 717 governance record — pleb.is
- The Defiant’s report on the final tally — thedefiant.io