Injective Veyra Vote Sets Block 193.145M Halt; Approval and v1.21.0 Release Remain Pending

NetNapz original reporting · Proposal submitted: 12 November 2026 · Governance and release status checked: 13 November 2026 at 18:27 GMT · Published: 13 November 2026

Injective governance proposal 717 asks voters to approve the Veyra mainnet upgrade and commit the chain to a coordinated halt at block 193,145,000 before resuming on application version v1.21.0. Injective’s official upgrade tracker lists the proposal as voting and dates the entry to 12 November.

The operative word is “asks.” The proposal has not yet completed governance, the target block has not been reached, and the official release page labels the production release as forthcoming. Describing Veyra as live, approved or guaranteed for 24 November would overstate the current record.

What proposal 717 would authorize

The proposal describes Veyra as an infrastructure upgrade for institutional and tokenized-asset applications. Its stated changes include additional Inter-Blockchain Communication routes for Injective’s EVM environment, request-for-quote infrastructure and expanded atomic-swap functions. It also presents the release as groundwork for future privacy capabilities under the project’s CypherOS roadmap.

Those descriptions establish intended software capabilities, not adoption. They do not demonstrate that a financial institution has issued an asset through Veyra, that liquidity will be available for a particular product, or that an INJ token represents ownership of any tokenized security. Product issuance, custody, redemption rights and jurisdictional availability remain separate questions.

The vote and the target date remain conditional

The proposal record says voting opened on 12 November and closes on 16 November 2026. A live governance mirror checked by NetNapz showed turnout close to, but still below, the stated 33.4% quorum at the time of review. Because votes can change until the voting window closes, that snapshot is not a final result and should not be treated as a forecast.

If the measure passes, the software-upgrade message names v1.21.0 and height 193,145,000. The proposal targets 24 November, but the chain action is keyed to block height rather than a guaranteed wall-clock time. Validators would have to install the approved binary and coordinate the restart after the halt.

The production binary is not yet published

Injective’s official GitHub releases page currently exposes a v1.21.0-beta testnet pre-release dated 6 November. Its own version output identifies it as a beta build. The official upgrade tracker, meanwhile, continues to list v1.20.4-safeharbor.5 as the current mainnet binary and marks the Veyra release as “Soon.”

This distinction matters operationally. A beta artifact can show the direction of testing, but it is not evidence that the final production package, hashes and migration instructions are available. Node operators should rely on the final official release and coordinated upgrade guidance rather than infer production readiness from the beta.

Veyra follows SafeHarbor 5, but it is a separate decision

Injective completed the SafeHarbor 5 upgrade under proposal 714 earlier in November. Proposal 717 is a new governance action with a different target height and version. The successful execution of SafeHarbor 5 does not pre-approve Veyra or remove the need for proposal 717 to meet quorum and pass.

The official tracker also pins a recovery snapshot for the current mainnet line. That is an operator safeguard. It is not evidence that Veyra has executed, nor does it imply that ordinary token holders need to move assets.

NetNapz assessment: the next proof points are governance and reproducible release details

The material development is the move from a roadmap description to a live software-upgrade vote with a defined halt height. That gives validators, developers and applications a concrete coordination point. It still leaves two decisive conditions unresolved: a valid final governance result and publication of the final v1.21.0 production release with verifiable artifacts.

After those conditions, the relevant checks are whether the chain reaches the target height, resumes consensus on the new version and publishes any incident or rollback notice. Claims about institutional adoption, tokenized-asset volume or privacy functionality require separate evidence after activation.

Sources

• Injective Chain official upgrade tracker — proposal 717, target height and current mainnet version, checked 13 November 2026
• Injective governance proposal 717 mirror — proposal text, voting window and live turnout snapshot, checked 13 November 2026
• Injective Foundation official release repository — v1.21.0-beta and production-release status, checked 13 November 2026