-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Addressing top of funnel DC abuse - KYC on incoming GitHub applications #833
Comments
Trulioo - https://www.trulioo.com/ |
Finally. Sounds perfect. |
Very welcomed proposal. |
I checked out the Trulioo platform.It can create workflows that match specific validation needs. |
What's the detailed KYC process? There's no elaboration on the website. I would love to learn more about it. |
What KYC info is required ? Trulioo applicable to Asia countries? |
On the whole, agree very much. Potential issues to be weighed:
|
Hi, Just to give an update about the community stance in numerics about this. I received 61 KYC submissions since Dcent started this a few weeks ago from all over the globe for around 80 LDN's. Fil+ improved in quality ( most of the content is retrievable now as participants know what to expect ). The participants who are serious getting the attention they deserve since notary's are more comfortable signing (quicker) as they know who they are dealing with and what to expect. It has had a positive effect on the Filecoin economy and price ( Participants who are not serious will not keep their FIL from their sold DC and try to get out as fast as they can to eliminate risk ). Conclusion from my side: There is no reason to not go on this path and get this proper and cleaned up with Fil+ Get it done asap! |
Thank you everyone for the comments. Given the overwhelmingly positive support, this proposal is considered passed by consensus |
Here is the google form to express interest to take charge of scoping a 3rd party KYC vendor in their region and conduct such checks on behalf of the community - https://forms.gle/MjjsFM8p7n64gkWKA |
@raghavrmadya The implementation of Know Your Customer (KYC) for reducing the influx of LDN’s is of utmost importance and requires immediate attention. Is there any additional support or input required from the community beyond approval? Each day without this measure in place represents a lost chance to acquire crucial information about clients and mitigate the risk of potential fraudulent applications slipping through unnoticed. |
@raghavrmadya Hi, could we apply for this KYC service now? https://docs.google.com/forms/d/e/1FAIpQLScQc2EMsj93265YWiXlyuuwMDv-EZY9xwAx-p8mLf59xrr6eg/viewform |
FYI - @raghavrmadya and others. A third party KYC product via Togggle.io is being integrated into Filplus.storage for every applicant. Goal is to go live by May 1. |
hey Does it mean we will not move forward until the 3rd party KYC product goes live on1st, May? Thanks |
@carol19920101. KYC will be an optional step in the process starting in May. You can move forward now, and also, if you like, you will be able to complete KYC after an application is created. |
Issue Description
There is a large amount of fake/unknown GitHub accounts that apply for DataCap
Impact
This leads to a lot of potential abuse of DataCap without knowing who is the entity/person behind an LDN application
Proposed Solution(s)
Make it mandatory to complete a 3rd party KYC check that is linked to their GitHub account. The current proposal is to use a tool called Trulioo
Timeline
Feb 23rd 2023 - March 3rd 2023 - Discussion
March 7th 2023 - Consensus announced based on discussion at T&T WG call
Technical dependencies
Integration with the Trulio platform
Risks and mitigations
Slowdown in incoming LDN traffic
Related Issues
N/A
The text was updated successfully, but these errors were encountered: