Дослідження з перевіркою джерел: Binance / OKX / Coinbase

Verified source facts

1. Major venues publish separate service-status or network-status surfaces in addition to their marketing homepages. 2. A general platform status can remain operational while one asset, network, region or wallet action is degraded or suspended. 3. An authenticated wallet may expose account-specific network choices, minimums, fees and destination requirements not visible on a public status page. 4. A completed small transfer is evidence for that route at that time, not a guarantee of future availability.

Comparison at a glance

1. Control test: Homepage

A trading-control disclosure is meaningful only when converted into a testable rule. For homepage, inspect general web availability. Use a sandbox, non-production context, or the smallest reversible test available, then treat as a weak first signal. 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, wallet-path health is therefore an explicit audit gap.

The homepage row should end with a concrete monitoring rule tied to general web availability. Make the operator treat as a weak first signal, 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; wallet-path health remains a separate production risk until observed.

2. Control test: Incident page

For incident page, inspect declared service degradation. Use a sandbox, non-production context, or the smallest reversible test available, then check component history.

In this dimension, undeclared issue is therefore an explicit audit gap.

The incident page row should end with a concrete monitoring rule tied to declared service degradation. Make the operator check component history, 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; undeclared issue remains a separate production risk until observed.

3. Control test: Asset status

For asset status, inspect coin-specific availability. Use a sandbox, non-production context, or the smallest reversible test available, then match the exact asset.

In this dimension, regional difference is therefore an explicit audit gap.

The asset status row should end with a concrete monitoring rule tied to coin-specific availability. Make the operator match the exact asset, 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; regional difference remains a separate production risk until observed.

4. Control test: Network status

For network status, inspect chain-specific deposit and withdrawal. Use a sandbox, non-production context, or the smallest reversible test available, then match both endpoints.

In this dimension, node lag is therefore an explicit audit gap.

The network status row should end with a concrete monitoring rule tied to chain-specific deposit and withdrawal. Make the operator match both endpoints, 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; node lag remains a separate production risk until observed.

5. Control test: Authenticated view

For authenticated view, inspect account-specific selectable route. Use a sandbox, non-production context, or the smallest reversible test available, then verify immediately before action.

In this dimension, hidden eligibility is therefore an explicit audit gap.

The authenticated view row should end with a concrete monitoring rule tied to account-specific selectable route. Make the operator verify immediately before action, 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; hidden eligibility remains a separate production risk until observed.

6. Control test: Address fields

For address fields, inspect network, memo and destination. Use a sandbox, non-production context, or the smallest reversible test available, then compare character by character.

In this dimension, recovery outcome is therefore an explicit audit gap.

The address fields row should end with a concrete monitoring rule tied to network, memo and destination. Make the operator compare character by character, 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; recovery outcome remains a separate production risk until observed.

7. Control test: Fees and limits

For fees and limits, inspect live minimum and withdrawal fee. Use a sandbox, non-production context, or the smallest reversible test available, then read the final screen.

In this dimension, future change is therefore an explicit audit gap.

The fees and limits row should end with a concrete monitoring rule tied to live minimum and withdrawal fee. Make the operator read the final screen, 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; future change remains a separate production risk until observed.

8. Control test: Test transfer

For test transfer, inspect small end-to-end evidence. Use a sandbox, non-production context, or the smallest reversible test available, then confirm credited balance.

In this dimension, later outage is therefore an explicit audit gap.

The test transfer row should end with a concrete monitoring rule tied to small end-to-end evidence. Make the operator confirm credited 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; later outage remains a separate production risk until observed.

9. Control test: Monitoring

For monitoring, inspect status change and confirmation delay. Use a sandbox, non-production context, or the smallest reversible test available, then set time-based alerts.

In this dimension, provider telemetry is therefore an explicit audit gap.

The monitoring row should end with a concrete monitoring rule tied to status change and confirmation delay. Make the operator set time-based alerts, 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; provider telemetry remains a separate production risk until observed.

10. Control test: Stop rule

For stop rule, inspect any disagreement across layers. Use a sandbox, non-production context, or the smallest reversible test available, then pause and re-verify.

In this dimension, support response time is therefore an explicit audit gap.

The stop rule row should end with a concrete monitoring rule tied to any disagreement across layers. Make the operator pause and re-verify, 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; support response time remains a separate production risk until observed.

Decision scenarios

Scenario 1: when homepage becomes decisive

Consider a reader whose main constraint is general web availability. The correct response is not to infer a universal platform or product winner. It is to treat as a weak first signal, 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 incident page becomes decisive

Consider a reader whose main constraint is declared service degradation. It is to check component history, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when asset status becomes decisive

Consider a reader whose main constraint is coin-specific availability. It is to match the exact asset, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when network status becomes decisive

Consider a reader whose main constraint is chain-specific deposit and withdrawal. It is to match both endpoints, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when authenticated view becomes decisive

Consider a reader whose main constraint is account-specific selectable route. It is to verify immediately before action, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when address fields becomes decisive

Consider a reader whose main constraint is network, memo and destination. It is to compare character by character, retain the evidence, and define a stop condition before funds or permissions are committed.

Sources and editorial method

• Network status — Binance
• OKX status — OKX
• Coinbase status — Coinbase
• Kraken status — Kraken