Injective Stops Blocks as Bithumb Pauses INJ Transfers

Injective stopped producing blocks after reaching height 191,016,661 on Nov. 9, according to the chain's block record. South Korean crypto exchange Bithumb suspended INJ deposits and withdrawals in response, while keeping INJ trading available.

Block production records transactions on a blockchain. When it stops, the network cannot process transfers through its normal recording process. For Bithumb users, that turned an infrastructure interruption into a practical constraint on moving funds.

What the block record does and does not show

The latest block height gives a fixed reference point for anyone checking the chain later. It shows where the recorded history stopped on Nov. 9. It does not, by itself, explain why production halted, when the next block would arrive or whether any transfers were delayed in the meantime. Those points remained unspecified.

Bithumb said it would restore deposits and withdrawals when the network was stable. The exchange did not give a specific reopening time. It also prevented customers from applying to stake or unstake INJ during the pause.

Deposits move tokens from outside wallets into an exchange. Withdrawals move them in the opposite direction. With both functions suspended, Bithumb customers could not move INJ between the exchange and their outside wallets.

Trading was a separate service. Users could still buy and sell INJ on Bithumb, but they could not transfer the token in or out or change its staking position through the platform. The pause applied to token movement and staking access, not to exchange trading.

What does this change for Bithumb customers?

It means trading remained available while the routes for moving INJ were closed. Users needed stable network operations before they could deposit or withdraw INJ, or submit a staking request. A balance on the exchange did not translate into an available withdrawal or a change in staking position.

For a Bithumb customer who wanted to withdraw INJ to an outside wallet, continued trading did not solve the problem. Selling INJ on the exchange remained possible, but transferring the token out did not. The same restriction affected customers seeking to stake or unstake INJ. They needed stable network operations before those requests could move forward.

The available information did not identify what caused the halt. It also did not quantify customer losses, report stolen funds or describe an exploit. The report likewise did not say that Injective had resumed block production. Continued trading on Bithumb should not be read as evidence of a functioning chain.

The upgrade and the reopening

Injective scheduled its next mainnet upgrade, v1.21.0, for Nov. 17. The report provided no release notes or change details and did not link the upgrade to the block-production interruption. The upgrade is a scheduled software event, not a confirmed reopening date for Bithumb's transfers.

For users, the first checkpoint is whether Injective advances beyond height 191,016,661. The second is whether Bithumb lifts the suspension after stable operations return. The next dated milestone is the Nov. 17 v1.21.0 upgrade, but reopening transfers still depends on stable network operations rather than a stated deadline.