-
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
2nd Community Diligence Review of Greater Heat Allocator #130
Comments
One additional note: All DataCap has been distributed, but 5PiBs of DataCap has not been used in deals yet. Perhaps its better to complete a review when 75% usage is reached cc @galen-mcandrew |
Thank you for your patience in reviewing this. Regarding the first issue: Data storage depends on various factors, such as storage plans, data preparation, DC quotas, technical integration, and Filecoin collateral, all of which need to be adapted individually. The STFIL crisis in March-April this year led many SPs, who originally planned to proceed with data sealing, to temporarily suspend their plans. The borrowing of collateral and the large amount of self-held Filecoin collateral significantly affected the sealing process of SPs. Therefore, it is entirely understandable that SPs may need to make updates during the actual data storage process. At the same time, clients disclose information about the SPs they are communicating with in a timely manner during the application process; if updates are not provided in a timely manner, GreaterHeat also requests further explanations. Detailed records can be found as follows: Regarding the second issue: Each allocator has its own allocation rules. Although clients may not promptly disclose information related to data preparation in their application, GreaterHeat, as an allocator, has conducted further inquiries about data preparation methods in the comment updates. Please see the details below: The inquiry method we used was also inspired by the official due diligence process in the V4 LDN model. However, as noted in the latest issue published by Kevzak: #125, the governance team encountered certain limitations during the review process. We have actively left comments, and as stated in the comments, while compliance verification of data preparation details can be appropriately due-diligenced, the role of the allocator requires a better balance between the convenience of client data onboarding and the effective increase in SPs' computing power. We believe that overly stringent and overly lenient due diligence are both detrimental to the development of the Filecoin ecosystem. Instead, entrusting the decision-making power to the allocator reflects the important role of the allocator. Regarding the third issue: We carefully reviewed the client’s official website, https://www.youle.com.sg/. As an early education institution, it continuously generates material such as daily teaching videos and children’s daily life videos. The application only includes a sample of this data. According to the original 580TiB of data, there will be some padding conversion rate when converting to CAR files. Based on the calculation, one backup corresponds to approximately 1PiB of data. If there are 10 backups, it aligns with the application for 10PiB. Finally, each allocator has its unique approval tendencies. As an allocator, GH focuses more on the Spark retrieval success rate of SPs. It is encouraging that, with our continuous requests, the Spark retrieval success rate of SPs is improving. Currently, SPs are still in the sealing process, and we will actively participate in governance meetings, hoping that the second recharge will receive 20PiB of DC support.Thank you very much! |
@galen-mcandrew @Kevin-FF-USA |
Given the details presented above and some additional investigation into these clients, we are seeing partial compliance. Specifically:
Given the overall status of this allocator, we are requesting a matched amount of 10PiB DataCap from RKH. @AlanGreaterheat Please verify that you will instruct, support, and require your clients to work with compliant storage providers. |
Thank you for @galen-mcandrew response. We will pay closer attention to the compliance of the allocator's operations in the future and execute its functions according to official requirements. For example:The Spark retrieval success rate continues to improve , KYC due diligence will be more rigorous and comprehensive,etc. |
DataCap issued: https://filecoinpulse.pages.dev/allocator/f03010601/#pageparamsallocator_id |
Link to First Review
Latest Allocator Report: https://compliance.allocator.tech/report/f03010601/1723594199/report.md
Allocator received 10PiBs additional allocation.
DataCap awarded to:
4PIBs AlanGreaterheat/Greaterheat-Allocator#9
1PiB AlanGreaterheat/Greaterheat-Allocator#11
4PiBs AlanGreaterheat/Greaterheat-Allocator#7
1PiB AlanGreaterheat/Greaterheat-Allocator#15
There are three points across the applications:
5 SPs not on original application SP lists have taken 60% (6PiBs) of new DataCap across the 4 clients.
Across all 4 applications, there is no detail on data preparation, all questions in the applications are left blank. 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. See list of questions:
The text was updated successfully, but these errors were encountered: