Binance's official announcement lists ACX, HFT, PIVX, PYR, VANRY and VIC for delisting on August 17, 2026. CryptoSigy treats this as a position and custody timeline event, not a price pick.
The scope is deliberately narrow: Binance announced it will delist ACX, HFT, PIVX, PYR, VANRY and VIC on August 17, 2026, with trading pairs removed on the scheduled date. 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 official notice names six tokens removed from the platform on the scheduled delisting date. Trading pairs and deposit routes for the affected assets are closed as part of the operation.
The withdrawal window and any final trading cut-off are published in the official notice and the affected-token pages, so the exact deadlines must be read from Binance, not assumed from the headline date.
The event key for this update is binance-2026-08-17-delist-acx-hft-pivx-pyr-vanry-vic-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
A delisting changes every route for an affected asset: trading, deposits and withdrawals can stop on different timestamps, and open positions must be closed or transferred inside the published window.
For CryptoSigy readers the useful frame is operational: reconcile balances, close or move positions before the cut-off, and use a small test withdrawal once the supported route is confirmed.
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 official delisting notice near the scheduled date and watch for a revised timeline, an extended withdrawal window or a network-specific change.
Do not hold an affected asset past the final withdrawal date expecting a later route; treat the published window as the controlling deadline.
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.
Continue this cluster
- Binance Updates Tick Size for Multiple Perpetual Contracts (August 18)
- Binance Launches Multiple TradFi Perpetual Contracts (August 17-18)
