Token Migration Guide

Tokens Included in Migration Phase 4

All tokens that are included in the migration smart contract will be available for migration after the hardfork on mainnet now scheduled for 30th of October.

Tokens locked in the Ethereum Smart Contract

On 2nd September all tokens in the AEternity ERC20 Smart contract got frezeed. All users that ware unable to migrate the tokens before that date, will be able to do it in the next migration pahse. All token holders and their balances were extracted from the ethereum contract and put into the aeternity migration contract. In that way the users will be able to claim their tokens to the aeternity mainnet.

Tokens mistakenly sent to the Ethereum Smart Contract

In all migration phases there were some tokens that were mistakenly sent to the ethereum smart contract. This transactions were tracked, and accounts and balances were also put into the aeternity migration contract. These users will also have the ability to claim and migrate their tokens to the AEternity mainnet.

• An example of such transactions is:
  When migrating the user accidentaly put the ERC20 contract address (0x5ca9a71b1d01849c0a95490cc00559717fcf0d1d) into the to field of the transaction.

Tokens mistakenly sent to the Token Burner Smart Contract

In all migration phases there were some tokens that were mistakenly sent to the token burner smart contract. This transactions were tracked, and accounts and balances were also put into the aeternity migration contract. These users will also have the ability to claim and migrate their tokens to the AEternity mainnet.

• An example of such transactions is:
  When migrating the user accidentaly put the Token Burner contract address (0x8a3B7094e1D80C8366B4687cB85862311C931C52) into the to field of the transaction.

Tokens Not Included in Migration Phase 4

Tokens held by Еthereum smart contracts

All tokens that are held by Ethereum smart contract are not included in the migraion accounts list. An example of this are the ethereum multi-sig wallets.

Tokens accidentally send to the 0x0 Ethereum address

All tokens that were accidentally send to the 0x0 Ethereum address are also excluded from the migration accounts list.

Verification

• All files with token holders are available on this GitHub repository
  https://github.com/LimeChain/aepp-token-migration-holders

• All user can check their migration info, calling the following link
  https://token-migration.appspot.com/info/your-ethereum-address

• The backend can be run locally following the instructions from Github: https://github.com/LimeChain/aepp-token-migration-backend

• The client side can be run locally follwing the istructions from Github : https://github.com/LimeChain/aepp-token-migration