Community Review of Bit Engine Reeta Allocator

[filecoin-watchdog]

Latest Allocator Report: https://compliance.allocator.tech/report/f03014781/1724112260/report.md

2 clients receiving allocations over several rounds.

Public Open Datasets - retrievals mixed, mostly 0% - no comments or diligence from allocator about retrievals

One client was NOAA replica. Client claims its good to have another copy.

The other was Dataset owner - KYB was asked for: filplus-bookkeeping/Bitengine-Reeta-Filplus#5 (comment)

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.

[Bitengine-reeta]

Spark search is a new search method. Many SPs use the Venus, Lotus and other modes to build nodes. Spark is not fully compatible with these modes, which still needs to be modified and adapted.
However, in general, most SPs have achieved a good search success rate. For the rest, I will actively contact the Client and SP to improve.

[Bitengine-reeta]

I have been urging the corresponding client to submit more detailed instructions and solve the retrieval problem.

[Bitengine-reeta]

Randomly retrieve a car file and decompress the car file to view its contents:

• Mipai Culture Media
  
• NOAA Re-forecast
  

[Bitengine-reeta]

Currently, the work of all SPs and Clients has been completed. We will continue to do a better job. We have applied for a second batch of 20PiB quota and hope to get support. Thank you.

[galen-mcandrew]

Based on a further diligence review, this allocator pathway is partially in compliance with filecoin-project/notary-governance#1015

Specifically:

• 27% avg retrievability rate of public open datasets
• High usage of VPNs without enforcing stated requirements from allocator application (hhttps://github.com/v5 Notary Allocator Application: Bitengine FIL+ Allocator notary-governance#1015 "we will ask clients to disclose all the information of Miner involved, including whether to use VPN"
• Noncompliant DataCap tranche allocations, second allocation of 1PiB
• Mixed KYC diligence into client claims, such as clients making conflicting region claims and lacking KYC checks in GitHub, with very minimal followup until the time this compliance review was opened ([DataCap Application] Mipai Culture Media - Portfolio Dataset  filplus-bookkeeping/Bitengine-Reeta-Filplus#5 (comment))

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.

Given this mixed review, we are requesting that the allocator verify that they will uphold all aspects & requirements of their initial application. If so, we will request an additional 5 PiB of DataCap from RKH, to allow this allocator to show increased diligence and alignment.

@Bitengine-reeta can you verify that you will enforce program and allocator requirements?
(for example: public diligence, tranche schedules, and public scale retrievability like Spark).

Please reply here with acknowledgement and any additional details for our review.

[Bitengine-reeta]

Thanks to the official team for their suggestions and guidance. We will continue to optimize and improve the issues mentioned by @galen-mcandrew .

• About SPARK retrieval
  Will continue to communicate with the Client, requiring the Client and SPs to continue to communicate, regularly track the adaptation of the Lotus and Venus programs, and gradually improve the Spark search success rate.
• About VPN
  The principle is to follow the FIL+ rules and eliminate VPN virtual IP locations. We will increase appropriate investigations and keep records.
• About allocation of DC
  Due to my negligence, I did not allocate 800TiB as required by the rules but directly allocated 1PiB. I apologize for this. In the future DC allocation work, I will pay close attention to this parameter value and operate cautiously and carefully.
• About Client KYC
  We will continue to improve the KYC process, especially the review of the qualifications and authenticity of the company. We will require the provision of relevant certificates and identity information, and for consideration of information confidentiality, the review will be conducted in the form of email.

In the following work, I will further improve the shortcomings of the past. Through continuous attempts and adjustments, my work output will be better. Thank you for your support.

[Kevin-FF-USA]

DataCap refreshed: https://filecoinpulse.pages.dev/allocator/f03014781/#pageparamsallocator_id
Closing issue