출처 검증 리서치: Binance

Verified source facts

1. Binance set the selected-network support cutoff at September 14, 2026 at 08:00 UTC. 2. The affected routes are AVA via BNB Smart Chain and Solana, GNS via Polygon, and TOWNS via BNB Smart Chain and Base. 3. Binance warns that deposits sent through the discontinued routes after the cutoff will not be credited and may lead to asset loss. 4. The notice says users may still deposit or withdraw the listed tokens through other networks that Binance supports.

Comparison at a glance

1. Official-product check: Cutoff

A venue announcement becomes useful only after its rule is translated into a testable account decision. Here, cutoff concerns September 14 at 08:00 UTC. Retain the dated first-party wording, identify the eligible entity and product screen, and then preserve the official UTC time. A launch headline cannot prove access, suitability, liquidity, or the result for a particular account.

Separate the product's stated mechanics from promotional framing. Identify the funding source, matching or pricing rule, settlement trigger, fee formula, loss boundary, and suspension policy. The documentation can describe those controls, but it cannot resolve later notice edits. That unknown must remain visible rather than being converted into a prediction.

Finally, make cutoff reversible where possible: preserve the official UTC time. Retain non-secret evidence and reconcile the result with the rule for September 14 at 08:00 UTC. This section evaluates operational mechanics; because later notice edits remains unresolved, it does not predict the underlying market or recommend taking the exposure.

2. Official-product check: Asset

Here, asset concerns AVA, GNS or TOWNS. Retain the dated first-party wording, identify the eligible entity and product screen, and then verify the exact token identity.

The documentation can describe those controls, but it cannot resolve ticker collision.

Finally, make asset reversible where possible: verify the exact token identity. Retain non-secret evidence and reconcile the result with the rule for AVA, GNS or TOWNS. This section evaluates operational mechanics; because ticker collision remains unresolved, it does not predict the underlying market or recommend taking the exposure.

3. Official-product check: Sending network

Here, sending network concerns chain selected at origin. Retain the dated first-party wording, identify the eligible entity and product screen, and then match the supported route.

The documentation can describe those controls, but it cannot resolve wallet defaults.

Finally, make sending network reversible where possible: match the supported route. Retain non-secret evidence and reconcile the result with the rule for chain selected at origin. This section evaluates operational mechanics; because wallet defaults remains unresolved, it does not predict the underlying market or recommend taking the exposure.

4. Official-product check: Receiving network

Here, receiving network concerns chain shown by Binance deposit. Retain the dated first-party wording, identify the eligible entity and product screen, and then copy from the live deposit screen.

The documentation can describe those controls, but it cannot resolve maintenance.

Finally, make receiving network reversible where possible: copy from the live deposit screen. Retain non-secret evidence and reconcile the result with the rule for chain shown by Binance deposit. This section evaluates operational mechanics; because maintenance remains unresolved, it does not predict the underlying market or recommend taking the exposure.

5. Official-product check: Address

Here, address concerns destination generated for the pair. Retain the dated first-party wording, identify the eligible entity and product screen, and then verify the full address.

The documentation can describe those controls, but it cannot resolve address reuse.

Finally, make address reversible where possible: verify the full address. Retain non-secret evidence and reconcile the result with the rule for destination generated for the pair. This section evaluates operational mechanics; because address reuse remains unresolved, it does not predict the underlying market or recommend taking the exposure.

6. Official-product check: Memo or tag

Here, memo or tag concerns extra destination identifier. Retain the dated first-party wording, identify the eligible entity and product screen, and then include when required.

The documentation can describe those controls, but it cannot resolve recovery availability.

Finally, make memo or tag reversible where possible: include when required. Retain non-secret evidence and reconcile the result with the rule for extra destination identifier. This section evaluates operational mechanics; because recovery availability remains unresolved, it does not predict the underlying market or recommend taking the exposure.

7. Official-product check: Credit status

Here, credit status concerns whether post-cutoff deposits are credited. Retain the dated first-party wording, identify the eligible entity and product screen, and then do not test a discontinued route.

The documentation can describe those controls, but it cannot resolve support discretion.

Finally, make credit status reversible where possible: do not test a discontinued route. Retain non-secret evidence and reconcile the result with the rule for whether post-cutoff deposits are credited. This section evaluates operational mechanics; because support discretion remains unresolved, it does not predict the underlying market or recommend taking the exposure.

8. Official-product check: Alternative route

Here, alternative route concerns other currently supported network. Retain the dated first-party wording, identify the eligible entity and product screen, and then verify both endpoints.

The documentation can describe those controls, but it cannot resolve liquidity and bridging.

Finally, make alternative route reversible where possible: verify both endpoints. Retain non-secret evidence and reconcile the result with the rule for other currently supported network. This section evaluates operational mechanics; because liquidity and bridging remains unresolved, it does not predict the underlying market or recommend taking the exposure.

9. Official-product check: Small test

Here, small test concerns minimum reversible transfer. Retain the dated first-party wording, identify the eligible entity and product screen, and then confirm receipt before scaling.

The documentation can describe those controls, but it cannot resolve minimum withdrawal.

Finally, make small test reversible where possible: confirm receipt before scaling. Retain non-secret evidence and reconcile the result with the rule for minimum reversible transfer. This section evaluates operational mechanics; because minimum withdrawal remains unresolved, it does not predict the underlying market or recommend taking the exposure.

10. Official-product check: Evidence

Here, evidence concerns transaction hash and account history. Retain the dated first-party wording, identify the eligible entity and product screen, and then retain non-secret records.

The documentation can describe those controls, but it cannot resolve future support outcome.

Finally, make evidence reversible where possible: retain non-secret records. Retain non-secret evidence and reconcile the result with the rule for transaction hash and account history. This section evaluates operational mechanics; because future support outcome remains unresolved, it does not predict the underlying market or recommend taking the exposure.

Decision scenarios

Scenario 1: when cutoff becomes decisive

Consider a reader whose main constraint is September 14 at 08:00 UTC. The correct response is not to infer a universal platform or product winner. It is to preserve the official UTC time, 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 asset becomes decisive

Consider a reader whose main constraint is AVA, GNS or TOWNS. It is to verify the exact token identity, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when sending network becomes decisive

Consider a reader whose main constraint is chain selected at origin. It is to match the supported route, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when receiving network becomes decisive

Consider a reader whose main constraint is chain shown by Binance deposit. It is to copy from the live deposit screen, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when address becomes decisive

Consider a reader whose main constraint is destination generated for the pair. It is to verify the full address, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when memo or tag becomes decisive

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