EOS mainnet is about to be launched, and EOS mapping worth more than 20 million US dollars is invalid

The ERC20 token EOS will be launched on the mainnet on June 2, but according to the PeckShield official website, as of today, PeckShield has found that 29.98% of EOS tokens have not been mapped. PeckShield also stated that among the EOS tokens that have been mapped (70.02%), 0.23% of the EOS tokens have been invalid. Based on today's EOS price ($12.40), this means that EOS tokens worth about $27 million may be invalid. For these 0.23%, if they do not remap immediately, they will lose their EOS tokens forever.

Mapping

The mapping mentioned here is public key mapping, which is to associate the EOS public key registered on the EOS contract with the EOS wallet where we store tokens . Therefore, you need to apply for the public key and private key on the EOS native public chain, and then associate them with your ETH address.

Why do we need to map the EOS mainnet? Because the current EOS tokens are on the Ethereum network, which is a different public chain from the EOS mainnet that will be launched. After the EOS mainnet is launched, native EOS tokens based on the EOS mainnet will be issued. Only after you have done the mapping step, the EOS mainnet will generate the corresponding number of tokens for you.

PeckShield disclosed two reasons for the invalid EOS mapping:

• Token holders use the publicly available EOS key (EOS6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV) for mapping, accounting for 0.19%;

• Using illegal keys (commonly used addresses such as EOSCrowdsale and EOSTokenContract as keys) for mapping accounts for 0.04%.
  

So far, PeckShield has found 1,243 illegal EOS keys and 325 affected wallet addresses. Affected wallet address query: https://peckshield.com/2018/05/31/eos/

Regarding remapping, it is divided into two steps:

• Generate a reliable key according to the method on the official website.
  

• Use the newly generated key to remap according to the officially recommended mapping steps.
  

Related reference URLs:

https://github.com/EOSIO/eosjs-ecc#usage-object-api

https://steemit.com/eos/@eosnewyork/securely-generating-an-eos-public-private-key-pair-using-official-eos-io-code

For coin holders, there are currently three options for completing the mainnet mapping:

• Individuals can perform mapping manually, but the operation is more complicated and there is a risk of private key leakage.

• Transfer the tokens to a wallet that supports mapping. However, the mapping operation on the wallet is more complicated, and you need to import your own private key during the mapping process, which raises the risk of losing your private key.
  

• Transfer your EOS tokens to exchanges that support EOS mainnet mapping. After the EOS mainnet is launched, these exchanges will automatically convert your tokens. And even if all ERC20 TOKENs are frozen after June, you can still trade shares (sugar rights) through exchanges.
  

Of course, there are some disadvantages to placing it on an exchange. For example, not all exchanges support airdrops or support every airdrop, so you may not get any candy.

As for how to complete the mainnet mapping, you can make a comprehensive consideration based on aspects such as your personal operating capabilities.