Implementation of a Third Party KYC (ID Check) for Fil+ Applicants

Background

In the Fil+ application process, all application information is public in a GitHub issue in the Fil+ repo. Because all information is public, applicants are only required to use GitHub IDs as a personal identifier in an effort to keep personal information (name, email) from public view (and from potential abuse from scammers who scrape for ID info).

However, using only GitHub IDs to identify applicants creates issues because there are a large amount of unknown accounts being created and applying for DataCap. And without knowing the person/entity behind the GitHub account, it creates a lot of potential abuse from fake accounts.

Applicant ID Check Process

In an effort to cut down on abuse during the application process, we have implemented a third party KYC (ID check) process to allow all Fil+ DataCap applicants to get their ID verified and have that verification be associated with their GitHub ID on the public application view.

Steps

1. Applicants go to Filplus.storage and login/register with their GitHub credentials.

2. Once logged in, from the same menu, there is an option now to select “Get Verified”. Applicants can click on this link and it takes them to the third party website to complete the verification.

• Steps include: ID check (Ex: License, Passport scan) and Liveliness check (Facial recognition check to match the ID).

3. Once verified, the applicant will show as a Verified User in Filplus.storage. See example below:

4. Also, on any applications created by the applicant, the application will show a “kyc verified” label so that Notaries and other community members can confirm the GitHub user is a real person behind the application . See label example below:

Important Notes about the applicant data:

• The KYC check process is completed by, Togggle.
• During the data collection phase, all personal information gathered is securely encrypted using the individual user’s personal key. This ensures that the data remains confidential and inaccessible, even to Togggle
• Applicant personal information will never show on GitHub applications, only the kyc verified label will signify a check was complete.

Next Steps

• All E-Fil+ applicants will be asked to complete this KYC check as part of the application process
• All other Fil+ applicants will be able to opt-in on Filplus.storage to complete the check, but are not required. Adding a kyc verification adds a layer of trust to a GitHub user account and will enable notaries to complete due diligence.
• Also, soon, all active notaries will be required to login and complete the KYC check to confirm that submitted notary information corresponds to ID check