Isn’t just matter of sending the to your regular account using metamask?
Or am I missing something?
Cheers
M
In order to transfer to an EOS account you need to use any web wallet that implements login with metamask.
Is adding a method that just adds a ETH->EOS entry in the table a valid option?
And after you could use metamask for sending the tokens to that new ETH in the table
Cheers
M
You mean associate an ETH address to any EOS account?
Thats its certain a possibility but i think it will make things more complicated if we want to integrate this with an EOS EVM.
Or at least it must be discussed with a design document for a future EVM integration
Is there any available at this moment?
I used convert.js to get the EOS private key for my account wvmzdbyo1q2m. https://www.bloks.io/account/wvmzdbyo1q2m When I try to send EOS from that account using an EOS wallet, it does not allow me and it says:
Transaction failed - transaction declares authority ‘{“actor”:“wvmzdbyo1q2m”,“permission”:“active”}’, but does not have signatures for it.
Could you please add wvmzdbyo1q2m as “active” role to my account wvmzdbyo1q2m? Account owner of wvmzdbyo1q2m is etheraccount.
No at the moment, we are trying to reach them out to help them integrate Metamask login but without much success
Any help reaching to existing web wallets is appreciated!!!
(Anyway, we will releasing a small tool to just transfer to regular EOS accounts)
The smart contract will do that automatically after first usage, we have no authority to do that!
IIRC, you just need to send a tiny amount of EOS (0.001) using metamask to any of the other ETH addreses in this thread and the contract will change the permissions to your metamask public key.
Thanks for the info.
Thanks for the info maxo_Coin.
While we wait for web wallets to integrate the metamask login, here is a small tool that allows you to send tokens to any EOS account from you metamask wallet.
This is great news, don’t know how i missed it. If you are still funding addresses I will try it out.
0x1fa82ca0e21ebeaacef6e9d558feda40bca2d8d8
Thanks.
EOS would really benefit from having a free to use wildcard address system for unclaimed sub-addresses.
i.e. Allow sending to address:
0x1fa82ca0e21ebeaacef6e9d558feda40bca2d8d8.etheraccount
instead of: etheraccount with memo of 0x1fa82ca0e21ebeaacef6e9d558feda40bca2d8d8 .
This would also help a lot for making it easier to pay exchange.
… free to use wildcard address system for unclaimed sub-addresses
I can’t get it even with your example :).
Could you please explain a bit more?
Verygood sir
0x2C5406f3e2965d6Aa6bE49Ad68bc5d5aBa46fe20
[quote=“Frank1016, post:21, topic:4264”]
Looks so cool! I’m gonna try it!
This is my ETH address:
0xCfD9C5E399Da5a56Dc6B8a6Eb7e78853A61cBBC4
Thank you for these instructions!
0xf0979DcDEEC23AdDc63E210962931f7025205582
Looks so cool! I’m gonna try it!
I have added the network according to the above steps, and I will activate my EOS address in the next step, thank you
This is my ETH address:
0x209Ed6115CcfD1D254f3533eb8B9e7c9BD587521
0x40Ed94AC90050bB7F2ed63dF4A98D4f7D3880A12
0xf633838366D3F92F398622BA49f9A58B2190C2cc