-
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
Community Review of QC Data Center Allocator #140
Comments
This is the method or tool they use to prepare the data |
Here's some pre-trigger questions After seeing that spark retrieval is supported, I will manually fetch the data to verify that and than 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 |
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. |
@galen-mcandrew Thank you for pointing this out and I will follow up!
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! |
DataCap refreshed: https://filecoinpulse.pages.dev/allocator/f03014608/#pageparamsallocator_id |
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.
The text was updated successfully, but these errors were encountered: