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

Verified source facts

1. Binance schedules the wallet-system upgrade for 06:00 UTC on September 22, 2026. 2. The notice says deposits and withdrawals across the platform will be suspended for about one hour. 3. Binance states that trading will not be affected by the wallet-system upgrade. 4. The venue says deposits and withdrawals will reopen after the system is stable without a further announcement.

Comparison at a glance

1. Compare scope on the same job

A platform comparison becomes useful only when both venues are measured against one job. For scope, that job concerns platform-wide or one network. Marketing pages frequently describe broad capability while the actual decision lives in a specific pair, contract, network, entity, or account tier. Build two evidence rows from the same timestamp, then read the notice boundary. Until that check is complete, neither venue earns the point.

The comparison should distinguish a published ceiling from an executable outcome. A fee table does not reveal slippage; a product menu does not prove regional eligibility; a security feature page does not prove the control is enabled on the reader's account. Record the route from public statement to authenticated evidence. The unresolved variable is wrong assumption, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For scope, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how platform-wide or one network changes the entry, exit, monitoring, or fallback decision, and make the operator read the notice boundary. The remaining uncertainty—wrong assumption—belongs in the dated scorecard. That produces a job-specific preference instead of a permanent winner.

2. Compare start time on the same job

For start time, that job concerns 06:00 UTC. Build two evidence rows from the same timestamp, then convert timezone.

The unresolved variable is missed cutoff, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For start time, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how 06:00 UTC changes the entry, exit, monitoring, or fallback decision, and make the operator convert timezone. The remaining uncertainty—missed cutoff—belongs in the dated scorecard.

3. Compare expected duration on the same job

For expected duration, that job concerns about one hour. Build two evidence rows from the same timestamp, then treat as estimate.

The unresolved variable is false certainty, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For expected duration, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how about one hour changes the entry, exit, monitoring, or fallback decision, and make the operator treat as estimate. The remaining uncertainty—false certainty—belongs in the dated scorecard.

4. Compare deposits on the same job

For deposits, that job concerns temporarily suspended. Build two evidence rows from the same timestamp, then finish early.

The unresolved variable is late credit, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For deposits, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how temporarily suspended changes the entry, exit, monitoring, or fallback decision, and make the operator finish early. The remaining uncertainty—late credit—belongs in the dated scorecard.

5. Compare withdrawals on the same job

For withdrawals, that job concerns temporarily suspended. Build two evidence rows from the same timestamp, then avoid urgent transfer.

The unresolved variable is stuck workflow, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For withdrawals, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how temporarily suspended changes the entry, exit, monitoring, or fallback decision, and make the operator avoid urgent transfer. The remaining uncertainty—stuck workflow—belongs in the dated scorecard.

6. Compare trading on the same job

For trading, that job concerns stated unaffected. Build two evidence rows from the same timestamp, then separate from wallet state.

The unresolved variable is false inference, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For trading, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how stated unaffected changes the entry, exit, monitoring, or fallback decision, and make the operator separate from wallet state. The remaining uncertainty—false inference—belongs in the dated scorecard.

7. Compare reopening on the same job

For reopening, that job concerns after stability check. Build two evidence rows from the same timestamp, then verify live status.

The unresolved variable is premature send, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For reopening, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how after stability check changes the entry, exit, monitoring, or fallback decision, and make the operator verify live status. The remaining uncertainty—premature send—belongs in the dated scorecard.

8. Compare network on the same job

For network, that job concerns asset-specific route. Build two evidence rows from the same timestamp, then match chain exactly.

The unresolved variable is wrong network, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For network, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how asset-specific route changes the entry, exit, monitoring, or fallback decision, and make the operator match chain exactly. The remaining uncertainty—wrong network—belongs in the dated scorecard.

9. Compare test transfer on the same job

For test transfer, that job concerns small amount after reopening. Build two evidence rows from the same timestamp, then wait for credit.

The unresolved variable is minimum fee, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For test transfer, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how small amount after reopening changes the entry, exit, monitoring, or fallback decision, and make the operator wait for credit. The remaining uncertainty—minimum fee—belongs in the dated scorecard.

10. Compare stop rule on the same job

For stop rule, that job concerns status or address mismatch. Build two evidence rows from the same timestamp, then do not send.

The unresolved variable is support evidence, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For stop rule, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how status or address mismatch changes the entry, exit, monitoring, or fallback decision, and make the operator do not send. The remaining uncertainty—support evidence—belongs in the dated scorecard.

Decision scenarios

Scenario 1: when scope becomes decisive

Consider a reader whose main constraint is platform-wide or one network. The correct response is not to infer a universal platform or product winner. It is to read the notice boundary, 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 start time becomes decisive

Consider a reader whose main constraint is 06:00 UTC. It is to convert timezone, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when expected duration becomes decisive

Consider a reader whose main constraint is about one hour. It is to treat as estimate, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when deposits becomes decisive

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

Scenario 5: when withdrawals becomes decisive

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

Scenario 6: when trading becomes decisive

Consider a reader whose main constraint is stated unaffected. It is to separate from wallet state, retain the evidence, and define a stop condition before funds or permissions are committed.

Sources and editorial method

• Wallet system upgrade on September 22, 2026 — Binance Support
• Maintenance updates — Binance Support
• Why deposits or withdrawals may be suspended — OKX