top of page
Blog: Blog2
Search

Privacy-Preserving, Mutual Identity Verification with TRIO Crypto Tokens

Updated: Mar 15



There are many situations where parties in P2P (Person-to-Person) transaction need to verify each other Identity:

Examples range from P2P Crypto Trading and P2P Lending/Crowdfunding to Dating Services and Digital Signature of any content (image, video, audio, or text).

Why verify? Simply because many identities are fake. The estimates for fake social network profiles are in the 5-15% range.

Every application has difficulty integrating the Identity Verification mechanism into the workflow. The following is the workflow that TRIO enables for its users:




The parties in P2P transactions may be required by regulatory compliance and fraud prevention best practices to verify each other Identities. These requirements are challenging to integrate into the existing Web infrastructure for P2P transactions in a privacy-preserving manner. TRIO makes this integration simple for its Users. This is how it goes:

Each party (Buyer or Seller) may publish their Public Address.

If somebody (say, Buyer) wants to engage in a P2P transaction - they send 1 TRIO token to the public address of another party (say, Seller). The recipient of the token queries TRIO for the Identity credentials of the Buyer as may be required by AML regulation. Then the Seller returns the token to the Buyer's public address. The recipient of the token queries TRIO for the Identity credentials of the Seller as may be required by fraud prevention best practices. Both parties verify each other Identities in a Privacy-Preserving way and can proceed to their original P2P transaction.

Scope of credentials.

Sometimes the partial scope (First Name, Last Name, Email) is adequate, but additional info (Phone#, Address, Birthday) is sometimes required.

Naturally, the decision to share credentials and their scope must be exclusively by the regulatory requirements and specifics of the application.

How to enable this?

The flow for partial identity scope.

Person 1 publishes his wallet public address (say on Twitter). If Person 2 wants to contact Person 1 privately – he must disclose his identity with partial scope (First Name, Last Name, Email). To do that, Person 2 will transfer to Person’s 1 wallet 0.5 TRIO token (representing authorization to receive Identity partial scope). On receipt – Person 1 will query TRIO SaaS for the required Identity scope using transaction details.

The flow for full identity scope,

Person 1 publishes his wallet public address (say on Facebook). If Person 2 wants to date Person 1 – he must disclose his identity in full scope (First Name, Last Name, Email, Phone#, Address, and Birthday). To do that, Person 2 will transfer to Person's 1 wallet 1 TRIO token (representing authorization to receive Identity full scope). On receipt – Person 1 will query TRIO SaaS for the required Identity scope using transaction details.

About TRIO utility tokens.

They are not traded on the exchanges and are served exclusively in the TRIO network for their utilization.

Short video summary:


25 views0 comments

Recent Posts

See All

Comments


bottom of page