Nesa’s NES token has made a comeback on Binance Alpha and has also regained Ethereum funding on Kraken after facing venue-specific interruptions due to a token-contract security incident on August 24. This restoration does not signify a network-wide relaunch or a single recovery plan. Binance Alpha is utilizing two snapshots to distinguish eligible 1:1 swaps from refunds on its platform. On the other hand, Kraken mentioned that NES covered by its funding incident would migrate 1:1 to a new Ethereum contract, while BNB-chain funding would remain disabled.
It is important to note that these distinctions extend beyond the two exchanges mentioned above. Neither notice provides a universal migration process for NES held in a private wallet.
For Binance and Kraken users, here is what you need to do:
On Binance Alpha, users who held NES before August 24 at 14:51 UTC must have also held an eligible portion when trading was suspended on September 5 at 04:00 UTC to receive the 1:1 swap for that portion. Additional NES acquired after the August 24 cutoff is excluded from the 1:1 swap and is subject to separate refund treatment. Users with eligible net purchases during the specified window will receive an email with refund details within seven business days. Trading on Binance Alpha is set to reopen at 08:00 UTC on September 10.
At Kraken, NES will be migrated 1:1 to a new Ethereum contract. Ethereum deposits and withdrawals are scheduled to return at 14:00 UTC on September 10. NES funding on BNB Chain will remain disabled, and only Ethereum-based NES will 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.
It is crucial to remember that the actions taken by the exchanges do not dictate what happens to NES outside of Binance Alpha or Kraken. Self-custodied holders should not assume that the snapshot windows on Binance or Kraken’s automatic migration apply to tokens in their own wallets.
As of now, Nesa’s official website and general wallet documentation do not provide incident-specific self-custody migration steps. Holders are advised to verify any contract address and migration process through Nesa’s official channels before approving a contract interaction or moving old-contract tokens.
In conclusion, the return of Nesa’s NES token on Binance Alpha and Kraken marks a significant milestone after the security incident. Users on these platforms should follow the instructions provided by the exchanges for a smooth transition.