-
Notifications
You must be signed in to change notification settings - Fork 35
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 Hash Big Data #174
Comments
Allocator Application Issue 3 The retrieval rate could be better, as all 11 SPs hover between 50-75%. Below SPs might be using a VPN: Issue 8 The retrieval rate is very uneven across 12 SPs, oscillating from 0 to 72%. The allocator should ask the client about this inconsistency. In general, the allocator ensures that the data clients provide is correct. They ask questions when detect discrepancies and regularly check CID reports, highlighting when the retrieval rate is too low. |
Thank you for pointing this out, I will continue to follow up on this issue, thank you! |
Based on the investigation and details provided, we are seeing mixed compliance results. Some areas for this allocator to focus on should include:
Given this review, we are requesting that the allocator verify that they will uphold all aspects & requirements of their initial application, with some extra focus on these areas. If so, we will request an additional 10PiB of DataCap from RKH, to allow this allocator to show increased diligence and alignment. |
Follow up on the issues you mentioned, thanks for reviewing! |
DataCap has been refilled. |
Latest Compliance Report: https://compliance.allocator.tech/report/f03014732/1727222529/report.md
Previous Compliance Review Comments: #99
Datacap continues to be assigned to two existing clients
hash889900/HashTeam#3
hash889900/HashTeam#8
Generates CID reports on an ongoing basis and asks additional questions based on the generated reports.
I found that the retrieval rate plummeted a few days ago, and when I asked why, the customers answered that the problem was caused by a program failure on SPARK's side.
hash889900/HashTeam#8 (comment)
hash889900/HashTeam#3 (comment)
Based on a few days of follow-up, retrieval rates are now continuing to rise
The text was updated successfully, but these errors were encountered: