Nghiên cứu đã kiểm chứng nguồn: Exchange Token Contract SWAP

Verified source facts

1. A contract swap can change token identifiers while leaving other exchange services available. 2. Binance's notice identifies a 1:1 swap and maps the new token to USDT0 and the old token to OPUSDTE. 3. The notice gives a suspension time but says reopening will be announced separately. 4. Continued trading does not prove that deposits or withdrawals are available.

Comparison at a glance

1. Control test: Chain

A trading-control disclosure is meaningful only when converted into a testable rule. For chain, inspect affected network. Use a sandbox, non-production context, or the smallest reversible test available, then name exactly. 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, multi-chain confusion is therefore an explicit audit gap.

The chain row should end with a concrete monitoring rule tied to affected network. Make the operator name exactly, 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; multi-chain confusion remains a separate production risk until observed.

2. Control test: Old contract

For old contract, inspect retired identifier. Use a sandbox, non-production context, or the smallest reversible test available, then retain evidence.

In this dimension, accidental send is therefore an explicit audit gap.

The old contract row should end with a concrete monitoring rule tied to retired identifier. 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; accidental send remains a separate production risk until observed.

3. Control test: New contract

For new contract, inspect replacement identifier. Use a sandbox, non-production context, or the smallest reversible test available, then verify official source.

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

The new contract row should end with a concrete monitoring rule tied to replacement identifier. Make the operator verify official source, 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; spoof remains a separate production risk until observed.

4. Control test: Ticker map

For ticker map, inspect old and new labels. Use a sandbox, non-production context, or the smallest reversible test available, then document mapping.

In this dimension, wallet display is therefore an explicit audit gap.

The ticker map row should end with a concrete monitoring rule tied to old and new labels. Make the operator document mapping, 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 display remains a separate production risk until observed.

5. Control test: Ratio

For ratio, inspect swap conversion. Use a sandbox, non-production context, or the smallest reversible test available, then confirm entitlement.

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

The ratio row should end with a concrete monitoring rule tied to swap conversion. Make the operator confirm entitlement, 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; fee assumption remains a separate production risk until observed.

6. Control test: Cutoff

For cutoff, inspect suspension UTC. Use a sandbox, non-production context, or the smallest reversible test available, then allow credit time.

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

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

7. Control test: Trading impact

For trading impact, inspect services continuing. Use a sandbox, non-production context, or the smallest reversible test available, then separate states.

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

The trading impact row should end with a concrete monitoring rule tied to services continuing. Make the operator separate states, 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 inference remains a separate production risk until observed.

8. Control test: Reopening

For reopening, inspect event or announcement. Use a sandbox, non-production context, or the smallest reversible test available, then monitor official page.

In this dimension, indefinite wait is therefore an explicit audit gap.

The reopening row should end with a concrete monitoring rule tied to event or announcement. Make the operator monitor official 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; indefinite wait remains a separate production risk until observed.

9. Control test: Wallet support

For wallet support, inspect external provider readiness. Use a sandbox, non-production context, or the smallest reversible test available, then confirm compatibility.

In this dimension, stranded asset is therefore an explicit audit gap.

The wallet support row should end with a concrete monitoring rule tied to external provider readiness. Make the operator confirm compatibility, 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; stranded asset remains a separate production risk until observed.

10. Control test: Post-swap test

For post-swap test, inspect small deposit and withdrawal. Use a sandbox, non-production context, or the smallest reversible test available, then wait for final credit.

In this dimension, minimum fee is therefore an explicit audit gap.

The post-swap test row should end with a concrete monitoring rule tied to small deposit and withdrawal. Make the operator wait for final credit, 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; minimum fee remains a separate production risk until observed.

Decision scenarios

Scenario 1: when chain becomes decisive

Consider a reader whose main constraint is affected network. The correct response is not to infer a universal platform or product winner. It is to name exactly, 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 old contract becomes decisive

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

Scenario 3: when new contract becomes decisive

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

Scenario 4: when ticker map becomes decisive

Consider a reader whose main constraint is old and new labels. It is to document mapping, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when ratio becomes decisive

Consider a reader whose main constraint is swap conversion. It is to confirm entitlement, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when cutoff becomes decisive

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

Sources and editorial method

• USDT contract swap on Optimism — Binance Support
• USDT contract swap notice — Binance UK
• Maintenance updates — Binance Support