출처 검증 리서치: Bybit

Verified source facts

1. Bybit says SWELLUSDC, SANDUSDC and LUNCUSDC spot trading pairs will be delisted on September 24, 2026 at 08:00 UTC. 2. The notice recommends canceling outstanding orders before cessation and says remaining open orders will be automatically removed by the system. 3. The notice says active Spot Grid Bots and DCA Bots involving the listed tokens will be automatically terminated by the system. 4. The notice states the delisting of a spot pair does not affect the underlying tokens and that deposits and withdrawals remain open unless announced otherwise.

Comparison at a glance

1. Official-product check: Deadline

A venue announcement becomes useful only after its rule is translated into a testable account decision. Here, deadline concerns the official 08:00 UTC cessation time. Retain the dated first-party wording, identify the eligible entity and product screen, and then convert the deadline once and set a pre-deadline action time. A launch headline cannot prove access, suitability, liquidity, or the result for a particular account.

Separate the product's stated mechanics from promotional framing. Identify the funding source, matching or pricing rule, settlement trigger, fee formula, loss boundary, and suspension policy. The documentation can describe those controls, but it cannot resolve whether Bybit later changes the notice. That unknown must remain visible rather than being converted into a prediction.

Finally, make deadline reversible where possible: convert the deadline once and set a pre-deadline action time. Retain non-secret evidence and reconcile the result with the rule for the official 08:00 UTC cessation time. This section evaluates operational mechanics; because whether Bybit later changes the notice remains unresolved, it does not predict the underlying market or recommend taking the exposure.

2. Official-product check: Open orders

Here, open orders concerns orders left on the affected pairs. Retain the dated first-party wording, identify the eligible entity and product screen, and then cancel intentionally and export order history.

The documentation can describe those controls, but it cannot resolve fills during the final minutes.

Finally, make open orders reversible where possible: cancel intentionally and export order history. Retain non-secret evidence and reconcile the result with the rule for orders left on the affected pairs. This section evaluates operational mechanics; because fills during the final minutes remains unresolved, it does not predict the underlying market or recommend taking the exposure.

3. Official-product check: Trading bots

Here, trading bots concerns Spot Grid and DCA bots tied to the pairs. Retain the dated first-party wording, identify the eligible entity and product screen, and then stop affected bots manually when record clarity matters.

The documentation can describe those controls, but it cannot resolve the exact termination sequence for each account.

Finally, make trading bots reversible where possible: stop affected bots manually when record clarity matters. Retain non-secret evidence and reconcile the result with the rule for Spot Grid and DCA bots tied to the pairs. This section evaluates operational mechanics; because the exact termination sequence for each account remains unresolved, it does not predict the underlying market or recommend taking the exposure.

4. Official-product check: Token availability

Here, token availability concerns whether base and quote assets remain accessible elsewhere. Retain the dated first-party wording, identify the eligible entity and product screen, and then check alternative pairs before placing replacement orders.

The documentation can describe those controls, but it cannot resolve future liquidity on other pairs.

Finally, make token availability reversible where possible: check alternative pairs before placing replacement orders. Retain non-secret evidence and reconcile the result with the rule for whether base and quote assets remain accessible elsewhere. This section evaluates operational mechanics; because future liquidity on other pairs remains unresolved, it does not predict the underlying market or recommend taking the exposure.

5. Official-product check: Deposits and withdrawals

Here, deposits and withdrawals concerns network availability for underlying tokens. Retain the dated first-party wording, identify the eligible entity and product screen, and then verify the live asset and network screen before transfer.

The documentation can describe those controls, but it cannot resolve future maintenance or token-specific restrictions.

Finally, make deposits and withdrawals reversible where possible: verify the live asset and network screen before transfer. Retain non-secret evidence and reconcile the result with the rule for network availability for underlying tokens. This section evaluates operational mechanics; because future maintenance or token-specific restrictions remains unresolved, it does not predict the underlying market or recommend taking the exposure.

6. Official-product check: Records

Here, records concerns orders, bot logs and account bills. Retain the dated first-party wording, identify the eligible entity and product screen, and then export non-secret records before interface changes.

