NES token resumed trading on Binance Alpha and regained Ethereum deposit and withdrawal access on Kraken on September 10, following a security incident that struck the token contract on August 24.
The two exchanges implemented separate recovery procedures tied to snapshot-based eligibility criteria, creating unequal outcomes for holders across platforms and self-custody wallets.
Binance Alpha Recovery Structure
Binance Alpha uses two snapshots to determine recovery treatment. Users who held NES before August 24 at 14:51 UTC and maintained an eligible portion when trading suspended on September 5 at 04:00 UTC receive a 1:1 swap for that portion. NES acquired after the August 24 cutoff is excluded from the 1:1 swap and subject to separate refund treatment.
Trading on Binance Alpha reopened at 08:00 UTC on September 10. Binance did not disclose its complete refund formula or guarantee that all affected holders will be made whole.
Kraken’s Ethereum-Only Migration
Kraken migrates NES 1:1 to a new Ethereum contract. BNB Chain funding remains disabled, and only Ethereum-based NES is supported going forward. Ethereum deposits and withdrawals returned at 14:00 UTC on September 10, with Kraken marking the funding incident resolved at 14:12 UTC the same day.
Self-Custody Holders Without Universal Route
Self-custody holders lack a verified, universal migration route from Nesa, the NES token project. Neither Binance Alpha nor Kraken has published standardized recovery procedures accessible to users holding tokens in non-custodial wallets, leaving that segment of holders without a clear path to recovery.
The divergence between exchange-specific recovery mechanisms and the absence of a self-custody migration route creates potential disparity in outcomes across holders depending on where they stored their NES when the August 24 incident occurred.
