Дослідження з перевіркою джерел: Exchange Network Upgrade Block

Verified source facts

1. Dual trigger,The notice provides both approximate time and block height.,bybit-zig 2. Service split,Deposits and withdrawals pause while trading is stated to continue.,bybit-zig 3. Resumption signal,The notice directs users to set an account-page alert.,bybit-zig 4. Internal movement,Wallet maintenance can create large venue-controlled onchain transfers.,bybit-wallet

Comparison at a glance

1. Control test: Version

A trading-control disclosure is meaningful only when converted into a testable rule. For version, inspect protocol release. Use a sandbox, non-production context, or the smallest reversible test available, then record exact tag. 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, version ambiguity is therefore an explicit audit gap.

The version row should end with a concrete monitoring rule tied to protocol release. Make the operator record exact tag, 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; version ambiguity remains a separate production risk until observed.

2. Control test: Time

For time, inspect approximate UTC. Use a sandbox, non-production context, or the smallest reversible test available, then normalize.

In this dimension, timezone error is therefore an explicit audit gap.

The time row should end with a concrete monitoring rule tied to approximate UTC. Make the operator normalize, 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; timezone error remains a separate production risk until observed.

3. Control test: Height

For height, inspect target block. Use a sandbox, non-production context, or the smallest reversible test available, then monitor.

In this dimension, chain-speed drift is therefore an explicit audit gap.

The height row should end with a concrete monitoring rule tied to target block. Make the operator monitor, 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; chain-speed drift remains a separate production risk until observed.

4. Control test: Deposit cutoff

For deposit cutoff, inspect venue time. Use a sandbox, non-production context, or the smallest reversible test available, then stop early.

In this dimension, late credit is therefore an explicit audit gap.

The deposit cutoff row should end with a concrete monitoring rule tied to venue time. Make the operator stop early, 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; late credit remains a separate production risk until observed.

5. Control test: Withdrawal cutoff

For withdrawal cutoff, inspect venue time. Use a sandbox, non-production context, or the smallest reversible test available, then avoid queue.

In this dimension, pending request is therefore an explicit audit gap.

The withdrawal cutoff row should end with a concrete monitoring rule tied to venue time. Make the operator avoid queue, 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; pending request remains a separate production risk until observed.

6. Control test: Trading state

For trading state, inspect separate product. Use a sandbox, non-production context, or the smallest reversible test available, then verify.

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

The trading state row should end with a concrete monitoring rule tied to separate product. Make the operator 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; false outage remains a separate production risk until observed.

7. Control test: Chain completion

For chain completion, inspect validator evidence. Use a sandbox, non-production context, or the smallest reversible test available, then wait confirmations.

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

The chain completion row should end with a concrete monitoring rule tied to validator evidence. Make the operator wait confirmations, 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; premature recovery remains a separate production risk until observed.

8. Control test: Wallet test

For wallet test, inspect venue evidence. Use a sandbox, non-production context, or the smallest reversible test available, then check account page.

In this dimension, chain-only assumption is therefore an explicit audit gap.

The wallet test row should end with a concrete monitoring rule tied to venue evidence. Make the operator check account page, 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; chain-only assumption remains a separate production risk until observed.

9. Control test: Alert

For alert, inspect resumption channel. Use a sandbox, non-production context, or the smallest reversible test available, then subscribe.

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

The alert row should end with a concrete monitoring rule tied to resumption channel. Make the operator subscribe, 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 change remains a separate production risk until observed.

10. Control test: Post-test

For post-test, inspect small transfer. Use a sandbox, non-production context, or the smallest reversible test available, then reconcile.

In this dimension, large-loss risk is therefore an explicit audit gap.

The post-test row should end with a concrete monitoring rule tied to small transfer. Make the operator reconcile, 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; large-loss risk remains a separate production risk until observed.

Decision scenarios

Scenario 1: when version becomes decisive

Consider a reader whose main constraint is protocol release. The correct response is not to infer a universal platform or product winner. It is to record exact tag, 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 time becomes decisive

Consider a reader whose main constraint is approximate UTC. It is to normalize, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when height becomes decisive

Consider a reader whose main constraint is target block. It is to monitor, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when deposit cutoff becomes decisive

Consider a reader whose main constraint is venue time. It is to stop early, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when withdrawal cutoff becomes decisive

It is to avoid queue, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when trading state becomes decisive

Consider a reader whose main constraint is separate product. It is to verify, retain the evidence, and define a stop condition before funds or permissions are committed.

Sources and editorial method

• Zigchain upgrade notice — Bybit
• Maintenance registry — Bybit
• Wallet maintenance example — Bybit