출처 검증 리서치: Bybit / OKX

Decision Matrix

Source Map

• Bybit Help Center: Platform Collateral Limit (bybit-platform-collateral)
• Bybit Help Center: Key Terms and Formulas in Unified Trading Account (bybit-uta-terms)
• OKX Help: Introduction to the platform collateralized borrowing limit (okx-platform-limit)
• OKX Help: Introduction to margin trading (okx-margin-intro)

Control Notes

1. Product scope

Product scope is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means which margin, loan or account mode is affected. The useful action is to map the product before adding collateral. The unresolved edge is regional product availability, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, product scope 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. Limit trigger

Limit trigger is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means platform-wide usage rather than only personal balance. The useful action is to treat cap warnings as external constraints. The unresolved edge is real-time utilization source, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

3. Unaffected scenario

Unaffected scenario is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means cases where trading or transfers may continue. The useful action is to separate no-borrowing and borrowing-on states. The unresolved edge is account-specific mode, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

4. Haircut

Haircut is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means asset value reduced for collateral calculation. The useful action is to check adjusted value before borrowing. The unresolved edge is future ratio changes, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

5. LTV or margin signal

LTV or margin signal is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means where liquidation pressure appears. The useful action is to read the venue-specific formula. The unresolved edge is private position data, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

6. Warning delivery

Warning delivery is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means UI icon, in-app, email or API visibility. The useful action is to do not rely on alerts alone. The unresolved edge is notification delay, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

7. API check

API check is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means machine-readable balance or position endpoint. The useful action is to build read-only checks before automation. The unresolved edge is endpoint permission scope, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

8. Transfer restriction

Transfer restriction is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means whether assets can still leave the account. The useful action is to test transfer rules without moving value. 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, transfer restriction should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

9. Fallback action

Fallback 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 or choose another asset. The useful action is to decide before cap pressure. The unresolved edge is market liquidity, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

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 comparison is not decision-quality. The useful action is to stop if account mode, cap status or borrowing state is unknown. The unresolved edge is future policy update, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

Known Unknowns

• regional product availability
• real-time utilization source
• account-specific mode
• future ratio changes
• private position data
• notification delay
• endpoint permission scope
• risk-engine edge cases
• market liquidity
• future policy update

Practical Takeaway

The safest version of this article is the one that stays boring and exact. Bybit and OKX both describe platform-level collateral or borrowing limits, but the useful comparison is how each tells the user what changes when a limit is near or reached. Bybit says a platform collateral limit can restrict new collateral use across UTA cross margin, portfolio margin, crypto loans and institutional loans; yellow and red warning icons can signal approaching or reached usage, and API users can inspect wallet balance or loan-position endpoints. OKX says its platform-wide collateralized borrowing limit considers factors such as liquidity, trading depth, total platform volume and borrowing volume, and that impact depends on account mode and whether borrowing is active. The decision outcome is to map product scope, limit trigger, unaffected scenarios, alert delivery, API check and liquidation exposure before comparing either venue as safer. 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.