Bitget to Delist WBDUSDT Futures and Services
Bitget announces the upcoming delisting of WBDUSDT futures trading, futures copy trading, and futures bots effective October 7, 2026.

Crypto exchange Bitget has announced plans to delist futures trading, futures copy trading, and futures bots for the WBDUSDT trading pair, according to an official support notice from the platform.
Opening of new WBDUSDT futures positions will be suspended starting October 7, 2026, at 13:00 UTC. Shortly after, at 13:30 UTC on the same day, the exchange will officially suspend futures trading for the pair, cancel all related open orders, and remove WBDUSDT from futures trading bots and unified trading accounts.
Instant Telegram notifications for large on-chain moves.
Position Management and Closing
According to the platform announcement, closing positions, close orders, and take-profit/stop-loss (TP/SL) functions will remain operational until the final delisting time. Users holding open WBDUSDT futures positions are required to close them by 13:30 UTC on October 7, 2026. Any remaining open positions at that time will be automatically settled and closed by the system.
For trading bot users, pending bot orders will be automatically canceled upon removal, and the relevant assets will be credited back to user accounts. The platform noted that users will still be able to access historical data of the trading bots after the removal is complete.
Key facts
- New WBDUSDT futures position opening suspended: October 7, 2026, at 13:00 UTC
- Final futures trading and service delisting: October 7, 2026, at 13:30 UTC
- Affected services: Futures trading, futures copy trading, futures trading bots, and unified trading account futures
- Position handling: Remaining open positions will be automatically settled and closed at the delisting deadline
Source: bitget.com
This article is for information only and is not investment advice. BullishMarketCap news is produced with AI assistance from public sources and reviewed by our editors; see our editorial policy. Spotted an error? Tell us.

