NES Holders Face Split Recovery Paths After $286M Exploit
Binance Alpha and Kraken restored NES trading on Sept. 10 using distinct recovery methods that leave self-custody holders without a verified migration route.
Nesa’s NES token resumed trading on Binance Alpha and regained Ethereum funding on Kraken on Sept. 10. This follows a token-contract security incident on Aug. 24 that impacted $286M in value. The exchange-specific fixes do not constitute a universal network relaunch.
Binance Alpha uses two snapshots to separate eligible 1:1 swaps from refunds. Kraken migrates affected funds to a new Ethereum contract. Neither venue provides a standardized process for tokens held in private wallets.
Binance defines eligibility via two snapshots
Binance Alpha requires users to have held NES before 14:51 UTC on Aug. 24. Users must also hold an eligible portion at 04:00 UTC on Sept. 5. Only these balances receive the 1:1 swap.
NES acquired after the Aug. 24 cutoff is excluded from the swap. This portion is subject to separate refund treatment. Binance will email refund details to eligible net purchasers within seven business days.
The announcement does not disclose the complete refund formula. It does not guarantee that every affected holder will be made whole. Trading reopened at 08:00 UTC on Sept. 10.
Kraken restricts support to Ethereum only
Kraken migrated NES covered by its funding incident to a new Ethereum contract. Ethereum deposits and withdrawals returned at 14:00 UTC on Sept. 10. The exchange marked the funding incident resolved 12 minutes later.
Funding on the BNB Chain remains disabled. Only Ethereum-based NES is supported going forward. Customers must select the Ethereum network when moving funds to or from Kraken.
Self-custody holders lack a migration route
Exchange-managed actions do not apply to NES held in private wallets. Binance’s snapshot windows and Kraken’s automatic migration do not cover self-custodied tokens. Nesa’s public documentation did not provide incident-specific migration steps as of press time.
Holders must verify any contract address through official channels. They should not assume that exchange rules apply to their own wallets. No universal migration process is currently available for non-exchange holders.
