Bithumb Delists Token With Trading Ending December 7

Trading Stops December 7, Withdrawals January 7

Bithumb will remove Fetch.ai (FET) from its platform, the South Korean exchange announced on November 5, 2026. In its official delisting notice, the exchange stated that the security concerns which had earlier placed the project under an investment warning were never resolved, and that the explanations submitted by the project team did not go far enough to clear the identified risks. Under the published schedule, trading in FET ends on December 7, 2026, at 15:00 Korea Standard Time, which equals 06:00 UTC, and withdrawal support runs until January 7, 2027, ending at the same hour of day.

The mechanics of the shutdown are set out in the same document. Open buy and sell orders on the order book are cancelled automatically once trading ends, and transactions executed through the API stop on the same date. Bithumb cautioned that the timetable can change for operational reasons and that approving external wallet addresses may take time, so users who intend to move their FET to another venue or a personal wallet should complete the transfer before the deadlines. The gap between the two dates matters: after December 7 an account can no longer trade the token, but assets can still be moved off the exchange for another month. Bithumb ranks among South Korea's leading exchanges, so the move removes one of the token's Korean venues. What the notice establishes is a fixed timetable: roughly one further month of trading, followed by a final month in which holders can still withdraw.

September Warning Set the Review in Motion

The path to the decision began earlier in the autumn. The exchange had already flagged FET in its September 21 warning notice, which cited security incidents in crypto wallets or blockchain infrastructure whose origin had not been clarified or remedied; that designation opened a review of the project. A second notice, published on October 23, extended the review period, with the exchange saying it needed more time to evaluate the defenses and additional explanations provided by the project's management. The final assessment went the other way: Bithumb concluded that the documents supplied by the Fetch.ai team failed to resolve the problems that had triggered the warning.

Fetch.ai sits in the artificial intelligence segment of the market, combining machine-oriented technology with blockchain infrastructure, and FET functions as the token of the Artificial Superintelligence Alliance ecosystem. The delisting does not mean the project's technological activity has stopped. It does, however, narrow access for South Korean investors, because removing an altcoin from a major venue tends to thin liquidity in the affected trading pairs and change execution conditions for anyone still holding there. How the dates line up:

• September 21, 2026: FET added to the investment-warning list over unexplained security incidents
• October 23, 2026: review period extended to weigh the project team's additional explanations
• December 7, 2026: trading and API support end at 15:00 KST, with open orders cancelled
• January 7, 2027: withdrawal support ends at 15:00 KST, after which token-level services may be restricted

The exchange stressed one further point that matters for holders: once withdrawal support stops, services tied to the delisted asset, such as network updates, token swaps and other blockchain operations, may no longer be provided.

Read as one sequence, the case shows a venue giving a project two chances, a warning on September 21 and an extension on October 23, before acting on November 5. For holders on the Korean platform, the operative deadline is January 7, 2027: assets left on the exchange after that date become difficult to recover, and token-level services may stop alongside them. The wider market for FET is untouched for now, and anyone tracking execution conditions as liquidity shifts can follow FET technical analysis for current support and resistance levels. Whether other venues take a similar step depends on how the project documents the underlying security incidents, not on Bithumb's calendar.