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

3rd Community Diligence Review of EF Allocator #185

Closed
Lind111 opened this issue Oct 7, 2024 · 6 comments
Closed

3rd Community Diligence Review of EF Allocator #185

Lind111 opened this issue Oct 7, 2024 · 6 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

@Lind111
Copy link

Lind111 commented Oct 7, 2024

Record of last review

https://compliance.allocator.tech/report/f03014490/1728259518/report.md

This datacap has been assigned to the following two clients

Lind111/EF#27

Lind111/EF#9

@filecoin-watchdog
Copy link
Collaborator

Allocator Application
Compliance Report
1st Review
2nd Review

1st Review score: 2.5PiB granted
2nd Review score: 5PiB granted

2nd allocation on 9/17

DC granted to two clients on this round:
New client
Ongoing client

Example of ongoing client
The Client has stored 13 replicas even though 11 were declared. The Allocator contacted the client for further clarification.
This client works with as many as 17 SPs, 4 of which have a retrieval rate of 0%.

Example of new client
The Client said the proposed dataset wasn’t stored on Filecoin before, but that’s inaccurate. The previously sent dataset might be irretrievable, but the Client and the Allocator should have checked that and explained accordingly.

Since June 2024, the client has cooperated with several different allocators on other datasets. All those issues are still open, and DC was granted in each case. The gov team should follow up.

The retrieval rate oscillates between 49-70%

According to the compliance report there are 3 allocations, but the github repo only confirms 2. How did the 3rd allocation get transferred?

The Allocator does KYC processes through e-mail. The Gov team should follow up.

@Kevin-FF-USA Kevin-FF-USA self-assigned this Oct 8, 2024
@Kevin-FF-USA Kevin-FF-USA added Refresh Applications received from existing Allocators for a refresh of DataCap allowance Awaiting Community/Watchdog Comment DataCap Refresh requests awaiting a public verification of the metrics outlined in Allocator App. Diligence Audit in Process Governance team is reviewing the DataCap distributions and verifying the deals were within standards and removed Awaiting Community/Watchdog Comment DataCap Refresh requests awaiting a public verification of the metrics outlined in Allocator App. labels Oct 8, 2024
@Lind111
Copy link
Author

Lind111 commented Oct 9, 2024

The Client has stored 13 replicas even though 11 were declared. The Allocator contacted the client for further clarification.

The customer has provided an explanation and I will consider closing the issue and letting the customer reapply
image

According to the compliance report there are 3 allocations, but the github repo only confirms 2. How did the 3rd allocation get transferred?

Triggered a bug when signing
fidlabs/allocator-tooling#77

@Lind111
Copy link
Author

Lind111 commented Oct 9, 2024

If there are any other questions, please point them out specifically, thanks!

@Lind111
Copy link
Author

Lind111 commented Nov 1, 2024

@filecoin-watchdog @Kevin-FF-USA @galen-mcandrew Hi
It's been three weeks, any updates here please?

@galen-mcandrew
Copy link
Collaborator

Overall good diligence and compliant behavior. It would be good to see how this allocator is investigating clients that are working with multiple allocator pathways. It is reasonable for a client or data preparer to be working with multiple teams, but there should be investigation, diligence, transparency, and justification for that behavior.

Perhaps your team is able to help work on this, and make some additional developments, suggestions, or tools for the community.

At this time we are requesting 10 PiB of DataCap from RKH, to allow this allocator to show increased diligence and alignment.

@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 Nov 2, 2024
@Lind111
Copy link
Author

Lind111 commented Nov 3, 2024

Thanks @galen-mcandrew

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