Explore Hub: Exchange Guides

The primary keyword for this update is Bybit six-token delisting. Bybit announced on August 16, 2026 that it will delist CAMP, WHITEWHALE, CUDIS, PIRATE, TAI and SVL under its Token Management Rules. Deposits close after August 24, 2026 at 8:00 a.m. UTC, trading on CAMPUSDT, WHITEWHALEUSDT, CUDISUSDT, PIRATEUSDT, TAIUSDT and SVLUSDT ends after August 25, 2026 at 8:00 a.m. UTC, and active Spot Grid or DCA bots on those pairs must be closed before the same deadline or they will be automatically terminated.

What Happened

Bybit announced on August 16, 2026 that it will delist CAMP, WHITEWHALE, CUDIS, PIRATE, TAI and SVL under its Token Management Rules. Deposits close after August 24, 2026 at 8:00 a.m. UTC, trading on CAMPUSDT, WHITEWHALEUSDT, CUDISUSDT, PIRATEUSDT, TAIUSDT and SVLUSDT ends after August 25, 2026 at 8:00 a.m. UTC, and active Spot Grid or DCA bots on those pairs must be closed before the same deadline or they will be automatically terminated.

The event dates above come from the cited sources; this page was checked against those sources on August 19, 2026 UTC before publishing. The event date and the publish date are intentionally separated: the event date comes from the cited source, while this page is published in UTC during the August 19 news window.

Why It Matters

For CryptoSigy, this is a delisting-deadline event with concrete execution decisions: exit or convert before the pair closure, close grid and DCA bots before the auto-termination point, and complete deposits before the August 24 cutoff, because withdrawals remain possible after the pairs close but should be managed early.

The owner fit controls the framing. Exchange and venue events stay on CryptoSigy as listing, liquidity, fee, margin or contract-risk context; protocol and ecosystem events stay on Radar when the useful question is chain operations, governance or security infrastructure.

What To Watch Next

Watch the August 24 deposit cutoff, the August 25 trading-end and bot-termination point, remaining order-book liquidity, and whether the tokens move to any follow-up convert or withdrawal route.

If the official source updates contract specs, fee terms, deadlines, block heights or protocol details, rebuild the decision from the updated source rather than from a stale headline.

The editorial filter is delisting deadline management, bot termination, deposit close and exit routing risk.. Treat this as decision context, not as a prediction, recommendation or promotional note.

Date discipline matters: published and updated timestamps are generated at publish time in UTC, while event dates in the body come from the cited source.

Risk reminder: betting and crypto decisions can cause financial loss. Use official sources, keep stakes or position sizes controlled, and avoid treating one update as a complete strategy.

Before acting on the update, compare the official notice with the live product, market or protocol surface. If contract specs, fee terms, route availability, lineup status or governance details differ, the live source should override the older assumption.

The practical output is a watchlist, not a verdict. Readers should know which timestamp, rule, venue field or protocol dependency must be checked next before the update has any operational value.

Continue this cluster

Continue this cluster with related source-backed updates that keep the same owner-specific decision frame.