-
Notifications
You must be signed in to change notification settings - Fork 41
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
Comments
Allocator Application 1st Review score: 2.5PiB granted 2nd allocation on 9/17 DC granted to two clients on this round: Example of ongoing client Example of new client 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. |
The customer has provided an explanation and I will consider closing the issue and letting the customer reapply
Triggered a bug when signing |
If there are any other questions, please point them out specifically, thanks! |
@filecoin-watchdog @Kevin-FF-USA @galen-mcandrew Hi |
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. |
Thanks @galen-mcandrew |
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
The text was updated successfully, but these errors were encountered: