Nesa’s $NES token returned to trading on Binance Alpha and regained Ethereum funding on Kraken on Sept. 10 after venue-specific interruptions tied to an Aug. 24 token-contract security incident.
The restorations are not a network-wide relaunch or a single recovery plan. Binance Alpha is using two snapshots to separate eligible 1:1 swaps from refunds on its platform. Kraken said $NES covered by its funding incident would migrate 1:1 to a new Ethereum contract, while $BNB-chain funding would remain disabled.
That distinction matters beyond the two exchanges: neither notice gives a universal migration process for $NES held in a private wallet.
What Binance and Kraken users need to do
On Binance Alpha, Binance said users who held $NES before Aug. 24 at 14:51 UTC must also have held an eligible portion when trading was suspended on Sept. 5 at 04:00 UTC to receive the 1:1 swap for that portion.
Additional $NES acquired after the Aug. 24 cutoff is excluded from the 1:1 swap and is subject to separate refund treatment. Binance said 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.
Binance’s announcement scheduled trading to reopen at 08:00 UTC on Sept. 10. Users should check which snapshot category applies to their balance and monitor the email address linked to their account.
At Kraken, the exchange’s incident page said $NES would be migrated 1:1 to a new Ethereum contract. It scheduled Ethereum deposits and withdrawals to return at 14:00 UTC on Sept. 10 and marked the funding incident resolved 12 minutes later.
Kraken said $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.
\n
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. Until Nesa publishes or directly verifies a route, holders should verify any contract address and migration process through its official channels before approving a contract interaction or moving old-contract tokens.
