I doubt that EOS token held on Binace will be detected by a "SNAPSHOT".
From what I understand the coins you have on most exchanges are not actually on the block chain. Rather I think that they are internalized on the exchanges private reserve.
This is all implied by reading the official EOS.IO website. Until June 1, 2018 the eos erc20 tokens have to be on the block chain outside of the exchange and in an etherium wallet (or metamask chrome browser extension). correct me if I am wrong, but I am pretty sure your can use a trezor or ledger hard wallet to securely access these wallets. Nevertheless once the eos tokens are in your etherium wallet, then you also need to follow up and register your wallet with EOS.IO. This step can be accomplished by following the detailed instructions on the EOS.IO web site under their "DISTRIBUTION" banner. Even if you use etherium out of your own etherium wallet to buy EOS tokens directly from the EOS.IO website distribution link, you still need to register your wallet address with EOS. This is so that they know to include you in their so called "SNAPSHOTS" so they can audit the balance of your eos tokens. Then hopefully new coin DEVELOPERS will launch surprise "AIRDROPS" with an avalanche of multitudes of hundreds of millions of newly minted wondrous assorted digital coins of various denominations that are presently being tested and developed at GIT HUB on the eos platform. They will all be switched over to launch and run on the "BLOCK ONE" block chain after June 1. I am pretty sure that if you buy tokens directly off the EOS.IO site, then you do not have to "CLAIM" them back into your wallet (unless you want to transfer or sell them elsewhere, in which case you will miss out proportionately on the airdrops as the wallet will not show any coins when developers do a snapshot audit of your registered wallet address. EOS says that they prefer that you reserve one wallet address exclusively for eos erc20 tokens.
Here is the mind bender though. Come June 1, with the launch of BLOCK ONE, your eos token will become obsolete and retired - but NOT forgotten. EOS erc20 token need etherium, but BLOCK ONE tokens will not...duh. Perhaps your EOS tokens will become enlightened and ascend mysteriously to the upper heavens of BLOCK ONE and inhabit that space as angels to watch over and help govern and nurture newly minted tokens - a fantastic metaphor perhaps. As I envision it, on June 1, when BLOCK ONE launches it's first seed block, at that juncture you will have a proportionate "STAKE" share in the BLOCK ONE block chain / operating platform which will be the backbone core blockchain that supplies the "BANDWIDTH" that all the newly developed blockchain coins will need in order to run for perpetuity. BLOCK ONE supported coins will be essentially smart contracts written/coded by developers. Each brand of coin will need to acquire some appropriate amount of bandwidth to operate on BLOCK ONE. Stakeholders on BLOCK ONE will be able to rent out bandwidth like a TRUE UTILITY - or outright sell their stake to someone else.
This is an ecosystem that synergistically aligns the beneficial interests of all stakeholders for the first time in history. It is a win-win-win GENEOS technology - how smart is that contract? I am so grateful for the thoughtful way in which EOS has metered out their token distribution. I am a small fish, not a whale. It took me a long time to begin to solve this riddle, and the slow motion distribution has allowed me time to participate. I bought EOS erc20 tokens directly from EOS.IO distribution link on their web site. I also registered my etherium wallet public key directly with the EOS distribution site. I have not bothered to claim EOS token back to my wallet. This is simply because the eos distribution site stated explicitly that it was not necessary to do so. IMHO, no matter if my EOS tokens are worthless June 1, it will have been well worth it. Potentially on June 1, 2018 on planet earth there will dawn a global redistribution of wealth. no one is making any promises, but it could be glorious.
You are viewing a single comment's thread from: