Community Review of ZCFIL+

[zcfil]

Latest Compliance Report:https://compliance.allocator.tech/report/f03014659/1725840012/report.md

example 1:zcfil/ZCFIL#3
example 2:zcfil/ZCFIL#6

KYC exists
zcfil/ZCFIL#6 (comment)

Retrievals look good for SP and distribution looks good

sp not in China have provided relevant documents to confirm geographic location

If you have any other questions, please leave a comment, thank you!

[filecoin-watchdog]

Allocator Application
Compliance Report

Example 1
According to the allocator application, the first tranche should be 5% DC or 50% weekly allocation, so for this client it should be 350TiB, why the decision to reduce it to 200 TiB?

Currently the retrieval rate of all SPs is around 50%, has the allocator clarified this issue with the client?

Example 2
According to the allocator application, the first tranche should be 5% DC or 50% weekly allocation, so for this client it should be 500TiB, why the decision to reduce it to 200 TiB?

1 out of 7 SPs has retrieval rate over 75%.
1 out of 7 SPs seems to not support Spark retrieval measure.
5 out of 7 SPs have retrieval rate around 50%.
Has the allocator clarified this issue with the client?

note to review - the specification of the amount of the first tranche results from the analysis of the allocator's application and is not a criticism of its amount, but an indication of an inaccuracy.

The allocator clearly documents communication with the client, generates CID reports on an ongoing basis and asks additional questions based on the generated reports.

[zcfil]

note to review - the specification of the amount of the first tranche results from the analysis of the allocator's application and is not a criticism of its amount, but an indication of an inaccuracy.

Regarding this issue, stemming from the meeting and the practice of other notaries, I have decided that for the first round I will issue 50TiB-200TiB datacap for data validation according to the information requested by the client, which has prevented abuses.
I'll mention this before and after the trigger

I'm also keeping an eye on the spark channel regarding the drop in retrieval rates
Significant drop in retrieval rate due to a crash in spark's internal program
Here's a transcript of mike's communication with them

It is possible to view previous reports where SPs have maintained high retrieval rates until issues with spark arose that caused a significant drop in retrieval rates

[zcfil]

1 out of 7 SPs seems to not support Spark retrieval measure.

Probably talking about this SP

But with the previous report, I was able to see the retrieval rate, so maybe it was caused by a glitch in SPARK?

[galen-mcandrew]

The compliance report and the above details are good evidence for this pathway. A quick review of the two clients that are working with this allocator reveal that there may be either duplicate datasets or duplicate clients applying to multiple allocators.

I would encourage this allocator to review this information and request some more clarification from their clients before proceeding with subsequent allocations. Checking this client database and searching FengwoExtraordinary & AllenInstitute revealed a total of 7 client ID's.

In the meantime, given the evidence of initial diligence and good deal-making, we will request an additional 5PiB of DataCap from RKH, to allow this allocator to show increased diligence and alignment.

[Kevin-FF-USA]

DataCap was refilled.
https://datacapstats.io/notaries/f03014659