[DataCap Refresh] 3rd Review of IPFS Force

[ipfsforcezuofu]

Basic info

1. Type of allocator: manual

2. Paste your JSON number: 1034

3. Allocator verification: yes

4. [Allocator Application]Notary Allocator Application for IPFS Force notary-governance#1034
5. [Compliance Report] https://compliance.allocator.tech/report/f03019856/1735613441/report.md

6. Previous reviews

• [1st review]Community Review of IPFS Force Allocator #168 Outcome: 5 PiB
• [2nd review]2nd Community Review of IPFS Force Allocator #229 Outcome: 5 PiB

Current allocation distribution

Client name	DC granted
FileDrive	0.3 PiB
Duitang	3.84 PiB
Xuanti	0.2 PiB

I. FileDrive ipfsforcezuofu/ipfsforce-allocator#15

• DC requested: 4 PiB
• DC granted so far: 1.95 PiB

II. Dataset Completion

https://registry.opendata.aws/smithsonian-open-access/

III. Does the list of SPs provided and updated in the issue match the list of SPs used for deals?

yes

IV. How many replicas has the client declared vs how many been made so far:

5 vs 2 41%
5 vs 3. 40%
5 vs 4 19%

V. Please provide a list of SPs used for deals and their retrieval rates

SP ID	% retrieval	Meet the >75% retrieval?
f03229933	1.97	NO
f03179570	0.09	NO
f03229932	2.36	NO

I. Duitang ipfsforcezuofu/ipfsforce-allocator#30

• DC requested: 10 PiB
• DC granted so far: 6.71 PiB

II. Dataset Completion

https://www.duitang.com/blog/?id=1221808369
https://www.duitang.com/blog/?id=939087415
https://www.duitang.com/blog/?id=1516930252

III. Does the list of SPs provided and updated in the issue match the list of SPs used for deals?

yes
IV. How many replicas has the client declared vs how many been made so far:

5 vs 1. 6%
5 vs 2 10%
5 vs 3 2%
5 vs 4 23%
5 vs 5 6%
5 vs 6 2%
5 vs 7 15%
5 vs 8 10%
5 vs 9 26%

V. Please provide a list of SPs used for deals and their retrieval rates

SP ID	% retrieval	Meet the >75% retrieval?
f03187925	90	YES
f03157902	90	YES
f03136895	36	NO
f03224828	59	NO

I. Shanghai Xuanti ipfsforcezuofu/ipfsforce-allocator#37

• DC requested: 12 PiB
• DC granted so far: 0.2 PiB

II. Dataset Completion

https://www.leisu.com/news/view-226501
https://www.leisu.com/data/zuqiu/comp-120/data
https://www.leisu.com/news/view-226228
https://www.leisu.com/news/view-226491

III. Does the list of SPs provided and updated in the issue match the list of SPs used for deals?

yes

IV. How many replicas has the client declared vs how many been made so far:

5 vs 3 5%
5 vs 4 94%

V. Please provide a list of SPs used for deals and their retrieval rates

SP ID	% retrieval	Meet the >75% retrieval?
f01807908	91	YES
f03090976	2	NO
f03224648	90	YES
f01927410	83	YES

Allocation summary

7. Notes from the Allocator

The number of replicas requested by the allocator is too high for clients to meet. We are exploring the possibility of adjusting it to make it more flexible, particularly during periods of high gas fees.

8. Did the allocator report up to date any issues or discrepancies that occurred during the application processing?

Yes

9. What steps have been taken to minimize unfair or risky practices in the allocation process?

Inform the client about the pauses in DC assignment during the DC refresh.

10. How did these distributions add value to the Filecoin ecosystem?

Adjust the DC assignment based on the clients' performance and demand.

11. Please confirm that you have maintained the standards set forward in your application for each disbursement issued to clients and that you understand the Fil+ guidelines set forward in your application

Yes

12. Please confirm that you understand that by submitting this Github request, you will receive a diligence review that will require you to return to this issue to provide updates.

Yes

[filecoin-watchdog]

@ipfsforcezuofu
FileDrive 1.95PiB / 4PiB

• requirements regarding replicas (+5 required) vs 4
• F03229933, f03214937, f03178144, F03229932, f02984331 All VPN
• Low retrieval on most of SP’s,
• Owner of this dataset is not FileDrive but Smithsonian Institute, preparation of the dataset is not well described.
• Allocator stated that he is halting future distribution until performance will increase that is a good approach, but further clarifications should also happen

Duitang - 6.72PiB / 10PiB

• exceeded max application allowed per client under allocator application (5PiB)
• The number of replicas continues to rise, reaching nine as of today vs 4 original. This concern was previously raised by the allocation team and attributed to the onboarding of new Storage Providers to replace old one’s.
• Currently, eight out of the nine SPs are using VPNs.
• The preparation process lacks clarity, and there is no clear specification of what the dataset contains.
• This client gets DC from 2 other allocators at the same time: FilscanOfficial – 10 PiB Venus Pathway-VFDA – 5 PiB
  While it is claimed that each dataset contains unique wallpapers, the requested DataCap (DC) amounts make this assertion highly questionable. Suspicion of storing same dataset. The gov team should follow up.

Shanghai Xuanti 200TiB / 12PiB

• Target allocation exceeded max possible on allocator
• Only one SP is NOT using a VPN.
• The data preparation step, as in both previous clients, is not described.
• While Shanghai Xuanti Information Technology Co., Ltd. produces and owns much of the content on leisu.com, some media, such as live broadcasts, images, or data, may originate from third-party sources.
• Not compliant with own requirements of +5 sp’s
• This client is getting DC from another allocator for the same dataset: FileDrive

[ipfsforcezuofu]

@filecoin-watchdog
Thank you for pointing out those potential issues. I will follow up with the clients and get back to you shortly.

[ipfsforcezuofu]

@filecoin-watchdog

One client, Duitan, has checked with the SPs regarding the VPN issue and found that they are facing challenges in verifying whether SPs are using VPN services. Could you suggest appropriate tools and/or standards for this verification? Thank you.

Please refer to the client's comments here:
ipfsforcezuofu/ipfsforce-allocator#30 (comment)

[filecoin-watchdog]

@ipfsforcezuofu
There is no single tool that is "the right one". However, I have checked several different tools and each one indicated a high probability of using a VPN. Hence the conclusion.

[ipfsforcezuofu]

@filecoin-watchdog

• Thank you, @filecoin-watchdog , for pointing out the common VPN issue and teaching us how to identify it. After communicating with clients, all SPs with VPN issues will be replaced with new ones. Although we remind our clients during the application process, we should continue conducting checks on our own. So I will also ensure thorough checks are conducted before approving new SPs and/or assigning new DC.

• Regarding the common concerns about exceeding the maximum DC application, or falling below the preset number of SPs or replicas, I believe the rules defined in my allocator application are too strict and may impact our service to clients. I previously raised this issue, and I believe the governance team might currently be working on a solution.

   https://filecoinproject.slack.com/archives/C06MTBZ44P2/p1730880804113299
  

Filedrive

• Low retrieval on most of SP’s,

We identified the problem promptly and paused new DataCap assignments. In alignment with the client, we will allocate a small amount of DataCap for testing in the next round.

• Owner of this dataset is not FileDrive but Smithsonian Institute, preparation of the dataset is not well described.

Please review the client’s feedback: “One of our core businesses is data preparation and processing. The dataset from Smithsonian is used because Smithsonian is one of our clients.”

• Allocator stated that he is halting future distribution until performance will increase that is a good approach, but further clarifications should also happen

Thank you for your reminding. Here is our followup:

Duitang

• The number of replicas continues to rise, reaching nine as of today vs 4 original. This concern was previously raised by the allocation team and attributed to the onboarding of new Storage Providers to replace old one’s.

• The preparation process lacks clarity, and there is no clear specification of what the dataset contains.

• This client gets DC from 2 other allocators at the same time:

I identified the issue and received the following feedback before:

I requested an explanation again after receiving the watchdog's comments.

Shanghai Xuanti 

• The data preparation step, as in both previous clients, is not described.

• While Shanghai Xuanti Information Technology Co., Ltd. produces and owns much of the content on leisu.com, some media, such as live broadcasts, images, or data, may originate from third-party sources.

• This client is getting DC from another allocator for the same dataset: [DataCap Application] <Shanghai Xuanti > filedrive-team/Filecoin-Plus-Pathway#21

[Kevin-FF-USA]

Hi @ipfsforcezuofu,

Thanks for submitting this application for refresh.
Wanted to send you a friendly update - as this works its way through the system you should see a comment from Galen on behalf of the Governance this week. If you have any questions or need support until then, please let us know.

Warmly,
-Kevin