Riset terverifikasi sumber: Bybit

Verified source facts

1. Bybit published the adjustment notice on September 9, 2026 with an effective time of September 11 at 08:00 UTC. 2. The notice lists changed maximum-leverage ceilings for specified contracts rather than a platform-wide entitlement for every account and position. 3. Bybit says effective position value includes open positions and active orders and can move the account between risk-limit tiers in real time. 4. Bybit says higher tiers can increase initial and maintenance margin requirements, while portfolio-margin accounts use a different portfolio-level risk calculation.

Comparison at a glance

1. Official-product check: Effective time

A venue announcement becomes useful only after its rule is translated into a testable account decision. Here, effective time concerns UTC deadline and local conversion. Retain the dated first-party wording, identify the eligible entity and product screen, and then record the exact effective timestamp. 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 later amendments. That unknown must remain visible rather than being converted into a prediction.

Finally, make effective time reversible where possible: record the exact effective timestamp. Retain non-secret evidence and reconcile the result with the rule for UTC deadline and local conversion. This section evaluates operational mechanics; because later amendments remains unresolved, it does not predict the underlying market or recommend taking the exposure.

2. Official-product check: Affected contract

Here, affected contract concerns symbol-specific change. Retain the dated first-party wording, identify the eligible entity and product screen, and then open the current contract rule page.

The documentation can describe those controls, but it cannot resolve future list changes.

Finally, make affected contract reversible where possible: open the current contract rule page. Retain non-secret evidence and reconcile the result with the rule for symbol-specific change. This section evaluates operational mechanics; because future list changes remains unresolved, it does not predict the underlying market or recommend taking the exposure.

3. Official-product check: Maximum leverage

Here, maximum leverage concerns ceiling rather than recommended leverage. Retain the dated first-party wording, identify the eligible entity and product screen, and then set a lower risk-owned limit.

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

Finally, make maximum leverage reversible where possible: set a lower risk-owned limit. Retain non-secret evidence and reconcile the result with the rule for ceiling rather than recommended leverage. This section evaluates operational mechanics; because account eligibility remains unresolved, it does not predict the underlying market or recommend taking the exposure.

4. Official-product check: Position value

Here, position value concerns open positions plus active orders. Retain the dated first-party wording, identify the eligible entity and product screen, and then calculate effective exposure before changing leverage.

The documentation can describe those controls, but it cannot resolve mark-price movement.

Finally, make position value reversible where possible: calculate effective exposure before changing leverage. Retain non-secret evidence and reconcile the result with the rule for open positions plus active orders. This section evaluates operational mechanics; because mark-price movement remains unresolved, it does not predict the underlying market or recommend taking the exposure.

5. Official-product check: Risk tier

Here, risk tier concerns dynamic tier selection. Retain the dated first-party wording, identify the eligible entity and product screen, and then inspect the current tier after any order change.

The documentation can describe those controls, but it cannot resolve venue parameter updates.

Finally, make risk tier reversible where possible: inspect the current tier after any order change. Retain non-secret evidence and reconcile the result with the rule for dynamic tier selection. This section evaluates operational mechanics; because venue parameter updates remains unresolved, it does not predict the underlying market or recommend taking the exposure.

6. Official-product check: Initial margin

Here, initial margin concerns capital required to open exposure. Retain the dated first-party wording, identify the eligible entity and product screen, and then recalculate before submitting an order.

The documentation can describe those controls, but it cannot resolve execution-time requirement.

Finally, make initial margin reversible where possible: recalculate before submitting an order. Retain non-secret evidence and reconcile the result with the rule for capital required to open exposure. This section evaluates operational mechanics; because execution-time requirement remains unresolved, it does not predict the underlying market or recommend taking the exposure.

7. Official-product check: Maintenance margin

Here, maintenance margin concerns threshold relevant to liquidation. Retain the dated first-party wording, identify the eligible entity and product screen, and then retain an explicit buffer.

The documentation can describe those controls, but it cannot resolve volatility and fee effects.

Finally, make maintenance margin reversible where possible: retain an explicit buffer. Retain non-secret evidence and reconcile the result with the rule for threshold relevant to liquidation. This section evaluates operational mechanics; because volatility and fee effects remains unresolved, it does not predict the underlying market or recommend taking the exposure.

8. Official-product check: Margin mode

Here, margin mode concerns isolated, cross or portfolio treatment. Retain the dated first-party wording, identify the eligible entity and product screen, and then verify the active account mode.

The documentation can describe those controls, but it cannot resolve portfolio stress assumptions.

Finally, make margin mode reversible where possible: verify the active account mode. Retain non-secret evidence and reconcile the result with the rule for isolated, cross or portfolio treatment. This section evaluates operational mechanics; because portfolio stress assumptions remains unresolved, it does not predict the underlying market or recommend taking the exposure.

9. Official-product check: Open orders

Here, open orders concerns orders can increase effective exposure. Retain the dated first-party wording, identify the eligible entity and product screen, and then review dormant and conditional orders.

The documentation can describe those controls, but it cannot resolve trigger timing.

Finally, make open orders reversible where possible: review dormant and conditional orders. Retain non-secret evidence and reconcile the result with the rule for orders can increase effective exposure. This section evaluates operational mechanics; because trigger timing remains unresolved, it does not predict the underlying market or recommend taking the exposure.

10. Official-product check: Decision boundary

Here, decision boundary concerns operational rule change, not a market forecast. Retain the dated first-party wording, identify the eligible entity and product screen, and then separate leverage availability from suitability.

The documentation can describe those controls, but it cannot resolve future price path.

Finally, make decision boundary reversible where possible: separate leverage availability from suitability. Retain non-secret evidence and reconcile the result with the rule for operational rule change, not a market forecast. This section evaluates operational mechanics; because future price path remains unresolved, it does not predict the underlying market or recommend taking the exposure.

Decision scenarios

Scenario 1: when effective time becomes decisive

Consider a reader whose main constraint is UTC deadline and local conversion. The correct response is not to infer a universal platform or product winner. It is to record the exact effective timestamp, 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 affected contract becomes decisive

Consider a reader whose main constraint is symbol-specific change. It is to open the current contract rule page, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when maximum leverage becomes decisive

Consider a reader whose main constraint is ceiling rather than recommended leverage. It is to set a lower risk-owned limit, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when position value becomes decisive

Consider a reader whose main constraint is open positions plus active orders. It is to calculate effective exposure before changing leverage, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when risk tier becomes decisive

Consider a reader whose main constraint is dynamic tier selection. It is to inspect the current tier after any order change, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when initial margin becomes decisive

Consider a reader whose main constraint is capital required to open exposure. It is to recalculate before submitting an order, retain the evidence, and define a stop condition before funds or permissions are committed.