Skip to content
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

Modification: Changes required to public open dataset application flow #922

Closed
ghost opened this issue Jul 7, 2023 · 11 comments
Closed
Assignees
Labels
Proposal For Fil+ change proposals

Comments

@ghost
Copy link

ghost commented Jul 7, 2023

Issue Description

In the past few months, many community discussions and disputes have been opened, primarily related to abuse of open, public dataset applications.

More specifically:

  • that clients are not following the Fil+ guidelines especially proper geodistribution with multiple SP entities and confirmation of retrievals being made available for the dataset.
  • that notaries are signing said applications without proper due diligence

Impact

It’s important to remember the focus of the Fil+ program is to subsidize reliable and valuable decentralized storage on the network. If applicants are clearly not working with the same focus, and at the same time continue receiving DataCap, then something needs to change to the current approval process.

This proposal is therefore focused on:

  • Better enforcement of clients adhering to the Fil+ guidelines by collecting more details upfront about the client and SPs involved.
  • Clear steps to monitor and compare the initial allocation storage results to the application plan.

Proposed Solution(s)

Moving forward, we recommend that all open, public data applicants MUST:

  • Complete this registration form for review by Fil+ Governance Team prior to an application being triggered for notary review.
    • The information submitted must have clear details about data preparation, project funding, data distribution, and all details regarding SP entities they will be working with, including contact information and confirmation of retrievals, upfront as part of their application.
    • If it does not have this information, applicants will be asked to return and re-submit once they have a plan that meets guidelines, specifically listing SP entities meeting Fil+ guidelines.
    • Once an application meets these guidelines, notaries will then be asked to review the application and conduct any additional due diligence.

Then, after a first DataCap allocation:

  • Notaries, as part of their required due diligence, need to review that the original application plan matches the actual actions of the client. Specifically, are SPs in CID report as listed in application and are retrievals being made available at a 'community accepted' rate.
  • If not, clients should be guided to make necessary changes to meet requirements before any future allocation.

After, if a client confirms Fil+ requirements are now met and the client plan again does not match after a second allocation (SPs are not as reported and retrievals are not available), then the application will be closed.

  • Likewise, any notaries caught blatantly signing on applications where Fil+ guidelines aren’t being met, will be submitted to T&T WG for review and potential dismissal.

Timeline

Proposal to be reviewed on upcoming Governance Call
Updated proposal process flow to be implemented after review and approval for all new applicants

Technical dependencies

In the short term, applicants will be manually asked to complete the Fil+ registration form. In future iterations, automations can be considered to support these processes more efficiently.

End of POC checkpoint (if applicable)

After 3 months, by October 30th, all new open, public dataset applications will be reviewed and results summarized as:

  • number that met guidelines without issue
  • number that did not meet guidelines after first allocation, revised application
  • number that did not meet guidelines twice, closed

The goal is to determine if the upfront check and initial allocation reviews:

  • Prohibits fake applicants from receiving DataCap without meeting clear requirements
  • Promotes clients that follow guidelines to get DataCap without delay

Risks and mitigations

  • Notaries will need some training to ensure they understand this process flow and their required participation

Related Issues

Note: Related, we’ve found recently in the E-Fil+ pilot that the use of an upfront registration form to vet all applicants enabled those clients with a legitimate onboarding and storage plan to be able to provide sufficient information about their business, funding and storage plan.

@ghost ghost added the Proposal For Fil+ change proposals label Jul 7, 2023
@herrehesse
Copy link

I agree with the proposal from @Filplus-govteam to enforce Fil+ guidelines (rules?), collect upfront details, and review applications to ensure compliance. It's a positive step towards reliable and valuable decentralised storage on the network.

@ghost ghost mentioned this issue Jul 7, 2023
@alchemypunk
Copy link

Finally see a more standardized process.

@spaceT9
Copy link

spaceT9 commented Jul 10, 2023

This is a great proposal which will effectively reduce dataCap abuse!

@NDLABS-Leo
Copy link

@Filplus-govteam
I am willing to support it, and I hope the community can establish a certain consensus so that all community members have a unified standard for criticism. We still have a long way to go, so let's complete the first step and discuss further optimizations afterward. Thank you for your work. By the way, is the Filplus-govteam account an official account?

@modmeta
Copy link

modmeta commented Jul 10, 2023

this is a Positive proposal.In addition, clear Review methods and auxiliary tools are employed to avoid ineffective work and review loopholes.

@kevzak
Copy link
Collaborator

kevzak commented Jul 11, 2023

@Filplus-govteam I am willing to support it, and I hope the community can establish a certain consensus so that all community members have a unified standard for criticism. We still have a long way to go, so let's complete the first step and discuss further optimizations afterward. Thank you for your work. By the way, is the Filplus-govteam account an official account?

Yes, I can confirm @Filplus-govteam is the Fil+ Gov team collective account.

@Chuangshi1
Copy link

waiting for the further step.

@Joss-Hua
Copy link

Support. This is the necessary path to eliminate friction.

@liyunzhi-666
Copy link

I support this proposal.

@woshidama323
Copy link

We also support but also please have a look at our concern about
Regulate community claims to make them more reasonable and fair

@ghost
Copy link
Author

ghost commented Jul 20, 2023

This modification proposal has seen overwhelming support in the past two weeks.

We will being implementation of the new application flow for all newly opened applications as well as any application with less than 2 allocations starting today.

We will report back on governance checkin calls on progress and insights.

@ghost ghost closed this as completed Jul 20, 2023
This was referenced Jul 20, 2023
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Proposal For Fil+ change proposals
Projects
None yet
Development

No branches or pull requests

10 participants