search

filecoin-project / Allocator-Governance

7 stars 35 forks source link

Community Review of TopBlocks #177

Closed woshidama323 closed 2 weeks ago

woshidama323 commented 1 month ago

Latest Compliance Report:https://compliance.allocator.tech/report/f03019931/1727395347/report.md

example 1:https://github.com/filplus-bookkeeping/TopBlocks/issues/10

Retrievals and data distribution data look good

image

If you have any other questions, please leave a comment, thank you!

filecoin-watchdog commented 1 month ago

Allocator Application Compliance Report

Examle 1 The dataset this client proposes seems to be already stored on filecoin: github search results The allocator should’ve asked why the client wanted to store another replica. After no response from the client, the allocator decided to close the issue.

Example 2 This client seems to have data similar to the client in Example 1. It also covers Allen Institute files. This leads to a similar conclusion that this data was already stored on the filecoin system.

4 out of 14 SPs have a retrieval rate of 0%, other 10 oscilate between 49-92%. CID sharing has been observed. Even if it’s not a direct violation of the system, that might result from preparing the exact same dataset. Either way, gov team should follow up.

woshidama323 commented 1 month ago

Thanks for your review

Examle 1 The dataset this client proposes seems to be already stored on filecoin: github search results The allocator should’ve asked why the client wanted to store another replica. After no response from the client, the allocator decided to close the issue.

You can see that all the datasets have expired on filecoin, and also as I know, they have not been restored at the moment So, from my point of view, I think this is fair.

After no response from the client, the allocator decided to close the issue. Since there is no response from the client at Slack, GitHub. etc, We need to move on instead of waiting again and again you can see we also left enough time for client handling but still no response.

Example 2 This client seems to have data similar to the client in Example 1. It also covers Allen Institute files. This leads to a similar conclusion that this data was already stored on the filecoin system.

Same as Example 1

4 out of 14 SPs have a retrieval rate of 0%, other 10 operate between 49-92%. image They've taken action for that, Some boost deploying issues blocked them,

As for CID sharing, I have asked them for reasons. image

The path of onboarding is not always smooth, but we are doing our utmost to complete the tasks. We look forward to your response.

galen-mcandrew commented 1 month ago

According the compliance report, this team has primarily worked with only one client (4.87PiB). As noted, checking this client database and searching AllenInstitute reveals some duplicates on the network. I would love some more details or evidence of the investigation that showed these other datasets as expired. Can you show the dashboard, explorer, or tools you used to determine those other clients were not active? Development of tools and process for that investigation could help other allocators and data-prep teams to quickly determine if a dataset is redundant.

Overall we see evidence of mixed compliance, with the allocator investigating and intervening with clients, but most of this allocator's history is with that sole client. Going forwards, we hope that the allocator continues to intervene quickly and build trust over time with clients. We will request an additional 5PiB of DataCap from RKH, to allow this allocator to show increased diligence and alignment.

Kevin-FF-USA commented 2 weeks ago

DataCap has been refilled. https://datacapstats.io/notaries/f03019931