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

Community Review of TopBlocks #177

Closed
woshidama323 opened this issue Sep 27, 2024 · 4 comments
Closed

Community Review of TopBlocks #177

woshidama323 opened this issue Sep 27, 2024 · 4 comments
Assignees
Labels
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

Comments

@woshidama323
Copy link

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

example 1:filplus-bookkeeping/TopBlocks#10

Retrievals and data distribution data look good
image

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

@Kevin-FF-USA Kevin-FF-USA self-assigned this Sep 30, 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. labels Sep 30, 2024
@filecoin-watchdog
Copy link
Collaborator

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.

@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 Awaiting Response from Allocator If there is a question that was raised in the issue that requires comment before moving forward. and removed 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 labels Oct 2, 2024
@woshidama323
Copy link
Author

woshidama323 commented Oct 8, 2024

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.

@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 and removed Awaiting Response from Allocator If there is a question that was raised in the issue that requires comment before moving forward. labels Oct 8, 2024
@galen-mcandrew
Copy link
Collaborator

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
Copy link
Collaborator

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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
Projects
None yet
Development

No branches or pull requests

4 participants