Recherche vérifiée par sources: Bybit

Verified source facts

1. Bybit lists six affected perpetual contracts: 1000XECUSDT, BLASTUSDT, GUNUSDT, KGENUSDT, RPLUSDT and B2USDT. 2. The adjustment begins around 07:30 UTC on September 18, 2026. 3. Accounts that cannot satisfy the new requirement may be restricted to reducing the affected position. 4. The buffer period is scheduled to end at 07:30 UTC on October 5, 2026, but may end early under risk controls.

Comparison at a glance

1. Official-product check: Contract

A venue announcement becomes useful only after its rule is translated into a testable account decision. Here, contract concerns six named symbols. Retain the dated first-party wording, identify the eligible entity and product screen, and then match position. 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 wrong instrument. That unknown must remain visible rather than being converted into a prediction.

Finally, make contract reversible where possible: match position. Retain non-secret evidence and reconcile the result with the rule for six named symbols. This section evaluates operational mechanics; because wrong instrument remains unresolved, it does not predict the underlying market or recommend taking the exposure.

2. Official-product check: Effective time

Here, effective time concerns Sep 18 07:30 UTC. Retain the dated first-party wording, identify the eligible entity and product screen, and then prepare early.

The documentation can describe those controls, but it cannot resolve late change.

Finally, make effective time reversible where possible: prepare early. Retain non-secret evidence and reconcile the result with the rule for Sep 18 07:30 UTC. This section evaluates operational mechanics; because late change remains unresolved, it does not predict the underlying market or recommend taking the exposure.

3. Official-product check: Risk tier

Here, risk tier concerns supported new limit. Retain the dated first-party wording, identify the eligible entity and product screen, and then select correct tier.

The documentation can describe those controls, but it cannot resolve invalid setting.

Finally, make risk tier reversible where possible: select correct tier. Retain non-secret evidence and reconcile the result with the rule for supported new limit. This section evaluates operational mechanics; because invalid setting remains unresolved, it does not predict the underlying market or recommend taking the exposure.

4. Official-product check: Leverage

Here, leverage concerns new maximum. Retain the dated first-party wording, identify the eligible entity and product screen, and then reduce if required.

The documentation can describe those controls, but it cannot resolve margin shortfall.

Finally, make leverage reversible where possible: reduce if required. Retain non-secret evidence and reconcile the result with the rule for new maximum. This section evaluates operational mechanics; because margin shortfall remains unresolved, it does not predict the underlying market or recommend taking the exposure.

5. Official-product check: Reduce-only

Here, reduce-only concerns restriction condition. Retain the dated first-party wording, identify the eligible entity and product screen, and then test account state.

The documentation can describe those controls, but it cannot resolve blocked order.

Finally, make reduce-only reversible where possible: test account state. Retain non-secret evidence and reconcile the result with the rule for restriction condition. This section evaluates operational mechanics; because blocked order remains unresolved, it does not predict the underlying market or recommend taking the exposure.

6. Official-product check: Buffer end

Here, buffer end concerns Oct 5 07:30 UTC. Retain the dated first-party wording, identify the eligible entity and product screen, and then set earlier deadline.

The documentation can describe those controls, but it cannot resolve last-minute risk.

Finally, make buffer end reversible where possible: set earlier deadline. Retain non-secret evidence and reconcile the result with the rule for Oct 5 07:30 UTC. This section evaluates operational mechanics; because last-minute risk remains unresolved, it does not predict the underlying market or recommend taking the exposure.

7. Official-product check: Early termination

Here, early termination concerns venue discretion. Retain the dated first-party wording, identify the eligible entity and product screen, and then retain extra buffer.

The documentation can describe those controls, but it cannot resolve unexpected liquidation.

Finally, make early termination reversible where possible: retain extra buffer. Retain non-secret evidence and reconcile the result with the rule for venue discretion. This section evaluates operational mechanics; because unexpected liquidation remains unresolved, it does not predict the underlying market or recommend taking the exposure.

8. Official-product check: Copy Trading

Here, copy trading concerns positions included. Retain the dated first-party wording, identify the eligible entity and product screen, and then notify followers.

The documentation can describe those controls, but it cannot resolve unmanaged exposure.

Finally, make copy trading reversible where possible: notify followers. Retain non-secret evidence and reconcile the result with the rule for positions included. This section evaluates operational mechanics; because unmanaged exposure remains unresolved, it does not predict the underlying market or recommend taking the exposure.

9. Official-product check: Trading Bot

Here, trading bot concerns no new orders in buffer. Retain the dated first-party wording, identify the eligible entity and product screen, and then review bot.

The documentation can describe those controls, but it cannot resolve silent inactivity.

Finally, make trading bot reversible where possible: review bot. Retain non-secret evidence and reconcile the result with the rule for no new orders in buffer. This section evaluates operational mechanics; because silent inactivity remains unresolved, it does not predict the underlying market or recommend taking the exposure.

10. Official-product check: Stop rule

Here, stop rule concerns margin cannot be proven. Retain the dated first-party wording, identify the eligible entity and product screen, and then reduce exposure.

The documentation can describe those controls, but it cannot resolve support confirmation.

Finally, make stop rule reversible where possible: reduce exposure. Retain non-secret evidence and reconcile the result with the rule for margin cannot be proven. This section evaluates operational mechanics; because support confirmation remains unresolved, it does not predict the underlying market or recommend taking the exposure.

Decision scenarios

Scenario 1: when contract becomes decisive

Consider a reader whose main constraint is six named symbols. The correct response is not to infer a universal platform or product winner. It is to match position, 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 effective time becomes decisive

Consider a reader whose main constraint is Sep 18 07:30 UTC. It is to prepare early, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when risk tier becomes decisive

Consider a reader whose main constraint is supported new limit. It is to select correct tier, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when leverage becomes decisive

Consider a reader whose main constraint is new maximum. It is to reduce if required, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when reduce-only becomes decisive

Consider a reader whose main constraint is restriction condition. It is to test account state, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when buffer end becomes decisive

Consider a reader whose main constraint is Oct 5 07:30 UTC. It is to set earlier deadline, retain the evidence, and define a stop condition before funds or permissions are committed.

Sources and editorial method

• Risk limit adjustment for selected perpetual contracts — Bybit
• Maintenance updates — Bybit
• USDT contract risk limits — Bybit Help Center