출처 검증 리서치: Crypto Lending Collateral TIER

Verified source facts

1. State change,The notice changes both tier structure and ratios.,bybit-update 2. Cross-product scope,The same announcement spans four loan products.,bybit-update 3. Account impact,Bybit says collateral value may change.,bybit-update 4. Action boundary,The notice directs users to review positions before effectiveness.,bybit-update

Comparison at a glance

1. Control test: Eligibility

A trading-control disclosure is meaningful only when converted into a testable rule. For eligibility, inspect product, region and account. Use a sandbox, non-production context, or the smallest reversible test available, then verify live access. Capture configuration and event evidence without recording credentials, and verify the documented cancel, reject, decrement, or history behavior.

Model the failure path, not just the setup path. Ask which strategy owns the maker and taker orders, which account boundary the venue evaluates, which message reveals intervention, and how reconciliation behaves after a partial fill or disconnect. Platform documentation describes supported settings; it cannot prove that an operator configured them correctly. In this dimension, false entitlement is therefore an explicit audit gap.

The eligibility row should end with a concrete monitoring rule tied to product, region and account. Make the operator verify live access, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; false entitlement remains a separate production risk until observed.

2. Control test: Effective time

For effective time, inspect dated UTC transition. Use a sandbox, non-production context, or the smallest reversible test available, then convert locally.

In this dimension, missed deadline is therefore an explicit audit gap.

The effective time row should end with a concrete monitoring rule tied to dated UTC transition. Make the operator convert locally, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; missed deadline remains a separate production risk until observed.

3. Control test: Tier

For tier, inspect quantity band and ratio. Use a sandbox, non-production context, or the smallest reversible test available, then map current balance.

In this dimension, wrong bucket is therefore an explicit audit gap.

The tier row should end with a concrete monitoring rule tied to quantity band and ratio. Make the operator map current balance, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; wrong bucket remains a separate production risk until observed.

4. Control test: Valuation

For valuation, inspect collateral ratio or haircut. Use a sandbox, non-production context, or the smallest reversible test available, then stress lower value.

In this dimension, buffer erosion is therefore an explicit audit gap.

The valuation row should end with a concrete monitoring rule tied to collateral ratio or haircut. Make the operator stress lower value, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; buffer erosion remains a separate production risk until observed.

5. Control test: Debt

For debt, inspect outstanding principal and interest. Use a sandbox, non-production context, or the smallest reversible test available, then recalculate health.

In this dimension, liquidation is therefore an explicit audit gap.

The debt row should end with a concrete monitoring rule tied to outstanding principal and interest. Make the operator recalculate health, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; liquidation remains a separate production risk until observed.

6. Control test: Transfers

For transfers, inspect deposit and withdrawal state. Use a sandbox, non-production context, or the smallest reversible test available, then verify route.

In this dimension, trapped funds is therefore an explicit audit gap.

The transfers row should end with a concrete monitoring rule tied to deposit and withdrawal state. Make the operator verify route, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; trapped funds remains a separate production risk until observed.

7. Control test: Orders

For orders, inspect open positions and orders. Use a sandbox, non-production context, or the smallest reversible test available, then inventory exposure.

In this dimension, orphan strategy is therefore an explicit audit gap.

The orders row should end with a concrete monitoring rule tied to open positions and orders. Make the operator inventory exposure, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; orphan strategy remains a separate production risk until observed.

8. Control test: Disclosure

For disclosure, inspect official dated source. Use a sandbox, non-production context, or the smallest reversible test available, then retain evidence.

In this dimension, stale assumption is therefore an explicit audit gap.

The disclosure row should end with a concrete monitoring rule tied to official dated source. Make the operator retain evidence, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; stale assumption remains a separate production risk until observed.

9. Control test: Recovery

For recovery, inspect post-change account state. Use a sandbox, non-production context, or the smallest reversible test available, then reconcile balances.

In this dimension, silent mismatch is therefore an explicit audit gap.

The recovery row should end with a concrete monitoring rule tied to post-change account state. Make the operator reconcile balances, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; silent mismatch remains a separate production risk until observed.

10. Control test: Stop rule

For stop rule, inspect unverified control or status. Use a sandbox, non-production context, or the smallest reversible test available, then do not add risk.

In this dimension, irreversible loss is therefore an explicit audit gap.

The stop rule row should end with a concrete monitoring rule tied to unverified control or status. Make the operator do not add risk, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; irreversible loss remains a separate production risk until observed.

Sources and editorial method

• Collateral tier update — Bybit
• Maintenance registry — Bybit
• Structured market-data method reference — SEC