Unfortunately, I think this has a flaw. Since no one planned ahead of time for the ETH key to be accessible to get the EOS chain tokens, it wasn’t necessarily safeguarded as such. Which means that if you made this change now it could be a massive security hole for many people, which makes it a non-starter as a solution. For example, in order to access some of the ETH token airdrops on ETH chain (i.e. EOSDAC) people may have exposed their private key after they knew the EOS ERC20 token was locked up to access the airdrops and then move them. It’s hard to add new powers to something that wasn’t previously defined as such. Best of luck to you in recovery through the current process!
You are viewing a single comment's thread from: