josepablofm78
commented
4 years ago An improvement over this flow, in order to facilitate the integration between the frontend app and this private process of datacap request, could be to add a form that allows the client to fill the same info asked in the public github flow:
- Organization or personal Name
- The Filecoin address where the datacap will be assigned
- The datacap requested
- Any other additional information related with the request
- email address
So the client chooses the verifier and fills the info.
If the verifier has enabled the option of contact by email, the app will send an email to the verifier using a generic email account, like noreply@filecoin.info, with the info provided by the client.
To keep traceability it would be possible to add a filecoin email address as bcc, or to create a new issue in a private repo in github, only visible to filecoin people.
If the verifier has enabled the option of contact by github, the app, using a generic github user like filecoin-verifier-app, will post a new issue with the data provided by the client to the repo configurated by the verifier. But this repo must be private, to keep privacy, but it should be configured properly to allow new issues from the app.
Currently the flows designed to request datacap force clients to open new issues on GitHub that would be visible to all Filecoin community
For some kind of clients this flow could be not convenience in order to keep privacy, so it's necessary to provide an alternative that allows clients to contact a verifier privately.
On the landing page for clients onboarding the frontend app will show a tab where the users can consult a list of verifiers available to private datacap requests
The information shown will be Name/Organization, Location, datacap remained, email address
In this screen, a text will explain to the users they can contact a verifier of their choice via email, providing some information: name/organization, address, datacap, ...
The verifier will receive the email from the client, check the information provided, asking for further info if needed.
If the verifier is ok with the info provided, it will manually verify the client using the application.
Also the verifier must write back to the client to inform about the decision. If the verifier rejects the request, the client should be informed about the reason of the rejection.
The verifier is responsible to keep and custody these emails with the clients for accountability reasons. Filecoin could request this emails to audit.