Injective Network Upgrade Follows Binary Options Exploit

High attention and emotional sentiment detected.

Injective contributors tagged the patch as v1.20.3-safeharbor.1 on GitHub. The rollout then stretched far longer than a routine upgrade, and that gap became the center of a public dispute.

What Injective Shipped on August 31

The release carried commit b994d6b and the telling suffix “safeharbor.” Unlike the Vulcan upgrade in June, no governance proposal set a scheduled halt height for this binary.

So contributors produced a patched build, told validators to switch, and coordinated the changeover in real time. On-chain researcher Paddy-earthling notes there was no on-chain upgrade proposal for the change.

Because Injective ships finance modules directly in its core code, the fix sits in the base chain. According to a public GitHub diff, the patch adds a missing insurance-fund denomination check and disables binary options on mainnet.

Not the Usual Injective Network Upgrade

This event looked nothing like Injective’s planned upgrades. Back on June 4, the governance-led Vulcan release activated at block 169,334,500 with native USDC and real-world asset markets.

That upgrade followed a published proposal and a known halt height. Validators knew the schedule in advance, so exchanges paused deposits briefly and then resumed as expected.

The July interoperability upgrade, IIP-677, also passed on-chain with about 72% support. In contrast, the August 31 patch skipped that governance path entirely and shipped as a security build.

Upgrade or Halt? The On-Chain Timeline

This is where accounts split. On-chain analysts report that block 181,027,006 landed at 16:10 UTC, and the next block did not arrive until 19:52 UTC.

As a result, the chain showed no new blocks for roughly three hours and 42 minutes. Still, the height rose by exactly one, so there was no rollback of the ledger.

Injective disputes the framing. In its official statement, the team said the chain “was upgraded, not halted” and “continued processing transactions.”

Yet Upbit told a different story to its users. The Korean exchange paused INJ deposits and withdrawals and listed the reason plainly as a block production halt.

What the Exploit Actually Hit

Injective says the attack struck “a small number of ecosystem applications operating binary options markets.” Therefore, the team argues, the blockchain, protocol, native assets, and consensus stayed clear.

Independent researchers push back on that line. They point out that binary options and insurance funds are native Injective modules, not third-party smart contracts.

According to Paddy-earthling’s reconstruction, the exploit routed through native settlement paths. A deficit payout function reportedly covered a market loss without checking that the insurance fund’s denomination matched the market’s quote currency.

The attacker could then loop that mismatch many times. Because the fix lives in the Injective network upgrade itself, and disables binary options chain-wide, critics say the “apps not chain” framing does not hold.

Where the Numbers Stand After the Injective Network Upgrade

Loss estimates remain unconfirmed and vary widely. Early figures ranged near $2.79 million, while several outlets cited roughly $4.9 million, or about 1,980 ETH bridged to Ethereum.

Paddy-earthling’s own tally across many transactions suggests a larger figure near $6.5 million. Injective, meanwhile, has not published any loss number of its own.

Price impact stayed contained. INJ traded around $4.81 to $4.90 on September 1, down modestly from a $4.93 close on August 31, per CoinGecko data.

The sharper signal sat in on-chain flows. DefiLlama showed Injective DeFi TVL near $9.29 million, down about 7% in a day, though that may mix the incident with older outflows.

What Injective Leadership Says

CEO and co-founder Eric Chen addressed the coverage first. In an early reply, he wrote that “there was an upgrade done to the chain, not a halt” and that funds are safe.

Chen also drew a line around responsibility. He said the team can help apps stay secure but cannot prevent every issue across a permissionless ecosystem.

The official account added operational detail. It confirmed that some validators were temporarily jailed for missing the upgrade window, and that some exchanges paused deposits while updating their nodes.

Community Splits Over the Wording

Reaction on X broke into three camps. Ambassadors and official replies restated the bullet points, calling halt coverage FUD and stressing that staked INJ never faced risk.

Skeptics focused on the wording instead. One widely shared post argued that taking the chain down for around four hours to upgrade it is not what most people would call an upgrade.

Others flagged a communications gap. The main account kept posting product marketing during the block gap, and the detailed statement arrived roughly a day after the chain resumed.

What Remains Unknown

Several core questions stay open as of September 1. Injective has not shared exact downtime timestamps, a formal root-cause report, or a verified loss figure.

It is also unclear whether any ordinary users of the binary options apps lost balances, or only shared insurance capital. Furthermore, nobody has confirmed who refilled the insurance pool that researchers say now reads as full.

For now, the next Injective network upgrade disclosure will likely decide the narrative. A published post-mortem with heights and figures would close the gap between the official wording and the on-chain record. This article is not financial advice.