CryptoSlate
Nesa's NES token returned to trading on Binance Alpha and regained Ethereum funding on Kraken on Sept. 10, more than two weeks after an Aug. 24 token-contract security incident exposed roughly $286M worth of tokens. The two venues are running parallel but incompatible recovery processes, and self-custody holders sit outside both of them.
Why it matters
Binance Alpha is using two separate snapshots to decide who gets the 1:1 swap into a new contract and who falls into a partial refund bucket. To qualify for the swap, a user must have held NES before Aug. 24 at 14:51 UTC and still held an eligible balance when trading was suspended on Sept. 5 at 04:00 UTC. Any additional NES purchased after the cutoff is excluded from the swap, and Binance has not published the full refund formula or committed to making every affected holder whole.
Kraken took a simpler path: all NES funding on Ethereum migrates 1:1 to a new contract, BNB-chain NES funding is being disabled, and Ethereum deposits and withdrawals reopened at 14:00 UTC on Sept. 10. Neither notice describes a process for NES sitting in a private wallet.
Market impact
The patchwork sets a precedent for how token migrations get staged when an exploit contaminates the contract: venue A runs a snapshot filter, venue B runs an automatic migration, and self-custody users wait for the issuer to publish guidance that, as of writing, has not appeared. Holders with old-contract NES in their own wallets should not assume any of the exchange-side steps apply to them, and any contract interaction should be verified against Nesa's official channels before approval.
Frequently asked questions
-
What happened to NES on Aug. 24?
A token-contract security incident exposed roughly $286M worth of NES tokens. The event triggered a trading suspension on Binance Alpha and a funding incident on Kraken that lasted more than two weeks.
-
How does Binance Alpha's NES recovery work?
Users who held NES before Aug. 24 at 14:51 UTC and still held an eligible balance at the Sept. 5 trading suspension qualify for a 1:1 swap into a new contract. Tokens bought after the cutoff fall into a separate refund bucket with a formula Binance has not fully published.
-
How does Kraken's NES migration differ from Binance's?
Kraken is migrating all Ethereum-based NES 1:1 to a new contract automatically. BNB-chain NES funding will remain disabled, and only the new Ethereum contract will be supported going forward.
-
What should self-custody NES holders do?
Wait for Nesa to publish incident-specific migration steps before approving any contract interaction. The Binance and Kraken recovery processes do not automatically apply to tokens held in private wallets.
-
When did NES trading resume?
Binance Alpha reopened NES trading at 08:00 UTC on Sept. 10. Kraken restored Ethereum deposits and withdrawals at 14:00 UTC the same day and marked the funding incident resolved minutes later.
TheBlock
WuBlockchain
CoinDesk