Bithumb Suspends INJ Deposits and Withdrawals After Injective Blocks Stop at 191,016,661
Key Facts
Bithumb announced the suspension of INJ deposits and withdrawals on November 9, 2026, after saying block production on the Injective network had stopped. The exchange posted its notice at 22:55:57 Korea time, stating that the measure was due to “a halt in Injective network block production, making deposits and withdrawals unavailable.” The decision affects transfers between the exchange and the network, while Bithumb said trading would remain available as normal during the suspension. The exchange also stopped accepting INJ staking and unstaking requests during the same period. The company tied the resumption of deposits and withdrawals to network stability, without giving an advance timetable for restoring the service.
The continuation of trading means Bithumb users can trade INJ on the platform, but cannot deposit or withdraw the coin through the network during the suspension. As for staking services, the suspension of new requests covers both staking the coin and unstaking it, according to the company’s notice. Bithumb did not cite any effect on trading in the notice, but confirmed that transactions would continue “as normal.” Transfers that had not been completed when the suspension began will be handled under the platform’s procedures, while some withdrawals may take longer to appear in customers’ accounts. The announced restrictions therefore focus on transfer and staking services, rather than spot trading on the platform.
Bithumb said withdrawal requests submitted before the suspension but not completed when the halt began would be reviewed through its system and then processed in turn. It warned that these transactions might take time to appear in members’ accounts, meaning that submitting a withdrawal request before the service was halted does not guarantee that it will appear immediately. Deposits arriving after the suspension began will likewise not be credited immediately; they will be processed sequentially after service resumes. The notice thus distinguished between requests still incomplete before the halt and deposits arriving during it, with processing of both deferred until service returns or the system review is complete. It did not specify how long subsequent processing would take or when deposits and withdrawals would resume.
Against the backdrop of the halt, a ChainCatcher report said the last visible block on the mainnet was at height 191,016,661 and was produced at 21:04 Beijing time on November 9. This provides a timestamp and a specific height for the last block observed by the report, coinciding with exchanges suspending transfer services. The report also said Upbit had halted INJ deposits and withdrawals because block production had stopped, and said spot trading was unaffected. However, Upbit’s announcement has not been verified through an official source or a major, reliable news source, so the action attributed to it cannot be confirmed with the same degree of certainty as Bithumb’s suspension notice. Coinone also reported suspending INJ deposits and withdrawals from 22:25 Korea time on the same day, attributing the move to a network issue while exempting trading and other services from the suspension.
Coinone said deposits and withdrawals made during the suspension would be processed sequentially after service resumed and the system’s stability was verified. This is similar to Bithumb’s announcement that deposits arriving during the halt would be processed later, while each exchange made service resumption conditional on system or network stability. Coinone has previously suspended INJ transfers: it halted the service on September 24, 2026, at 20:00 Korea time as part of a network upgrade, then announced the upgrade’s completion on September 26 at 09:38. That incident was tied to a scheduled upgrade, while the November 9 notice described the cause as a network issue. The earlier case shows that a service suspension can coincide with network work, but Coinone’s current notice did not identify a specific upgrade.
Injective’s upgrades page provides additional context on activity on the network: it listed the emergency patch v1.20.4-bl.3 as “deployment in progress” and described the deployment as gradual and without downtime. The page also showed the network at height 191,016,662, one block after height 191,016,661, which the ChainCatcher report cited as the last visible block. Injective explains that major upgrades are activated through governance software upgrade proposals, and that the chain halts at a specified height before validators move to the new software and resume consensus. However, the page did not explicitly link the emergency patch to Bithumb’s or Coinone’s suspension. What can be confirmed is that the displayed deployment coincided with a height after the block cited in the report, not that the patch caused the suspension.
Bithumb did not announce a timetable for resuming transfer services, saying instead that it would restore them “as soon as network stability is confirmed” and notify users of the timing through the same notice. Coinone said transactions made during the halt would be processed after service resumed and system stability was confirmed, without specifying a return time in its notice. According to Injective’s upgrades page, deployment of the emergency patch v1.20.4-bl.3 was still in progress when the page was viewed, with the network shown at height 191,016,662. Bithumb’s announced next operational step therefore remains tied to confirming stability and then posting an update specifying when deposits and withdrawals will reopen.