NES Token Resumes Trading on Binance Alpha and Kraken After Security Incident
Nesa’s NES token returned to trading on Binance Alpha and regained Ethereum funding support on Kraken on September 10, following exchange-specific interruptions tied to an August 24 token-contract security incident. The restorations are not a network-wide relaunch or a single recovery plan, and they do not establish a universal migration process for NES held in private wallets.
Binance Alpha: Two-Snapshot System for Swaps and Refunds
Binance Alpha is using two separate snapshots to determine eligibility for a 1:1 token swap versus refund treatment on its platform. According to the exchange’s announcement, 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 qualify for the 1:1 swap for that portion.
Any additional NES acquired after the August 24 cutoff is excluded from the 1:1 swap and will be subject to separate refund treatment. Binance stated that users with eligible net purchases during the specified window would receive an email with refund details within seven business days. The announcement does not disclose the complete refund formula or support a claim that every affected holder will be made whole.
Trading was scheduled to reopen at 08:00 UTC on September 10. Users should check which snapshot category applies to their balance and monitor the email address linked to their account.
Kraken: Ethereum-Only Migration, BNB Chain Funding Disabled
Kraken’s incident page confirmed that NES covered by its funding incident would migrate 1:1 to a new Ethereum contract. The exchange scheduled Ethereum deposits and withdrawals to resume at 14:00 UTC on September 10 and marked the funding incident resolved 12 minutes later.
Kraken explicitly stated that NES funding on BNB Chain would remain disabled and only Ethereum-based NES would be supported going forward. Customers moving NES to or from Kraken should select Ethereum and verify the new contract details in Kraken’s official notice before transferring funds.
No Universal Migration for Self-Custodied Holders
The exchange-managed actions do not determine what happens to NES held 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. Until Nesa publishes or directly verifies a route, holders should verify any contract address and migration process through official Nesa channels before approving a contract interaction or moving old-contract tokens.
