If you don't re-register, the same private key will be used to claim both the Evolution (EVO) and the EOS tokens. Right now a conservative person might worry that Evolution is trying to steal the private keys that will claim peoples' EOS stake. They could do this by creating software that has you enter your private key to claim your EVO tokens, and then using that private key themselves to take control of your real EOS account.
If they publicly encourage people to change their keys after the Evolution airdrop date, that gives us more reason to trust that they're not just trying to steal EOS keys.
If they were actually scammers (note, I have no idea if they're legit or not, but with security always assume the worst), we might expect them to go out of their way not to educate people about the risks.
We will never ask for your private keys and the registration for Evolution is through EOS.io which operates the initial sale of EOS tokens. Again, we are not asking anyone for private information. This is all done through EOS.io the official developer of EOS.
Forgive my cynicism, and thanks for replying.
I'm talking about later, once the EVO and EOS chains are operational, not now as people are registering keypairs for the airdrop. Once the Evolutionos chain is running, how will people claim their EVO tokens? Their private key will have to interact with your software in some way. If they haven't updated their EOS keys after May 10th, they'll be in the insecure position of having a single key control balances on both EOS and EVO. It would be fairly easy for you to steal peoples' valuable EOS private keys when they claim their EVO balances.
By telling people to change their EOS keys before claiming their EVO mainnet stakes, you have the opportunity to publicly increase your credibility -- as this isn't something a thief would do.
Evolution is a separate chain and will have no relation to any EOS key pairs. The airdrop to registered users was just one of the many ways to verify that the airdrop was being sent to core contributors and non-exchange owners of the EOS token. The EVO token will be distributed as an ERC-20 token and the swap to a native EVO token on the Evolution blockchain will have no correlation to the EOS blockchain. This is an adaptation of EOS and not a connected chain. The public wallet ID ( EOSxxxx) is also not being used for anything. Registration was only a means to identify airdrop participants. To receive the EVO native token we'll establish some guidelines in the months ahead on how to interact with the Evolution blockchain. Which, again, is not interconnected with the EOS chain or it's users private keys.
Hopefully this gave your more clarity around your question.
Excellent, I had missed this. That satisfies my concerns. I look forward to seeing what you come up with!
Interesting point. This would be like moving your BTC after every BTC fork coin (bitcoin cash, bitcoin gold, bitcoin private, etc). Personally, that may be overkill. If you're concerned, you can always move your EOS before doing anything for a fork or airdrop (I covered this 9 months ago here). But you're right, if there are multiple drops, you'll endanger something (even if you move your EOS) unless you create new EOS addresses each time.
That said, I'd never EVER participate in something that required a private key. There are many other ways to do this including signed messages.
Unlike eosDAC the Evolution tokens will never be converted over to the EOS blockchain. Evolution is not a hard fork since EOS is not a fully launched blockchain.
The EVO token will be distributed as an ERC-20 token and the swap to a native EVO token on the Evolution blockchain will have no correlation to the EOS blockchain nor the private keys on the future EOS blockchain.
Way back in the early bitshares days with PTS and such, I got into the habit of changing my keys after every snapshot, and if I ever claim my balances of the Bitcoin forks I'll do the same. As long as you have good key management, it seems like good security practice. I do not like the idea of a single key controlling balances on two chains.
This is why I've still never claimed my peerplays-bitshares airdrop -- the official way to claim is to enter your BTS owner key in the peerplays client. Utter madness!
Very good point! not only for this airdrop but for the others doing similar approach.
@evolutionos?
When eos is live will moving my eos tokens to a new private key before claiming any air drops work just as well?
Yes, that would be fine.