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

2nd Community Diligence Review of Meta Era Allocator #108

Closed
filecoin-watchdog opened this issue Jul 19, 2024 · 7 comments
Closed

2nd Community Diligence Review of Meta Era Allocator #108

filecoin-watchdog opened this issue Jul 19, 2024 · 7 comments
Assignees
Labels
Awaiting RKH Refresh request has been verified by Public, Watchdog, and Governance - now awaiting release of DC Refresh Applications received from existing Allocators for a refresh of DataCap allowance

Comments

@filecoin-watchdog
Copy link
Collaborator

@CockroachBoss
Allocator report:
https://compliance.allocator.tech/report/f03014641/1721400670/report.md

First diligence review: #19

SP retrievals still low on two public open dataset clients

@Kevin-FF-USA Kevin-FF-USA self-assigned this Jul 19, 2024
@Kevin-FF-USA Kevin-FF-USA added Diligence Audit in Process Governance team is reviewing the DataCap distributions and verifying the deals were within standards Refresh Applications received from existing Allocators for a refresh of DataCap allowance labels Jul 19, 2024
@galen-mcandrew
Copy link
Collaborator

This allocator is still primarily working with the same 2 clients, and those both claim to have public open data. While there is some evidence of intervention and diligence on the part of the allocator to these clients, the clients are still broadly non-compliant. For example, this report still shows non-compliant retrieval (despite claims of updates and additional retrieval methods) as well as non-compliant data distribution to SPs (regional, number, VPNs).

The primary client has incomplete initial application details (with multiple "No Response" answers). This client claims to be an SP preparing slingshot data, with a wide range of claimed data types but no explanation of data ownership or provenance.

The other client AOLIGEI has already been flagged in this ecosystem for showing up across various seemingly unrelated projects and noncompliance.

Beyond these issues, there is increasing evidence that this allocator is not making sufficient effort to enforce their own stated application targets and requirements. For example, question 10 listed only enterprise web3 clients as target clients, and neither of the above approved clients fit that category. There is also no evidence of utilizing 3rd party KYC services, or

Given the continued support of this kind of activity across a range of metrics (missing client info, lack of data ownership, poor SP distribution, insufficient retrieval, previously flagged data clients, etc), as well as the broad and unenforced nature of the initial allocator application, we are proposing removal of this allocator pathway.

This team can reapply under the new rolling application with a more scoped and specific set of requirements, such as a more narrow set of allowed client and data types.

@galen-mcandrew
Copy link
Collaborator

@CockroachBoss

We have reviewed the information provided here, and we will request an additional 2.5PiB of DataCap. I strongly encourage you to review you allocator application, and make extra effort to provide evidence of diligence and compliance with all the requirements.

@galen-mcandrew galen-mcandrew added Awaiting RKH Refresh request has been verified by Public, Watchdog, and Governance - now awaiting release of DC and removed Diligence Audit in Process Governance team is reviewing the DataCap distributions and verifying the deals were within standards labels Sep 25, 2024
@Kevin-FF-USA
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting RKH Refresh request has been verified by Public, Watchdog, and Governance - now awaiting release of DC Refresh Applications received from existing Allocators for a refresh of DataCap allowance
Projects
None yet
Development

No branches or pull requests

4 participants
@filecoin-watchdog @galen-mcandrew @Kevin-FF-USA and others