Altcoins
Injective puts its Veyra mainnet upgrade to a vote
Proposal 717 calls for switching to version 1.21.0 after a halt at block 193,145,000. Voting is due to end on November 16, and the upgrade still depends on the result.

The vote comes before the planned halt at block 193,145,000
Injective opened voting on November 12, 2026, on Veyra, a proposed mainnet upgrade. Proposal 717 is listed in the governance record with voting scheduled to close on November 16 at 16:53 UTC. The plan in that record calls for halting the chain at block 193,145,000 and resuming with version 1.21.0 of the protocol software.
The proposal puts the chain’s arrival at that height around November 24. If the vote passes, the block number triggers the halt. The date remains an estimate based on the chain’s progress, and the plan sets no activation time. The proposal was still in its voting period when the record was checked. The project’s tracking page still showed version 1.20.4-safeharbor.5 running on mainnet.
Cross-chain transfers and new trading tools
The proposal extends the exchange of data and assets between Injective’s EVM environment and other networks compatible with the IBC protocol. The EVM is the environment where Ethereum-compatible contracts run. The proposal describes the IBC extension as a way to ease asset transfers between that environment and chains using the protocol. It gives no launch schedule for a particular asset.
Veyra also calls for request-for-quote infrastructure and expanded atomic swap functionality. A request for quote lets users ask for a price before deciding whether to execute a trade. In an atomic swap, both transfers complete together or are canceled. The proposal describes these tools as a foundation for future execution and settlement workflows. It also mentions privacy work building on Meridian and links it to the CypherOS roadmap.
Operators are waiting for the binary and the vote outcome
Injective’s documentation describes a coordinated procedure for major upgrades. After a successful vote and once the chain reaches the halt height, validators switch to the new binary and the chain resumes when consensus restarts. The tracking page directs node operators to preparation instructions that cover binary verification and rollback procedures.
The tracking page still listed the version 1.21.0 binary as forthcoming at the time of the check. The vote close and the software release are therefore the next things to verify before treating November 24 as an implementation window. For applications that rely on the chain, the planned halt remains conditional on approval and tied to the block height.
