On November 9, 2026, the Injective mainnet stopped producing blocks at height 191,016,661, and Upbit, Bithumb and Coinone paused INJ deposits and withdrawals while INJ spot trading stayed open. For anyone running an automated spot strategy, that combination is the lesson: a market can keep printing prices after the asset behind it can no longer move in or out of the venue. An open order book is not the same thing as a normal market, and a quote is not the same thing as an exit.
This article is an operational checklist, not a trading signal. It does not say anything about the future price of INJ, it does not claim that Gimmer supports or integrates with any exchange or network named here, and it does not suggest that anyone should trade or avoid this asset. The aim is narrower: to show which questions a spot strategy should be able to answer when a network halts but its markets do not.
What happened
According to reports citing Injective’s official node data, the last block before the stop was 191,016,661, produced at 21:04 Beijing time (13:04 UTC) on November 9. ChainCatcher reported that Upbit suspended INJ deposits and withdrawals because block generation was interrupted, with spot trading unaffected, and that Coinone suspended INJ transfers from 22:25 Beijing time while keeping trading and other services running. PANews reported that Bithumb’s suspension began at 23:00 KST, covered deposits, withdrawals, staking and unstaking, and would end only “when the network was stable,” with no reopening time given. Bithumb said queued withdrawals would be processed in order once service resumed.
TokenPost confirmed the halt height and Bithumb’s pause, and noted that Injective’s next scheduled mainnet upgrade, v1.21.0, is set for November 17. In a follow-up, TokenPost quoted an Injective community administrator describing the pause as a planned mainnet upgrade test to rehearse emergency upgrade procedures with validators. We did not find that framing in a formal post-mortem, so treat it as the community account rather than a final explanation. By November 10 at 16:26 UTC, Injective’s public node endpoint was again returning new blocks, at height 191,150,024. Exchange transfer status is a separate question, and each venue announces its own reopening.
The event involves several distinct states that are easy to collapse into one:
- Chain state: whether the network is producing and finalizing blocks.
- Transfer state: whether a given exchange accepts deposits and processes withdrawals for that asset.
- Trading state: whether the order book on that exchange is open and matching.
- Your position state: what you actually hold on the venue, including pending orders and queued withdrawals.
The mistakes a halted-but-trading market exposes
When transfers stop and trading continues, each order book becomes more of an island, and spot automation tends to make quiet, avoidable errors.
- Treating the last price as fair value. A closed-loop market can drift away from other venues, and spreads can widen while liquidity thins. A strategy that reads the last trade as “the price” may size entries or exits on a number few participants can actually trade at.
- Assuming an exit exists because the market is open. If a sell order meets a thin book, the result can be a partial fill or a fill far from the displayed quote. Open trading does not mean deep trading.
- Counting on a transfer to rebalance. Plans that rely on moving tokens between venues, or withdrawing to self-custody, stall when transfers pause. Queued withdrawals are not completed withdrawals.
- Retrying blindly. When responses are slow or ambiguous, resubmitting an order can double exposure if the first request already reached the venue.
- Reading “chain resumed” as “everything resumed.” Block production can restart before each exchange reopens deposits and withdrawals, and those reopenings arrive at different times.
Checklist: spot execution during a network halt
| State | Question to answer | Evidence to keep |
|---|---|---|
| Chain | Is the network producing blocks, and since when did it stop or resume? | Block height and timestamp from a node or explorer, with the time zone noted. |
| Transfers | Which venues paused deposits or withdrawals for this asset, and what did each notice say about reopening? | Links to each exchange notice, with start times as stated. |
| Trading | Is the pair still trading, and has the spread or visible depth changed? | A snapshot of the spread and top-of-book depth at the time you reviewed it. |
| Strategy mode | Is the strategy actually running in Spot mode on the pair you think it is? | The strategy summary showing mode, base/quote pair and sizing. |
| Order rules | Would the next order still meet the minimum notional, quantity step and price tick at current prices? | The order rules for the pair and a worked size calculation. |
| Position | What do you hold, what orders are open, and what withdrawals are queued? | Balances, open orders and withdrawal status from the exchange itself. |
| Valuation | How far could the realizable amount differ from the displayed quote valuation? | A note of spread, fees and estimated slippage at your size. |
Run the checklist with Gimmer’s Spot execution settings
Gimmer’s Spot execution guide describes Spot mode as one that “exchanges one asset for another without intentionally borrowing funds.” It is a useful lens for this kind of event because it keeps the decision, the order and the valuation separate.
1. Confirm the mode and the pair
The guide’s first steps are to “Select Spot in the builder” and to “Confirm that the strategy summary shows the intended mode.” Then check the markets you added: the docs say to “Read a symbol as base/quote, such as ETH/USDT.” During a halt, it matters that you know exactly which asset is the base and which is the quote, because the base asset is the one that cannot move in or out of the venue.
2. Know what each decision does
The guide maps decisions to orders. Buy “uses the quote asset to acquire the base asset, subject to available balance and order constraints,” and Sell “sells available base asset for the quote asset.” The most important line for a halted network is about Hold: it “records no new order for that decision. It does not guarantee that existing exposure is risk-free.” A strategy that is holding is still exposed to a market that may be drifting from other venues.
3. Re-check sizing and order rules
The docs ask you to “Confirm percentage versus fixed value and reserve balance for fees, rounding, and simultaneous entries,” and they warn that “Minimum notional, quantity step, price tick, and available liquidity can change what is executable.” When a market thins out, available liquidity is the rule most likely to change. Review the sizing before the next candle closes, not after an order fails.
4. Read valuation as a display, not an exit price
The guide is direct: “Quote valuation converts a position into the quote asset for display. It is not necessarily the exact amount obtainable after spread, slippage, fees, and partial fills.” In a closed-loop market, that gap can be wider than usual.
5. Treat ambiguous orders carefully
If an order request times out or returns an unclear result, the docs say: “Do not assume a retry is safe until you know whether the first attempt reached the venue.” Check open orders and fills on the exchange before you act again.
Related reading from earlier posts: our network recovery checklist on why “back online” is not one state, the exchange delisting checklist for auditing an exact market, and the slippage stress test for questioning fill assumptions.
A short example
The following is synthetic. The pair, prices and sizes are invented to illustrate the checklist and do not describe any real account or market.
- A trader runs a Spot strategy on a fictional pair, TOKEN/USD, on a four-hour interval, with fixed sizing of 500 USD per entry and a reserve kept aside for fees and rounding.
- The TOKEN network stops producing blocks. The trader’s exchange posts a notice pausing TOKEN deposits and withdrawals, while trading remains open.
- The trader records the halt height and time, saves the exchange notice and takes a snapshot of the order book: the spread has widened from about 0.1% to about 1.2%, and visible depth near the top of the book is much thinner.
- The strategy summary confirms Spot mode on TOKEN/USD. The trader checks the order rules and confirms a 500 USD order still meets the minimum notional, but estimates that a sell of the full position would move through several price levels.
- The position screen shows a quote valuation of 2,000 USD. The trader notes that the realizable amount after spread, fees and slippage could be noticeably lower, and that a withdrawal requested earlier is queued, not completed.
- The trader decides to keep the strategy in simulation for the next few candles, watch how the spread behaves, and wait for both block production and the exchange’s transfer notice to show normal service before reconsidering live operation.
This example shows a process for gathering evidence. It is not a recommendation to buy, sell, hold or pause any asset.
What Spot execution settings cannot do
- They cannot tell you whether a network is halted or whether an exchange has paused transfers. You need to check the chain and each venue’s notices yourself.
- They cannot create liquidity. Minimum notional, quantity step, price tick and available liquidity “can change what is executable.”
- They cannot make a quote valuation into a guaranteed exit price or guarantee a fill.
- They cannot make Hold risk-free. Existing exposure remains exposed to the market.
- They cannot confirm whether an ambiguous order reached the venue. Only the exchange’s own records can.
Risk note: As the guide says, Spot “still carries market, liquidity, fee, balance, and exchange risk.” Trading digital assets involves substantial risk. Backtests and simulations do not guarantee future results. Gimmer is a desktop workspace for designing, backtesting, simulating and operating automated strategies. It is not financial advice and does not trade on your behalf.
Frequently asked questions
If trading is open, why does a transfer pause matter to a spot strategy?
Because transfers are how prices stay aligned across venues. When tokens cannot move in or out, a single order book can drift, spreads can widen and depth can thin, so the displayed price becomes a weaker guide to what an order will actually achieve.
The chain is producing blocks again. Is it back to normal?
Not necessarily. Block production, exchange deposits, exchange withdrawals and queued requests each recover on their own schedule. Check each exchange’s notice and your own balances and withdrawal status before assuming normal service.
Should I stop my bot during a network halt?
That is your decision, and it depends on your strategy and risk tolerance. Keep in mind that stopping a bot does not necessarily close positions or cancel orders already on the exchange, so review what is open on the venue itself.
Keep the quote and the exit apart
A market can look open while its plumbing is not. Separate the chain, transfer, trading and position states, and read quote valuation as a display rather than a promise.
Next step: Open the Spot execution guide, confirm your strategy summary shows the intended mode and pair, and walk through the order rules for each market before the next candle closes.
— The Gimmer Team