-
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
Modification: Changes required to public open dataset application flow #922
Comments
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. |
Finally see a more standardized process. |
This is a great proposal which will effectively reduce dataCap abuse! |
@Filplus-govteam |
this is a Positive proposal.In addition, clear Review methods and auxiliary tools are employed to avoid ineffective work and review loopholes. |
Yes, I can confirm @Filplus-govteam is the Fil+ Gov team collective account. |
waiting for the further step. |
Support. This is the necessary path to eliminate friction. |
I support this proposal. |
We also support but also please have a look at our concern about |
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. |
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:
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:
Proposed Solution(s)
Moving forward, we recommend that all open, public data applicants MUST:
Then, after a first DataCap 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.
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:
The goal is to determine if the upfront check and initial allocation reviews:
Risks and mitigations
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.
The text was updated successfully, but these errors were encountered: