Is KYC coming to EOS?
Is the EOS/Block.one team planning to implement AML/KYC on the main chain?
Check out this sub-domain: https://testkyc.eos.io/
Sure, it resolves to a "bad gateway"....but it resolves which means that they have created the sub-domain on purpose.
If they didn't create the sub-domain, then it would look like this:
Sub-domain used: https://testkycunpublished.eos.io/ (an obviously fake address)
This tells me that something is happening and KYC is at least being looked at on EOS.
I'm pretty confused because I know that @dan is an "anarcho-capitalist" and this would make it quite easy for government's to snoop and spy on us. Also, who would approve the verification process and either validate or decline an ID?
Also, what personal info would be required? Government ID? Banking history? Proof of residency?
I worked in the Offshore Banking industry (I helped build Euro Pacific Bank from the bottom up (http://www.europacbank.com) and I know first hand the types of personal paperwork we required before opening an account for someone. Also, I remember how we would decline ppl's applications and required a notary to "prove" their documents were legit. We would also CALL the notary to ensure they were properly licensed by the appropriate government. Also, we used to ask people all the time who they were sending money to and why. We would hold up your money (either sending or receiving) any time we wanted to for almost any reason. Were you rude to us on the phone one day....your account just got re-inspected and oops we need an updated, notarized passport before we will unblock your account. Listen, I understand that we still live in a government-controlled world and AML/KYC is a big part of that.
It also reminds me of @stan mentioning the other day that Bitshares was working with politicians for something as well, but I can't recall what exactly it was.
Either way, I thought it was worth mentioning today and see if anyone from the EOS or Bitshares community has additional insights.
In Liberty,
Ashe
if you follow dan trend of thoughts in his blog posts he is in favor of identities tied to accounts in the blockchain in order to avoid the problems we see today in governance, minimize criminal behavior covered by anonimity, facilitate a future universal basic income, etc. you can read this post from dan where he clearly states his thoughts about privacy vs transparency: https://steemit.com/eos/@dan/does-freedom-require-radical-transparency-or-radical-privacy
yep, i've read that but I didn't think it was going to be enforced.
I know he wants to be able to manage identities and ensure each identity is unique and real, the doubt we all have is how this will be implemented in a global way, I want to see that too :)
I guess the level of identification you will need to provide will depend on the level of usage of the blockchain: Dapp user, EOS token holder, Dapp Developer, Block Producer, etc.
Good to know something best..thanks for post @ashe-oro
Hi, It could be that this sub domain was created in relation to testing KYC for the distribution of EOS tokens and later decided against. There is no KYC for the purchase of EOS tokens from the distribution on eos.io.
Identities on the eos blockchain is something else imho although very likely will be the case that identies will make an assumption re tracability of accounts on eos mainnet back to accounts on ethereum eos (erc20) possible.
Question is, would that tracability present a problem for eos participants aquiring eos token from eos.io smart contract directly and would the same problems exist if purchased from exchanges ?
If US citizens have EOS ERC20 during EOS launch will KYC stop them from getting the real EOS?
One thing I'm concerned about is that US citizens are using VPN thinking that will ensure their actual EOS is actually in the future, but what if EOS has to do KYC / AML as part of their launch, they should reject all US citizens claiming EOS (non ERC20 ) So how does the EOS community's concern about US citizens buying useless token EOS ERC20 tokens. Cool @ashe-oro
You are absolutely right @ashe-oro
Hope #dan will resolve all this
He’s adorable and Great
Thanks for pointing out this issue
@dan WILL take care of it. He said that “now is the time to bring this kind of issues up so we can fix them”
I’m 100% sure that he appreciates your insight as we all do.
UpVoted!
I'm always skeptical when it comes to KYC.
Of course it's needed and I understand but my biggest worries are how and where my data is stored.
I don't want an unsecured basket where criminals just pick an ID and to criminal stuff.
exactly, and who's managing it? It's not a good idea to implement "legacy" banking's KYC handbook to the blockchain space. Too risky and out dated. I hope Dan is thinking clearly.
@stan want the problem will get soon! thanks you informing us!
Hope these problems would get fixed soon...
First of all, what is AML/KYC?
If it is true that they created a sub domain, how come they didn't notify anyone about it?
Is EOS domed?
Why would it?