Дослідження з перевіркою джерел: Binance

Verified source facts

1. Pairs,The notice names ENJ/USDC, GENIUS/USDC, CVX/USDC, GUN/USDC and VANA/USDC for cross margin, and GENIUS/USDC for isolated margin.,binance-removal 2. Borrowing,Isolated margin borrowing for the named isolated pair was scheduled to stop on September 16 at 06:00 UTC.,binance-removal 3. Removal,At September 18 06:00 UTC, Binance says it will close positions, settle automatically and cancel pending orders.,binance-removal 4. Other pairs,The base and quote assets may remain available through other margin pairs.,binance-removal

Comparison at a glance

1. Official-product check: Scope

A venue announcement becomes useful only after its rule is translated into a testable account decision. Here, scope concerns cross or isolated pair. Retain the dated first-party wording, identify the eligible entity and product screen, and then match account mode. 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-account action. That unknown must remain visible rather than being converted into a prediction.

Finally, make scope reversible where possible: match account mode. Retain non-secret evidence and reconcile the result with the rule for cross or isolated pair. This section evaluates operational mechanics; because wrong-account action remains unresolved, it does not predict the underlying market or recommend taking the exposure.

2. Official-product check: Transfer

Here, transfer concerns manual and auto-transfer restriction. Retain the dated first-party wording, identify the eligible entity and product screen, and then stop new inflow.

The documentation can describe those controls, but it cannot resolve trapped balance.

Finally, make transfer reversible where possible: stop new inflow. Retain non-secret evidence and reconcile the result with the rule for manual and auto-transfer restriction. This section evaluates operational mechanics; because trapped balance remains unresolved, it does not predict the underlying market or recommend taking the exposure.

3. Official-product check: Borrowing

Here, borrowing concerns isolated suspension time. Retain the dated first-party wording, identify the eligible entity and product screen, and then repay early.

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

Finally, make borrowing reversible where possible: repay early. Retain non-secret evidence and reconcile the result with the rule for isolated suspension time. This section evaluates operational mechanics; because new liability blocked remains unresolved, it does not predict the underlying market or recommend taking the exposure.

4. Official-product check: Orders

Here, orders concerns open orders cancelled. Retain the dated first-party wording, identify the eligible entity and product screen, and then export and cancel.

The documentation can describe those controls, but it cannot resolve execution surprise.

Finally, make orders reversible where possible: export and cancel. Retain non-secret evidence and reconcile the result with the rule for open orders cancelled. This section evaluates operational mechanics; because execution surprise remains unresolved, it does not predict the underlying market or recommend taking the exposure.

5. Official-product check: Positions

Here, positions concerns automatic closure. Retain the dated first-party wording, identify the eligible entity and product screen, and then reduce before window.

The documentation can describe those controls, but it cannot resolve forced close.

Finally, make positions reversible where possible: reduce before window. Retain non-secret evidence and reconcile the result with the rule for automatic closure. This section evaluates operational mechanics; because forced close remains unresolved, it does not predict the underlying market or recommend taking the exposure.

6. Official-product check: Settlement

Here, settlement concerns liability handling. Retain the dated first-party wording, identify the eligible entity and product screen, and then reconcile ledger.

The documentation can describe those controls, but it cannot resolve residual debt.

Finally, make settlement reversible where possible: reconcile ledger. Retain non-secret evidence and reconcile the result with the rule for liability handling. This section evaluates operational mechanics; because residual debt remains unresolved, it does not predict the underlying market or recommend taking the exposure.

7. Official-product check: Timing

Here, timing concerns 06:00 UTC deadline. Retain the dated first-party wording, identify the eligible entity and product screen, and then convert locally.

The documentation can describe those controls, but it cannot resolve timezone error.

Finally, make timing reversible where possible: convert locally. Retain non-secret evidence and reconcile the result with the rule for 06:00 UTC deadline. This section evaluates operational mechanics; because timezone error remains unresolved, it does not predict the underlying market or recommend taking the exposure.

8. Official-product check: Duration

Here, duration concerns approximately three hours. Retain the dated first-party wording, identify the eligible entity and product screen, and then avoid changes during process.

The documentation can describe those controls, but it cannot resolve partial state.

Finally, make duration reversible where possible: avoid changes during process. Retain non-secret evidence and reconcile the result with the rule for approximately three hours. This section evaluates operational mechanics; because partial state remains unresolved, it does not predict the underlying market or recommend taking the exposure.

9. Official-product check: Other markets

Here, other markets concerns asset may remain elsewhere. Retain the dated first-party wording, identify the eligible entity and product screen, and then verify exact pair.

The documentation can describe those controls, but it cannot resolve false delisting inference.

Finally, make other markets reversible where possible: verify exact pair. Retain non-secret evidence and reconcile the result with the rule for asset may remain elsewhere. This section evaluates operational mechanics; because false delisting inference remains unresolved, it does not predict the underlying market or recommend taking the exposure.

10. Official-product check: Evidence

Here, evidence concerns post-event account history. Retain the dated first-party wording, identify the eligible entity and product screen, and then retain non-secret export.

The documentation can describe those controls, but it cannot resolve unresolved discrepancy.

Finally, make evidence reversible where possible: retain non-secret export. Retain non-secret evidence and reconcile the result with the rule for post-event account history. This section evaluates operational mechanics; because unresolved discrepancy remains unresolved, it does not predict the underlying market or recommend taking the exposure.

Decision scenarios

Scenario 1: when scope becomes decisive

Consider a reader whose main constraint is cross or isolated pair. The correct response is not to infer a universal platform or product winner. It is to match account mode, 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 transfer becomes decisive

Consider a reader whose main constraint is manual and auto-transfer restriction. It is to stop new inflow, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when borrowing becomes decisive

Consider a reader whose main constraint is isolated suspension time. It is to repay early, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when orders becomes decisive

Consider a reader whose main constraint is open orders cancelled. It is to export and cancel, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when positions becomes decisive

Consider a reader whose main constraint is automatic closure. It is to reduce before window, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when settlement becomes decisive

Consider a reader whose main constraint is liability handling. It is to reconcile ledger, retain the evidence, and define a stop condition before funds or permissions are committed.

Sources and editorial method

• Margin pair removal notice — Binance
• Official announcements — Binance
• Collateral eligibility boundary — Binance