EOS Mainnet is now available on Metamask

[promoangel]

0x95127fb802E3960e86D445248438Af8D7992D11c

[slandyman]

Will be happy to check it out)
0x072B20DCc0583Da9c1c3C35F9e44aedfE4554Ee4

[psteeep]

0xbF3020736D0f9DD88490fea7f11e53Dd792B4188

[zexerevev]

0xECf4b8152477b8C93855fD9a66dE6ABaEA6DCe71

[Yuan]

0x5FA0D89e8A9D415Fed9959fB2Ca43b264A196ae5

[CRAZY131419]

0x73BEaA2Dd24aDA65DF6Da284729558aFDd8105Ba

[itachi]

0xA709E4E3114D4985df2c26f1F56A1e0b3d20f48E

[topraktepeefe]

0x9F4732c9e545454896De9c81f9f3B0E8938D735c

Congrats

[hamish]

Thanks for asking, I didn’t fully explain.
I should put this in a post as a called “Feature Request: Please Allow wildcard EOS names”
If it makes sense. Please let me know if it doesn’t make sense.

Current Situation:
Currently some accounts can create sub-accounts / sub-addresses /sub-names .
For example the “gems” account has created sub-names like burn.gems and blend.gems
I would like to be able to send to *.gems ( any name at .gems)

Idea 1: Allow wildcard address names
Allow sending to an uncreated sub-addresses like anyaddressyoulike.gems
When making a transfer a wallet could check if that sub-account exists and if not direct to the parent account with a memo instead.
This could be done at a wallet level.

Idea 2: Virtual address token balances
Block explorers could check for sent and received tokens and balances for that virtual address (e.g. anyaddressyoulike.gems ) ,
Users could then see these virtual addresses listed with balances.
This way users could have unlimited addresses for holding virtual token balances.
Offering unlimited new addresses without creating extra accounts of paying any extra fees.

Idea 3: Allow migration from virtual to real accounts
If an EOS account with name of the virtual address (e.g. anyaddressyoulike.gems ) is created then that address / name would be upgraded to a full account.
This way users of a a virtual address managed by someone else could pay to upgrade to a real EOS account, with full ownership that can be used for dapps and keep the name.

[blaceflo]

Is there still a slot for the funding available?
0xDbe7d9Ca2748F0B033706acE1B988B817116bfFd

Would be very happy if it is and thanks that i can finally use EOS because before this change i didnt understand it.

[jhomz09]

thank you very much for the instructions…

0x887d60F1d27529fc3DE7c718742998a122f2B307

[hiseanchen]

hi, is there open source code for eth-provider wrapper of eos?

[lintian]

Hi. Thanks for the info. 0xE5070aa4A1f7aBF30b0636e3a8704B8A65fA00c6

[timur]

Hope not too late for this
0xd2dc28F65c76510a4A930D28664a60828C4cF64e

[timur]

Hey EOS Community! There is a problem with Metamask’s extension and here are steps to avoid loosing funds. So if you first use https://eosargentina.github.io/mmtransfer/# to transfer funds and THEN try to do the same via Metamask extension, it will offer you to paste smart contracts address instead of address you actually want to use

Please be careful with re-using address in Metamask especially about what address you add to you address book. The list of know address/account is in the smart contract so you should double check in any case. Cheers

[elmato]

Thanks for the feedback @timur!

Yes, if we want to use the Metamask local addressbook to save the ETH address of an EOS account we should always get the address from the smartcontract table

[agelospanagiotakis]

great stuff! Congrats!

0x2644B1aA23ec70ca7a3d7deA45aF18bBe3dB04d8

[madhu]

thanks…It worked well …!

if support is still available , please consider

0x840C37436edEdCd913947e4A066423daD184D4F3

[akshat4916]

Thanks for the instructions, a pretty straightforward process.

If support available - 0x346e7fe437D6d3d882eC5e9C82baeD88FC4c9a8b

[NickSanto]

Great write up. If I’m not to late, here’s my wallet. Thanks!!

0x47f064CcF66deA5Bd4Ea643F2E40E6F3eFdeE50d