The documentation can describe those controls, but it cannot resolve future retention period.

Finally, make records reversible where possible: export non-secret records before interface changes. Retain non-secret evidence and reconcile the result with the rule for orders, bot logs and account bills. This section evaluates operational mechanics; because future retention period remains unresolved, it does not predict the underlying market or recommend taking the exposure.

7. Official-product check: Account scope

Here, account scope concerns regional and entity-specific product availability. Retain the dated first-party wording, identify the eligible entity and product screen, and then confirm the signed-in entity and product screen.

The documentation can describe those controls, but it cannot resolve account-specific eligibility changes.

Finally, make account scope reversible where possible: confirm the signed-in entity and product screen. Retain non-secret evidence and reconcile the result with the rule for regional and entity-specific product availability. This section evaluates operational mechanics; because account-specific eligibility changes remains unresolved, it does not predict the underlying market or recommend taking the exposure.

8. Official-product check: Risk framing

Here, risk framing concerns operational deadline rather than price outlook. Retain the dated first-party wording, identify the eligible entity and product screen, and then separate delisting mechanics from token price views.

The documentation can describe those controls, but it cannot resolve future token price or relisting.

Finally, make risk framing reversible where possible: separate delisting mechanics from token price views. Retain non-secret evidence and reconcile the result with the rule for operational deadline rather than price outlook. This section evaluates operational mechanics; because future token price or relisting remains unresolved, it does not predict the underlying market or recommend taking the exposure.

9. Official-product check: Evidence

Here, evidence concerns first-party announcement and help documentation. Retain the dated first-party wording, identify the eligible entity and product screen, and then retain dated official URLs in the decision file.

The documentation can describe those controls, but it cannot resolve unpublished internal review criteria.

Finally, make evidence reversible where possible: retain dated official URLs in the decision file. Retain non-secret evidence and reconcile the result with the rule for first-party announcement and help documentation. This section evaluates operational mechanics; because unpublished internal review criteria remains unresolved, it does not predict the underlying market or recommend taking the exposure.

10. Official-product check: Stop rule

Here, stop rule concerns any unverified material fact. Retain the dated first-party wording, identify the eligible entity and product screen, and then pause transfers or replacement orders until verified.

The documentation can describe those controls, but it cannot resolve whether support will resolve every edge case before deadline.

Finally, make stop rule reversible where possible: pause transfers or replacement orders until verified. Retain non-secret evidence and reconcile the result with the rule for any unverified material fact. This section evaluates operational mechanics; because whether support will resolve every edge case before deadline remains unresolved, it does not predict the underlying market or recommend taking the exposure.

Decision scenarios

Scenario 1: when deadline becomes decisive

Consider a reader whose main constraint is the official 08:00 UTC cessation time. The correct response is not to infer a universal platform or product winner. It is to convert the deadline once and set a pre-deadline action time, retain the evidence, and define a stop condition before funds or permissions are committed. If the evidence changes, the decision must be reopened. This produces a repeatable operating rule rather than a one-time opinion.

Scenario 2: when open orders becomes decisive

Consider a reader whose main constraint is orders left on the affected pairs. It is to cancel intentionally and export order history, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when trading bots becomes decisive

Consider a reader whose main constraint is Spot Grid and DCA bots tied to the pairs. It is to stop affected bots manually when record clarity matters, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when token availability becomes decisive

Consider a reader whose main constraint is whether base and quote assets remain accessible elsewhere. It is to check alternative pairs before placing replacement orders, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when deposits and withdrawals becomes decisive

Consider a reader whose main constraint is network availability for underlying tokens. It is to verify the live asset and network screen before transfer, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when records becomes decisive

Consider a reader whose main constraint is orders, bot logs and account bills. It is to export non-secret records before interface changes, retain the evidence, and define a stop condition before funds or permissions are committed.

Sources and editorial method

• Bybit to Delist 3 Trading Pair(s) on Sep 24, 2026 — Bybit
• Token Management Rules — Bybit Help Center
• Spot Grid Bot — Bybit Help Center