Дослідження з перевіркою джерел: Crypto Collateral Alert Liquidation

Decision Matrix

Source Map

• Bybit Help Center: Platform Collateral Limit (bybit-platform-collateral)
• Bybit Help Center: FAQ — Crypto Loans (bybit-crypto-loans-faq)
• OKX Help: Introduction to the platform collateralized borrowing limit (okx-platform-limit)
• OKX Help: Introduction to margin trading (okx-margin-intro)

Control Notes

1. Trigger

Trigger is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means usage cap, LTV, margin ratio or borrowing state. The useful action is to record the exact trigger. The unresolved edge is private account state, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, trigger should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material. The record can stay simple: the official source URL, the date checked, the product or network under review, and a non-secret note describing why the next step is acceptable. Screenshots should avoid balances, identity documents, API keys, recovery phrases, private keys, passphrases, verification codes and support-ticket private data.

2. Visible alert

Visible alert is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means icon, email, SMS, push or page warning. The useful action is to capture non-secret wording. The unresolved edge is delivery failure, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, visible alert should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

3. Machine check

Machine check is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means API or UI state that can be queried. The useful action is to prefer read-only verification. The unresolved edge is permission requirement, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, machine check should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

4. Restriction

Restriction is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means new collateral, borrow, transfer or liquidation block. The useful action is to separate each action. The unresolved edge is risk-engine edge cases, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, restriction should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

5. Formula

Formula is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means LTV, haircut, margin rate or adjusted equity. The useful action is to cite the formula before calculating. The unresolved edge is future parameter changes, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, formula should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

6. Delay caveat

Delay caveat is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means whether notification timing is guaranteed. The useful action is to plan without assuming alert delivery. The unresolved edge is incident load, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, delay caveat should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

7. User action

User action is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means repay, reduce exposure, add different collateral or stop. The useful action is to predefine fallback. The unresolved edge is execution quality, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, user action should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

8. Platform cap

Platform cap is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means constraint shared across users. The useful action is to avoid treating it as personal balance only. The unresolved edge is cap utilization data, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, platform cap should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

9. Evidence packet

Evidence packet is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means official URL, date, trigger and non-secret screenshot. The useful action is to avoid balances and IDs. The unresolved edge is support case facts, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

10. Stop rule

Stop rule is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means when radar status is not publishable. The useful action is to stop if trigger, alert, formula or restriction cannot be sourced. The unresolved edge is future help-center edits, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

Known Unknowns

• private account state
• delivery failure
• permission requirement
• risk-engine edge cases
• future parameter changes
• incident load
• execution quality
• cap utilization data
• support case facts
• future help-center edits

Practical Takeaway

The safest version of this article is the one that stays boring and exact. NexuAlpha's collateral radar treats alert delivery, platform caps and liquidation formulas as separate evidence fields. Bybit's platform collateral-limit page says yellow and red warning icons and notifications can appear as collateral usage approaches or reaches a platform limit, but it also tells users not to rely solely on system notifications. Bybit's Crypto Loans FAQ says margin-call and liquidation thresholds can trigger email, SMS and push alerts, while warning that risk alerts may be delayed or experience glitches. OKX describes a separate platform-wide collateralized borrowing limit whose impact depends on account mode and borrowing state. A useful radar therefore records five fields for every venue: trigger, user-visible alert, machine-readable check, transfer or borrow restriction, and liquidation or repayment action. The user outcome is a clearer next inspection step, not a promise that a platform, API, transfer route or tokenized asset will work under every future condition.