Blab Crypto
Binance Alpha and Kraken Resume Nesa Trading After August 24 Incident, Offering 1:1 Swaps and Refunds for Eligible Holders
After a security incident on August 24 that halted deposits, withdrawals and trading, the Nesa (NES) token returned to market on September 10, 2026, re‑establishing Ethereum‑based funding on Kraken and resuming trading on Binance Alpha.
Binance Alpha’s recovery hinges on two snapshots. The first records holders who owned NES before the August 24, 14:51 UTC breach and who still held an eligible portion when trading was suspended on September 5 at 04:00 UTC. Those users will receive a 1:1 swap of their eligible NES to a new Binance Smart Chain contract. The second snapshot captures all NES acquired after the August 24 cutoff; those tokens will not be swapped and will instead be handled through a refund process.
Refunds are not automatic. Binance will email users who made net purchases during the eligibility window within seven business days, detailing the refund amount and method. The email will also explain the calculation, though the full formula remains undisclosed. Trading on Binance Alpha is scheduled to resume at 08:00 UTC on September 10, and users are urged to check the email address linked to their account to determine their snapshot category.
Kraken’s approach is more straightforward. The exchange’s incident page confirms that NES will be migrated 1:1 to a new Ethereum contract. Deposits and withdrawals for the new contract will open at 14:00 UTC on September 10, and Kraken marked the incident as resolved 12 minutes later. Kraken also clarified that BNB‑Chain funding will remain disabled, meaning only Ethereum‑based NES will be supported moving forward. Customers moving NES to or from Kraken should select the Ethereum network and verify the new contract address before initiating a transfer.
The BNB‑Chain status remains unchanged. Both Binance Alpha and Kraken have disabled BNB‑Chain funding for NES, and no official migration path has been announced for tokens held on that chain. Users who hold NES on BNB‑Chain are therefore unable to trade or withdraw the token until a future update or separate migration is released.
Self‑custody holders face the greatest uncertainty. Neither Binance nor Kraken’s notices provide a universal migration route for NES held in private wallets. The Nesa public site and general wallet documentation do not yet contain incident‑specific migration instructions. Until Nesa publishes or verifies a route, holders should confirm any contract address and migration process through official Nesa channels before interacting with a new contract or moving old‑contract tokens.
In summary, the August 24 security incident prompted a coordinated recovery that restored trading on Binance Alpha and Kraken’s Ethereum‑based funding on September 10. Eligible holders on Binance Alpha will receive a 1:1 swap, while others will receive refunds via email. Kraken will migrate all NES to a new Ethereum contract, with BNB‑Chain funding remaining disabled. Self‑custody holders must seek official guidance from Nesa before taking any action. The situation remains fluid, and users should monitor official announcements for updates on contract addresses, refund calculations, and any future BNB‑Chain migration.
Binance Alpha’s recovery hinges on two snapshots. The first records holders who owned NES before the August 24, 14:51 UTC breach and who still held an eligible portion when trading was suspended on September 5 at 04:00 UTC. Those users will receive a 1:1 swap of their eligible NES to a new Binance Smart Chain contract. The second snapshot captures all NES acquired after the August 24 cutoff; those tokens will not be swapped and will instead be handled through a refund process.
Refunds are not automatic. Binance will email users who made net purchases during the eligibility window within seven business days, detailing the refund amount and method. The email will also explain the calculation, though the full formula remains undisclosed. Trading on Binance Alpha is scheduled to resume at 08:00 UTC on September 10, and users are urged to check the email address linked to their account to determine their snapshot category.
Kraken’s approach is more straightforward. The exchange’s incident page confirms that NES will be migrated 1:1 to a new Ethereum contract. Deposits and withdrawals for the new contract will open at 14:00 UTC on September 10, and Kraken marked the incident as resolved 12 minutes later. Kraken also clarified that BNB‑Chain funding will remain disabled, meaning only Ethereum‑based NES will be supported moving forward. Customers moving NES to or from Kraken should select the Ethereum network and verify the new contract address before initiating a transfer.
The BNB‑Chain status remains unchanged. Both Binance Alpha and Kraken have disabled BNB‑Chain funding for NES, and no official migration path has been announced for tokens held on that chain. Users who hold NES on BNB‑Chain are therefore unable to trade or withdraw the token until a future update or separate migration is released.
Self‑custody holders face the greatest uncertainty. Neither Binance nor Kraken’s notices provide a universal migration route for NES held in private wallets. The Nesa public site and general wallet documentation do not yet contain incident‑specific migration instructions. Until Nesa publishes or verifies a route, holders should confirm any contract address and migration process through official Nesa channels before interacting with a new contract or moving old‑contract tokens.
In summary, the August 24 security incident prompted a coordinated recovery that restored trading on Binance Alpha and Kraken’s Ethereum‑based funding on September 10. Eligible holders on Binance Alpha will receive a 1:1 swap, while others will receive refunds via email. Kraken will migrate all NES to a new Ethereum contract, with BNB‑Chain funding remaining disabled. Self‑custody holders must seek official guidance from Nesa before taking any action. The situation remains fluid, and users should monitor official announcements for updates on contract addresses, refund calculations, and any future BNB‑Chain migration.
