Injective’s governance vote on the Veyra mainnet upgrade has crossed the participation threshold required for a valid result, removing a key obstacle that had left the proposal short of quorum earlier in the voting period. Proposal 717 remained open and its final outcome was not yet determined when The Token Press verified the live tally on November 15.

Quorum reached before the deadline

The governance tracker Plebis showed 21,971,325 INJ in voting power participating, equal to 39.11% of the eligible total and above the 33.40% quorum requirement. The snapshot listed 14,526,403 INJ, or 66.1% of votes cast, in favor; 80,589 INJ, or 0.4%, against; one unit of voting power against with veto; and 7,364,332 INJ, or 33.5%, abstaining. Abstentions contribute to participation, so the quorum figure and the share supporting the proposal answer different questions. The ballot is scheduled to close on November 16 at 16:53 UTC, and the tracker still labeled the outcome as pending despite projecting that the proposal was likely to pass.

Related reporting: Aztec Tierra Fixes Critical V5 Flaw and Speeds Private Proofs

What Veyra would change

Injective’s official upgrade page identifies Veyra as version 1.21.0 and links it to proposal 717. The proposal would expand Inter-Blockchain Communication capabilities across Injective’s MultiVM architecture, including routes between its Ethereum Virtual Machine environment and the wider interchain ecosystem. It also proposes request-for-quote infrastructure and broader atomic-swap functionality. RFQ systems let a participant seek a price from liquidity providers before executing a trade, while atomic settlement is designed so linked legs complete together or fail without a partial transfer.

Institutional features remain prospective

The proposal frames those changes as infrastructure for issuing, trading and settling tokenized real-world assets. It also says Veyra would prepare the network for CypherOS, a planned privacy platform intended to support confidential trading and financial transactions. Crypto.news independently reported the proposal’s launch and the same feature set on November 13, when participation was still below quorum. That earlier snapshot underscores what changed: turnout has since moved above the required threshold, but governance approval and the software activation are still separate steps.

Why operators watch the halt height

Injective’s upgrade process uses a predetermined block height rather than a conventional maintenance window. The official chain documentation says a major-version proposal commits the network to halt at that height, after which validators replace the application binary manually or through the Cosmovisor upgrade manager. Consensus resumes when enough voting power is running compatible software. That coordination makes the published height important to validators, exchanges, RPC providers and applications that depend on the chain. It also means a favorable vote would begin an operational preparation period rather than complete the upgrade immediately. Release checks, binary verification and rollback planning remain part of the work before activation.

Activation depends on the final vote

If the proposal passes, Injective would halt at block 193,145,000, targeted for November 24, and validators would restart the chain using the v1.21.0 application binary. The official upgrade page currently lists the existing mainnet version as v1.20.4-safeharbor.5 and marks the Veyra release as forthcoming. Reaching quorum does not itself authorize the upgrade, and the vote distribution can continue to change until the ballot closes. Node operators and applications therefore still need to wait for the final governance result and published release materials before treating the new version as scheduled for deployment.

Sources

AI-generated editorial image; not a photograph of the reported event. Prepared with AI assistance and source verification.