On a single day, two exchanges switched the same token back on using two entirely different rulebooks. And neither rulebook says a word about the tokens held in your own wallet.
Nesa’s NES token returned to trading on Binance Alpha and had Ethereum funding restored on Kraken on Sept. 10, following venue-by-venue outages stemming from an Aug. 24 security incident involving the token contract.
That’s the upside. Everything after it hinges on where your NES was parked, and at what moment.
Two snapshots, and the second one is the one that bites
According to Binance, anyone holding NES before Aug. 24 at 14:51 UTC must also have been holding an eligible portion at the moment trading was halted on Sept. 5 at 04:00 UTC in order to qualify for the 1:1 swap on that portion.
That deserves a second pass. Clearing the first cutoff on its own counts for nothing. The balance had to survive the second one too.
Anyone who sold during the stretch between Aug. 24 and Sept. 5 finds the sold portion sitting outside the 1:1 swap. It’s a two-week gap in which an entirely reasonable move — shaving down exposure after a security incident — quietly rewrites what you’re entitled to.
NES acquired after the Aug. 24 cutoff doesn’t qualify for the 1:1 swap at all. Those tokens are handled under a separate refund process.
The refund math isn’t public
Users with eligible net purchases inside the specified window will be emailed refund details within seven business days, Binance said.
What the notice stops short of doing is spelling out the full refund formula. Nor does anything in it back the assumption that every affected holder ends up whole.
That omission carries weight. “Refund details to follow” is a materially different pledge from “you’ll get your money back,” and the space between those two readings is where most of the anger over this episode is likely to settle.
Trading resumed at 08:00 UTC on Sept. 10. For anyone caught up in it, the sensible step is to determine which snapshot bucket your balance lands in, then keep an eye on the inbox linked to your account.
Kraken picked a chain and dropped the other one
Per Kraken’s incident page, NES would be migrated 1:1 onto a new Ethereum contract. Ethereum deposits and withdrawals were slated to come back at 14:00 UTC on Sept. 10, and the exchange flagged the funding incident as resolved 12 minutes afterward.
There were no snapshots, no eligibility windows and no refund formula. A migration, and that’s it.
NES funding on BNB Chain, however, remains switched off. Kraken said only Ethereum-based NES will be supported from here on.
Anyone shifting NES into or out of Kraken should choose Ethereum and verify the new contract details against Kraken’s official notice before hitting send. Pushing a BNB Chain transfer to a venue that has retired BNB Chain funding is precisely the sort of error that comes without an undo button.
Self-custody holders get nothing from either notice
This is the detail that tends to vanish amid the relief of watching trading come back online. Both measures are exchange-managed, and exchange-managed measures end at the exchange door.
Binance’s snapshot windows never touch your wallet. Kraken’s automatic migration doesn’t either. For anyone who held NES in private custody through Aug. 24, neither announcement explains what becomes of those tokens.
At press time, neither Nesa’s public official site nor its general wallet documentation offered incident-specific migration instructions for self-custody holders.
For the moment, then, waiting beats improvising. Until Nesa publishes a path or confirms one directly, avoid approving any contract interaction or moving old-contract tokens based on an address sourced from anywhere but Nesa’s official channels. Migrations that follow an incident are fertile ground for counterfeit migration contracts, and an approval signed by your own key is not something any exchange can undo.
Fallout from the $286M exploit has yielded two recovery frameworks that contradict one another on nearly every point, plus a third cohort of holders that neither framework reaches. For those in that third cohort, today’s only worthwhile task is confirming the contract address with Nesa directly — and sitting tight until one exists.