You are viewing a single comment's thread from:
RE: What you need to know about mapping an EOS Public Key to an Ethereum address
This is super useful dude, this info is hard to find. I still don't fully understand what it means for the tokens to be locked in place on the ETH blockchain.
Nor do I understand the purpose of the tokens for people not interested in developing apps.
Well, if there is a network effect with regards to app development and there comes a scarcity of resources, IE tokens, then the tokens may appreciate in value. So while it has speculative value, it's long-term. Most valuable for developers though IMO.
How do you trade a locked down token though? If I'm holding it after June 1, 2018 how would I give it to someone who wanted it more?
Ah, When ERC20 tokens are FROZEN 24 hours or so after June 1st 2018, these tokens will be worthless. It is because of this why mapping an Ethereum address to an EOS public key is so important, you are mapping your EOS ERC20 token balance so that this balance can be included as a snapshot in the genesis block of the EOS blockchain. If the ERC20 Tokens could be transferred on Ethereum after being moved to EOS blockchain, this would cause confusion and dilute valuation, among a bunch of other things.
In regards to locking, I thought you were talking about the locking in regards to locking native EOS tokens. EOS native tokens in the future, will be locked to secure "bandwidth, computation and storage" resources.
Dude, thanks so much for this reply. I still hadn't figured this out, you explained it super clearly. I found an article on how to link an eth wallet to an eos public key.
Thanks again!