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 QC Data Center Allocator #140

Closed
filecoin-watchdog opened this issue Aug 20, 2024 · 5 comments
Closed

Community Review of QC Data Center Allocator #140

filecoin-watchdog opened this issue Aug 20, 2024 · 5 comments
Assignees
Labels
Refresh Applications received from existing Allocators for a refresh of DataCap allowance

Comments

@filecoin-watchdog
Copy link
Collaborator

filecoin-watchdog commented Aug 20, 2024

Latest Compliance Report: https://compliance.allocator.tech/report/f03014608/1724113222/report.md

luhong123/QC-Data-center#3

One client over 4 allocations

KYC exists

Retrievals look good for SP and distribution looks good

There is no detail on data preparation, all questions in the applications are left blank and answers from client in comments are vague. I'd challenge the allocator to push for more details and demonstrate proof of how dataset is prepared and documented and how the client can actually retrieve the open files.

@Kevin-FF-USA Kevin-FF-USA self-assigned this Aug 21, 2024
@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 Refresh Applications received from existing Allocators for a refresh of DataCap allowance labels Aug 21, 2024
@luhong123
Copy link

This is the method or tool they use to prepare the data
luhong123/QC-Data-center#3 (comment)
image

@luhong123
Copy link

Here's some pre-trigger questions
luhong123/QC-Data-center#3 (comment)
image

After seeing that spark retrieval is supported, I will manually fetch the data to verify that
The method used is as follows
Using the client's wallet, look up a random deal id
image
`lotus state get-deal 88223805
{
"Proposal": {
"PieceCID": {
"/": "baga6ea4seaqmydui7nxqovgaodc2bizhkmnzndtkmnvd7sjxjbqyfct5ngoh2fa"
},
"PieceSize": 34359738368,
"VerifiedDeal": true,
"Client": "f03155630",
"Provider": "f03166668",
"Label": "bafybeihvng7qrwaegy6yzx3kr5c6wpbzxs3kcj7tdcejspzo2c4qviu7de",
"StartEpoch": 4173526,
"EndEpoch": 5699926,
"StoragePricePerEpoch": "0",
"ProviderCollateral": "6320280705102388",
"ClientCollateral": "0"
},
"State": {
"SectorNumber": 4615,
"SectorStartEpoch": 4154137,
"LastUpdatedEpoch": -1,
"SlashEpoch": -1
}
}

and than
lotus client retrieve --miner f03166668 bafybeihvng7qrwaegy6yzx3kr5c6wpbzxs3kcj7tdcejspzo2c4qviu7de /tmp/QC/

The data will appear in /tmp/QC/ after the fetch, and then the comparison is performed

By the way, lotus no longer has the client command in version 1.28.2. Still exists in 1.26.2

@galen-mcandrew
Copy link
Collaborator

Flagging something for allocator to follow-up on with their client: In their first application they claim to be the dataset owner, however in a subsequent application to a different allocator they claim to be a data preparer. This may be accurate, owning one set of data and having official authorization to represent the company (https://www.yimiaohb.net/), while also acting as a data preparer for another publicly available dataset.

Additionally, while there is some SP distribution, the ISPs in US appear to be VPNs, which could mean distribution limited to HK and CN. The allocator application states "require customers to provide the real address of sp and related materials" (question 28).

@luhong123 You should direct these additional questions to your client. As a reminder, the allocator team is responsible for verifying, supporting, and intervening with their clients. If a client is NOT providing accurate deal-making info (such as incomplete or inaccurate SP details) or making deals with noncompliant unretrievable SPs, then the allocator needs to intervene and require client updates before more DataCap should be awarded.

Please verify that you will instruct, support, and require your clients to work with retrievable storage providers. Please reply here with acknowledgement and any additional details for our review.

Given the diligence evidence and retrieval we are seeing, we are requesting an additional 5 PiB of DataCap from RKH to support this allocator increasing their diligence and alignment.

@luhong123
Copy link

@galen-mcandrew Thank you for pointing this out and I will follow up!

Additionally, while there is some SP distribution, the ISPs in US appear to be VPNs, which could mean distribution limited to HK and CN. The allocator application states "require customers to provide the real address of sp and related materials" (filecoin-project/notary-governance#1071 (comment)).

I've noticed this, too.So also the geo-location confirmation for the SP in the US group, and they sent a utility bill for me to confirm, and here's my comment at the time

Because this is the customer's private documents, can not be published here, if necessary, you can leave your e-mail, I will send later!

image

@Kevin-FF-USA
Copy link
Collaborator

@galen-mcandrew galen-mcandrew removed the Diligence Audit in Process Governance team is reviewing the DataCap distributions and verifying the deals were within standards label Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Refresh Applications received from existing Allocators for a refresh of DataCap allowance
Projects
None yet
Development

No branches or pull requests

4 participants