Kaynak doğrulamalı araştırma: Binance

Verified source facts

1. Binance states that HIMSB and CRMB became margin collateral on September 9, 2026 at 12:00 UTC. 2. The notice names Cross Margin, Portfolio Margin and Portfolio Margin Pro as the covered account modes. 3. Eligibility is limited to VIP 3 or higher users in permitted jurisdictions, and borrowing of the two bStocks is not supported. 4. The notice describes bStocks as certificates and says holders do not directly own the underlying shares.

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 official UTC activation time. Retain the dated first-party wording, identify the eligible entity and product screen, and then record the timestamp and current account display. 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 schedule changes. That unknown must remain visible rather than being converted into a prediction.

Finally, make effective time reversible where possible: record the timestamp and current account display. Retain non-secret evidence and reconcile the result with the rule for official UTC activation time. This section evaluates operational mechanics; because later schedule changes remains unresolved, it does not predict the underlying market or recommend taking the exposure.

2. Official-product check: Jurisdiction

Here, jurisdiction concerns permitted-country access. Retain the dated first-party wording, identify the eligible entity and product screen, and then verify signed-in eligibility.

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

Finally, make jurisdiction reversible where possible: verify signed-in eligibility. Retain non-secret evidence and reconcile the result with the rule for permitted-country access. This section evaluates operational mechanics; because future restrictions remains unresolved, it does not predict the underlying market or recommend taking the exposure.

3. Official-product check: VIP tier

Here, vip tier concerns VIP 3 or higher requirement. Retain the dated first-party wording, identify the eligible entity and product screen, and then confirm the live account tier.

The documentation can describe those controls, but it cannot resolve tier recalculation.

Finally, make vip tier reversible where possible: confirm the live account tier. Retain non-secret evidence and reconcile the result with the rule for VIP 3 or higher requirement. This section evaluates operational mechanics; because tier recalculation remains unresolved, it does not predict the underlying market or recommend taking the exposure.

4. Official-product check: Account mode

Here, account mode concerns Cross or Portfolio Margin support. Retain the dated first-party wording, identify the eligible entity and product screen, and then confirm the exact active mode.

The documentation can describe those controls, but it cannot resolve entity-specific availability.

Finally, make account mode reversible where possible: confirm the exact active mode. Retain non-secret evidence and reconcile the result with the rule for Cross or Portfolio Margin support. This section evaluates operational mechanics; because entity-specific availability remains unresolved, it does not predict the underlying market or recommend taking the exposure.

5. Official-product check: Collateral ratio

Here, collateral ratio concerns recognized value for margin. Retain the dated first-party wording, identify the eligible entity and product screen, and then read the live collateral table.

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

Finally, make collateral ratio reversible where possible: read the live collateral table. Retain non-secret evidence and reconcile the result with the rule for recognized value for margin. This section evaluates operational mechanics; because ratio changes remains unresolved, it does not predict the underlying market or recommend taking the exposure.

6. Official-product check: Borrowing

Here, borrowing concerns collateral use without borrowing support. Retain the dated first-party wording, identify the eligible entity and product screen, and then do not design a borrow workflow.

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

Finally, make borrowing reversible where possible: do not design a borrow workflow. Retain non-secret evidence and reconcile the result with the rule for collateral use without borrowing support. This section evaluates operational mechanics; because future product changes remains unresolved, it does not predict the underlying market or recommend taking the exposure.

7. Official-product check: Legal form

Here, legal form concerns certificate rather than direct share. Retain the dated first-party wording, identify the eligible entity and product screen, and then read the issuer and prospectus documents.

The documentation can describe those controls, but it cannot resolve claim enforceability.

Finally, make legal form reversible where possible: read the issuer and prospectus documents. Retain non-secret evidence and reconcile the result with the rule for certificate rather than direct share. This section evaluates operational mechanics; because claim enforceability remains unresolved, it does not predict the underlying market or recommend taking the exposure.

8. Official-product check: Liquidation

Here, liquidation concerns treatment during margin shortfall. Retain the dated first-party wording, identify the eligible entity and product screen, and then model a stressed collateral haircut.

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

Finally, make liquidation reversible where possible: model a stressed collateral haircut. Retain non-secret evidence and reconcile the result with the rule for treatment during margin shortfall. This section evaluates operational mechanics; because stress execution remains unresolved, it does not predict the underlying market or recommend taking the exposure.

9. Official-product check: Liquidity

Here, liquidity concerns exit route and market depth. Retain the dated first-party wording, identify the eligible entity and product screen, and then test with a reversible size.

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

Finally, make liquidity reversible where possible: test with a reversible size. Retain non-secret evidence and reconcile the result with the rule for exit route and market depth. This section evaluates operational mechanics; because future spreads remains unresolved, it does not predict the underlying market or recommend taking the exposure.

10. Official-product check: Records

Here, records concerns orders, collateral valuation and notices. Retain the dated first-party wording, identify the eligible entity and product screen, and then retain dated non-secret evidence.

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

Finally, make records reversible where possible: retain dated non-secret evidence. Retain non-secret evidence and reconcile the result with the rule for orders, collateral valuation and notices. This section evaluates operational mechanics; because retention period 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 official UTC activation time. The correct response is not to infer a universal platform or product winner. It is to record the timestamp and current account display, 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 jurisdiction becomes decisive

Consider a reader whose main constraint is permitted-country access. It is to verify signed-in eligibility, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when vip tier becomes decisive

Consider a reader whose main constraint is VIP 3 or higher requirement. It is to confirm the live account tier, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when account mode becomes decisive

Consider a reader whose main constraint is Cross or Portfolio Margin support. It is to confirm the exact active mode, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when collateral ratio becomes decisive

Consider a reader whose main constraint is recognized value for margin. It is to read the live collateral table, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when borrowing becomes decisive

Consider a reader whose main constraint is collateral use without borrowing support. It is to do not design a borrow workflow, retain the evidence, and define a stop condition before funds or permissions are committed.