As the thread subject mentioned, I strongly believe the KYC documents requirement from the ICOs will open up a new area of scam to the world, much larger than the ICO itself.
Reason 1:
The basic idea of crypto currency is de-centralization and anonymity. I understand that ICO will have to comply with the regulatory requirements, but isn't it directly challenging the basic idea of crypto currency? If KYC is required for every ICO, then the whole idea of de-centralization and anonymity is gone. The ICO requirement should be the other way around. Means, every ICO should provide a proper KYC documentation to the public so that investors can be assured that they are not dealing with a bot or a child operating from his home computer.
Reason 2: (this is a big threat)
KYC means "Personally Identifiable Information" and it is a very serious level of data. Most of the governments have a very stringent rules against the breach of PII data, especially in USA. The SSN numbers of USA residents are traded in darkweb for $5-$10 each based on the details available. While most of the ICO owners are not identifiable to public (linkedin and FB profile can't be considered as valid here), they can secretly open up a secondary market for PII data, that will provide them an extra layer to their income. Most of the ICOs are not compliant with the infosec policy of many countries. No one is sure, what is going to happen with their data. It leads to a much larger future scam.
Reason 3:
It provides a big opportunity to the ICOs to deny the bounty hunters from their payment even after their promotional efforts. I am not sure we have already encountered some of these, but I am sure it will happen in future. I have seen no ICO bounty thread mentioned anything about the KYC requirement. There is no upfront communication. However, they may come back saying that KYC needs to be done before the bounty rewards can be released. That's complete miscommunication and cheating. If the ICOs can be upfront on their KYC requirement (which they are not), only bounty hunters and investors will join who can fulfill the requirement. The campaign managers needs to be upfront in this matter.
*While I don't know what needs to be done in order to regularize the first two reason, the third reason can be solved via upfront communication. Please share your thoughts.
This is something I've been thinking about because it's a real problem. I have some ideas but there's no perfect answer to the situation.
Here in the United States we have legal requirements for Know Your Customer / Anti-Money Laundering / Countering the Financing of Terrorism. I certainly understand the reason we have these regulations in place, but when you apply the same principles as used in legacy banking and finance to the world of crypto assets, new problems emerge:
- How do you know the ICO is who they represent themselves to be?
- How do you know the ICO is going to safeguard your PII? They could be careless and it could be stolen through a hack, or they could be malicious and sell the information or use it directly to steal your identity. Sad to think about, but some of the ICOs are full-out scams.
- What happens to your information if the ICO fails, shrivels up and dies?
- How do you still comply with the legal requirements while implementing a trust-free model?
The answer I come up with is to have a trusted party conduct the KYC and make attestations to ICO issuers. But, I don't like that idea because it has a point of centralization that could abuse trust. So, I'm thinking about a decentralized way to do it. Potentially something like, go through the KYC gamut with your primary exchange, be that Binance or Coinbase, etc., and then they would be able to issue some type of credential that ICOs would accept as KYC verification without having access to all of the information directly. Potentially even non-exchanges could provide this as a service. If done properly, you as a user would be able to approve what information they are able to access, on an ICO by ICO basis (or any other entity that was using the system, for that matter). Somewhere in this concept a user would have to place trust in someone, someone must actually perform and verify KYC, so I figure the best place for that trust to be the exchange they already have a relationship with.
Facebook has something like this in how they implement third-party app permissions (as does Android). They have a basic permission that allows them to get basic information, and then if the app needs more information, like your social graph, or the ability to post, etc. it's another "confirm/decline" decision for the user.
I think something like this could be the way to go, but it needs an open standard on conducting the due diligence as well as a software interface to accessing the information. It's an idea that's been in my mind as something that we should look at through BTRIC Institute.
I believe if done right it would reduce fraud.
Best regards,
Ben