Binance's official notice says support for deposits and withdrawals of AVA, GNS and TOWNS through specified networks ends at 08:00 UTC on September 14. CryptoSigy treats the cutoff as an exchange-route and custody-control event, not a price signal.
The scope is deliberately narrow: Binance said deposits and withdrawals for AVA, GNS and TOWNS would stop on specified networks at 08:00 UTC on September 14, while other supported networks remain available. Every time and status below comes from the linked sources available at publication. Readers should reopen those sources before acting because a later amendment, scratch or venue-status change can supersede this snapshot.
What Happened
The notice names AVA through BNB Smart Chain and Solana, GNS through Polygon, and TOWNS through BNB Smart Chain and Base. Binance warns that deposits sent through those routes after 08:00 UTC will not be credited and may lead to asset loss.
The same notice says users can still deposit or withdraw the named tokens through other networks supported by Binance. Asset, network, address format and the venue's current route therefore need to be checked together; a token being visible in an account does not keep every network open.
The event key for this update is binance-2026-09-14-network-deposit-withdrawal-cutoff-cryptosigy. Keeping that identifier separate from the headline prevents a revised display title from being mistaken for a new event and makes follow-up notices easier to reconcile.
Why It Matters
Network selection is an execution field, not a cosmetic label. A wallet can broadcast a valid transaction while the receiving venue no longer credits that network, leaving the user with a delayed or difficult recovery path.
Automated treasury, rebalancing and withdrawal workflows may retain the old route after the cutoff. Digital assets carry loss and operational risk, so the correct control is to reconcile the live venue route and use a small test transfer where appropriate rather than infer support from an old address.
The useful decision is therefore conditional. Confirm the stated input, compare the available route and decline the action if a required field is missing. A current timestamp does not turn uncertain information into an edge, and it does not remove market, execution or operational risk.
What To Watch Next
Reopen the original Binance notice and the live deposit or withdrawal screen for the exact asset and network. Confirm the network is explicitly supported after the 08:00 UTC cutoff, then update address books, bot configuration and internal runbooks.
If a transfer was sent through a stopped route, preserve the transaction hash, asset, network and timestamp and use Binance's documented support process. Do not send a second transfer to cover an unresolved first one until the route and account state reconcile.
Use the official source as the change log. If a new notice alters the schedule, participants, supported route or settlement process, rebuild the decision from that notice rather than editing the old conclusion in place.