NES Token Recovery Splits Holders Across Exchanges After $286M Exploit
In brief
- NES resumed trading on Binance Alpha and Kraken on September 10 following August 24 security incident
- Binance Alpha uses two snapshots (Aug. 24 and Sept. 5) to determine 1:1 swaps versus refunds
- Kraken supports only Ethereum-based NES; BNB Chain funding remains disabled
- Self-custodied NES holders lack official migration guidance and fall outside exchange recovery programs
Two Snapshots, Two Classes of Holders
Binance Alpha is using two snapshots to separate eligible 1:1 swaps from refunds on its platform. The first snapshot was taken at August 24 at 14:51 UTC (the time of the incident), and the second at September 5 at 04:00 UTC (when trading was suspended).
On Binance Alpha, users who held NES before August 24 at 14:51 UTC must also have held an eligible portion when trading was suspended on September 5 at 04:00 UTC to receive the 1:1 swap. NES acquired after the August 24 cutoff is excluded from the 1:1 swap and is subject to separate refund treatment. The distinction matters. Holders who bought during the 12-day window between the two snapshots face a different recovery path than those who held continuously before the incident.
Binance said users with eligible net purchases during the specified window would receive an email with refund details within seven business days. Yet the announcement does not disclose the complete refund formula or support a claim that every affected holder will be made whole.
Kraken's Ethereum-Only Path
Kraken said NES would be migrated 1:1 to a new Ethereum contract, with Ethereum deposits and withdrawals returning at 14:00 UTC on September 10. The exchange took a narrower stance than Binance. Kraken said NES funding on BNB Chain would remain disabled and only Ethereum-based NES would be supported going forward. Users who held NES on BNB Chain at Kraken lost access to that version of the token entirely.
Self-Custody Holders Left in the Dark
The exchange-managed actions do not determine what happens to NES outside Binance Alpha or Kraken. Self-custodied holders should not assume that Binance's snapshot windows or Kraken's automatic migration apply to tokens in their own wallets. As of press time, Nesa's public official site and general wallet documentation did not provide incident-specific self-custody migration steps. Holders who moved NES to personal wallets before or after the incident must navigate recovery on their own, without official guidance on how to migrate to the new contract or claim refunds.
Frequently asked questions
Why do Binance Alpha and Kraken have different recovery rules for NES?
Each exchange manages its own platform independently. Binance Alpha uses dual snapshots to distinguish between pre-incident holders and those who bought during the recovery window. Kraken chose to migrate NES to Ethereum only and disabled BNB Chain support. Neither exchange is obligated to follow the other's recovery model.
What happens to NES I held in my own wallet?
Self-custodied holders fall outside both Binance Alpha's snapshot system and Kraken's automatic migration. As of press time, Nesa had not published official self-custody migration steps. You cannot rely on the exchange recovery programs and must monitor official channels for guidance on migrating to the new contract.
