Исследование с проверкой источников: Bybit

Verified source facts

1. Bybit documents three Odds product types: Up/Down, Price Target and Price Range. 2. The FAQ says the entire allocated amount is forfeited when the selected outcome is incorrect or a contract resolves as a draw. 3. Bybit publishes a taker-fee formula based on fill value, product fee rate and payout ratio. 4. The FAQ says Odds does not support demo trading or API trading and may use automatic USDT borrowing under eligible margin modes.

Comparison at a glance

1. Official-product check: Product type

A venue announcement becomes useful only after its rule is translated into a testable account decision. Here, product type concerns different outcome definitions and expiry windows. Retain the dated first-party wording, identify the eligible entity and product screen, and then read the rule for the exact contract before allocation. 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 future product additions. That unknown must remain visible rather than being converted into a prediction.

Finally, make product type reversible where possible: read the rule for the exact contract before allocation. Retain non-secret evidence and reconcile the result with the rule for different outcome definitions and expiry windows. This section evaluates operational mechanics; because future product additions remains unresolved, it does not predict the underlying market or recommend taking the exposure.

2. Official-product check: Entry price

Here, entry price concerns matched index price rather than the screen reference. Retain the dated first-party wording, identify the eligible entity and product screen, and then retain the fill record.

The documentation can describe those controls, but it cannot resolve slippage between display and match.

Finally, make entry price reversible where possible: retain the fill record. Retain non-secret evidence and reconcile the result with the rule for matched index price rather than the screen reference. This section evaluates operational mechanics; because slippage between display and match remains unresolved, it does not predict the underlying market or recommend taking the exposure.

3. Official-product check: Settlement

Here, settlement concerns instant index or thirty-minute arithmetic mean. Retain the dated first-party wording, identify the eligible entity and product screen, and then map the selected contract to its method.

The documentation can describe those controls, but it cannot resolve feed behavior during disruption.

Finally, make settlement reversible where possible: map the selected contract to its method. Retain non-secret evidence and reconcile the result with the rule for instant index or thirty-minute arithmetic mean. This section evaluates operational mechanics; because feed behavior during disruption remains unresolved, it does not predict the underlying market or recommend taking the exposure.

4. Official-product check: Draw handling

Here, draw handling concerns exact-boundary treatment. Retain the dated first-party wording, identify the eligible entity and product screen, and then treat a draw as a full-loss scenario.

The documentation can describe those controls, but it cannot resolve probability of an exact boundary.

Finally, make draw handling reversible where possible: treat a draw as a full-loss scenario. Retain non-secret evidence and reconcile the result with the rule for exact-boundary treatment. This section evaluates operational mechanics; because probability of an exact boundary remains unresolved, it does not predict the underlying market or recommend taking the exposure.

5. Official-product check: Payout ratio

Here, payout ratio concerns market-maker quote and displayed return. Retain the dated first-party wording, identify the eligible entity and product screen, and then separate gross return from net profit.

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

Finally, make payout ratio reversible where possible: separate gross return from net profit. Retain non-secret evidence and reconcile the result with the rule for market-maker quote and displayed return. This section evaluates operational mechanics; because future quote quality remains unresolved, it does not predict the underlying market or recommend taking the exposure.

6. Official-product check: Fee formula

Here, fee formula concerns fee outside the allocated amount. Retain the dated first-party wording, identify the eligible entity and product screen, and then calculate the fee before confirming.

The documentation can describe those controls, but it cannot resolve account-specific displayed rate.

Finally, make fee formula reversible where possible: calculate the fee before confirming. Retain non-secret evidence and reconcile the result with the rule for fee outside the allocated amount. This section evaluates operational mechanics; because account-specific displayed rate remains unresolved, it does not predict the underlying market or recommend taking the exposure.

7. Official-product check: Borrowing

Here, borrowing concerns automatic USDT borrowing in margin modes. Retain the dated first-party wording, identify the eligible entity and product screen, and then disable or account for borrowing before entry.

The documentation can describe those controls, but it cannot resolve liquidation effect for a specific portfolio.

Finally, make borrowing reversible where possible: disable or account for borrowing before entry. Retain non-secret evidence and reconcile the result with the rule for automatic USDT borrowing in margin modes. This section evaluates operational mechanics; because liquidation effect for a specific portfolio remains unresolved, it does not predict the underlying market or recommend taking the exposure.

8. Official-product check: Suspension

Here, suspension concerns new-order halt during abnormal conditions. Retain the dated first-party wording, identify the eligible entity and product screen, and then define a no-entry stop condition.

The documentation can describe those controls, but it cannot resolve timing of a future suspension.

Finally, make suspension reversible where possible: define a no-entry stop condition. Retain non-secret evidence and reconcile the result with the rule for new-order halt during abnormal conditions. This section evaluates operational mechanics; because timing of a future suspension remains unresolved, it does not predict the underlying market or recommend taking the exposure.

9. Official-product check: Automation

Here, automation concerns no demo or API trading. Retain the dated first-party wording, identify the eligible entity and product screen, and then avoid designing an unsupported bot workflow.

The documentation can describe those controls, but it cannot resolve whether API access will be added.

Finally, make automation reversible where possible: avoid designing an unsupported bot workflow. Retain non-secret evidence and reconcile the result with the rule for no demo or API trading. This section evaluates operational mechanics; because whether API access will be added remains unresolved, it does not predict the underlying market or recommend taking the exposure.

10. Official-product check: Eligibility

Here, eligibility concerns region, entity and account access. Retain the dated first-party wording, identify the eligible entity and product screen, and then verify the signed-in product page.

The documentation can describe those controls, but it cannot resolve availability for a particular reader.

Finally, make eligibility reversible where possible: verify the signed-in product page. Retain non-secret evidence and reconcile the result with the rule for region, entity and account access. This section evaluates operational mechanics; because availability for a particular reader remains unresolved, it does not predict the underlying market or recommend taking the exposure.

Decision scenarios

Scenario 1: when product type becomes decisive

Consider a reader whose main constraint is different outcome definitions and expiry windows. The correct response is not to infer a universal platform or product winner. It is to read the rule for the exact contract before allocation, 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 entry price becomes decisive

Consider a reader whose main constraint is matched index price rather than the screen reference. It is to retain the fill record, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when settlement becomes decisive

Consider a reader whose main constraint is instant index or thirty-minute arithmetic mean. It is to map the selected contract to its method, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when draw handling becomes decisive

Consider a reader whose main constraint is exact-boundary treatment. It is to treat a draw as a full-loss scenario, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when payout ratio becomes decisive

Consider a reader whose main constraint is market-maker quote and displayed return. It is to separate gross return from net profit, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when fee formula becomes decisive

Consider a reader whose main constraint is fee outside the allocated amount. It is to calculate the fee before confirming, retain the evidence, and define a stop condition before funds or permissions are committed.