SPONSORED PARTNERMEXCExplore global spot and futures marketsEXPLORE MEXC →
CHARTING PARTNERTradingViewAdvanced charts, indicators and market analysisOPEN CHARTS →
TRADING PARTNERGMX via NetNapz TradeTrade decentralised perpetual marketsSTART TRADING →Injective Executes SafeHarbor 5 at Block 191.27M; Recovery Snapshot Pinned
NetNapz original reporting · Tracker entry dated: 10 November 2026 · Execution status checked: 11 November 2026 · Published: 11 November 2026
Injective’s official upgrade portal now records governance proposal 714 as passed and the v1.20.4-safeharbor.5 mainnet upgrade as executed at block 191,270,000. The portal labels the new binary live on the injective-1 chain and lists Cosmos SDK v0.50.15-inj.1 with CometBFT 1.0.1.
The completed status is a material step beyond the proposal’s earlier conditional language. The proposal had called for an expedited halt at the target block and a restart on the SafeHarbor 5 binary. Injective’s current upgrade tracker says that process has been completed; it should not be described as merely scheduled or still awaiting a vote.
What the official record confirms
The upgrade tracker identifies proposal 714 as the governance route for v1.20.4-safeharbor.5 and records execution at the stated height. Its accompanying description frames the release as preparation for a larger chain upgrade later in November, with changes aimed at network infrastructure, validator coordination and operational efficiency.
Those are project descriptions rather than an independent performance test. The public material does not quantify throughput gains, latency improvements or new institutional usage resulting from the upgrade. It also does not establish that every exchange, RPC provider or application operator completed its own integration work at the same moment as the chain-level activation.
Recovery resources are pinned at the pre-upgrade height
Injective’s official snapshots page now pins a recovery snapshot at height 191,269,999, immediately before the SafeHarbor 5 activation block. The page instructs node operators to preserve validator state, follow the coordinated recovery procedure and confirm database-backend compatibility before restoring.
The guidance also warns that CometBFT state sync does not restore the wasm directory and can therefore produce an AppHash mismatch. A full snapshot restore is the documented route when that condition applies. These are operator safeguards, not evidence that the chain rolled back or that ordinary INJ holders must take action.
A second coordinated change after the 9 November patch
The same official upgrade tracker records an emergency v1.20.4-bl.3 binary swap on 9 November at block 191,016,661. It describes that earlier event as a coordinated halt from a network-readiness exercise and says all node classes, including sentries, RPC infrastructure and exchange infrastructure, were required to run the patched binary.
SafeHarbor 5 is listed separately as a governance-approved upgrade at block 191,270,000. Keeping the two events distinct matters: the 9 November emergency patch and the separately recorded proposal-714 execution are related operational steps, but they are not the same release or the same decision process.
NetNapz assessment: activation is confirmed; performance claims need evidence
The strongest verified conclusion is narrow: Injective’s first-party tracker marks the proposal passed and the target-height upgrade complete, while the recovery page provides a pinned pre-upgrade snapshot. That reduces the uncertainty that existed while the proposal was still in voting and the halt was only projected.
The more consequential questions remain open. Validators and infrastructure providers need to demonstrate stable operation on the new binary, and the project has not published measured results showing how the release changes network performance or institutional adoption. A successful activation is therefore an operational milestone, not proof of additional token demand, exchange availability or investment returns.
For follow-up, the useful checks are whether the official portal continues to report SafeHarbor 5 as the live mainnet binary, whether any post-upgrade incident or rollback notice appears, and whether the larger November upgrade receives a separate proposal with specific code, timing and migration requirements. NetNapz will treat those as new events rather than folding them into this activation.