Update IdentityVerification.yml

[ABISprotocol]

Extending details and distinctions of IdentityVerification proposed as tiered process for either organization members (staff) or users of organization (e.g., exchange, brokerage, etc.). Includes traditional and decentralized identification methods.

[Abstrct]

Typical methods of identity verification which are necessary for staff or consultants working for organizations (exchanges, brokerages, etc.) include:

Methods of identity verification which could be deemed necessary for users (of an exchange, brokerage, web wallet, etc.) might include:

Providing a tiered list of suggestions is a good idea, but I don't believe it should be organized based on who is being verified. I think the when and why of the verification is just as important. It may also be purely a business decision which one is used, so we need to be careful not to be too prescriptive, just provide a benchmark of effectiveness and prescribe strength where we all agree it is required.

I'm not as familiar with all the new options as I'd like to be (namely BlockchainMe & Blockchain ID), so I'm going to do a bit more research on those for the time being.

Overall, good idea though. Thanks for the contribution!

[ABISprotocol]

Thanks, I look forward to further comments on this idea, and have left it open so that the people with commit ability on this repo can change it prior to merge if you'd like. Let me know if there are any issues there.

[Ekinmayer]

Thanks