Community Diligence Review of MetaEra Allocator

[filecoin-watchdog]

Review of MetaEra Allocations from @CockroachBoss
Allocator Application: filecoin-project/notary-governance#1029

First example:
DataCap was given to:
CockroachBoss/Allocator-MediaPlatformData#2

Public Open Dataset - key compliance requirement: Retrievability

1st point)
KYC question asked, and client claimed to send via direct message. This is something for gov team to follow up on to confirm.

2nd point)
Allocation schedule per allocator:
The first allocation will be 1/20 of the total application amount, and each allocation will be twice as much as the last time. Until the maximum single amount is 2p. The remaining rounds will continue to be distributed at 2p.
For example:
The client expected 10PiB datacap.
The first allocation will be 500TiB, the second allocation will be 1000TiB, third allocation: 2000TiB, fourth: 2000TiB, fifth: 2000TiB, six: 2000TiB, seven: 500TiB.

Actual allocation: 1PiB, 1PiB, 1PiB - this does not follow their guidelines

3rd point)
SPs provided by client:
f02211572 | Chengdu, Sichuan | MicroAnt
f02814600 | Chengdu, Sichuan| BigMax
f02226869 | Nanchang, Jiangxi | LuckyMine
f02274508 | Hong Kong | H&W
f02329119 | Hangzhou, Zhejiang | Cryptomage
f02837293 | Seoul, Seoul | FiveByte
f01159754 | Singapore, Singapore | VITACapital
f01852363 | Singapore, Singapore | HectorLi
f02321504 | Los Angeles, California | ipollo
f02320312 | Los Angeles, California | R1
f02327534 | Los Angeles, California | ipollo
f02322031 | Los Angeles, California | ipollo
f02320270 | Los Angeles, California | R1
f01853077 | Singapore, Singapore | Alpha100

https://check.allocator.tech/report/CockroachBoss/Allocator-MediaPlatformData/issues/2/1716390793865.md

Actual SPs taking deals
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals | Mean Spark Retrieval Success Rate 7d
f02956383 | Hong Kong, Hong Kong, HKANYUN INTERNET TECHNOLOGY (HK) CO.,LIMITED | 254.00 TiB | 10.67% | 254.00 TiB | 0.00% | -
f02826123 | Shenzhen, Guangdong, CNChina Mobile communications corporation | 131.16 TiB | 5.51% | 131.16 TiB | 0.00% | -
f02948413 | Chengdu, Sichuan, CNChina Mobile Communications Group Co., Ltd. | 258.72 TiB | 10.87% | 258.72 TiB | 0.00% | -
f03066382 | Chengdu, Sichuan, CNChina Mobile Communications Group Co., Ltd. | 193.25 TiB | 8.12% | 192.25 TiB | 0.52% | -
f03046248 | Hong Kong, Hong Kong, HKChina Unicom Global | 549.56 TiB | 23.09% | 549.56 TiB | 0.00% | -
f03079511 | Hong Kong, Hong Kong, HKChina Unicom Global | 239.09 TiB | 10.05% | 239.09 TiB | 0.00% | -
f02023435 | Hong Kong, Hong Kong, HKHK Broadband Network Ltd. | 35.91 TiB | 1.51% | 35.91 TiB | 0.00% | 78.86%
f03064819new | Seoul, Seoul, KRKorea Telecom | 539.53 TiB | 22.67% | 539.16 TiB | 0.07% | -
f02826234 | Singapore, Singapore, SGTencent Building, Kejizhongyi Avenue | 178.53 TiB | 7.50% | 140.88 TiB | 21.09% | -

No Sps match
No retrievals enabled, only one SP showing retrievals per Spark reports. Allocator made a comment about this fact, but still gave more DataCap to client.

[Kevin-FF-USA]

Hi @CockroachBoss

On the next Fil+ Allocator meeting we will be going over each refill application. Wanted to ensure you were tracking the review discussion taking place in #19.

If your schedule allows, recommend coming to the May 28th meeting to answer/discuss the issues raised in the recent distributions. This will allow you to faster address - or, the issue in Allocator Governance for ongoing written discussion.

Warmly,
-Kevin
https://calendar.google.com/calendar/embed?src=c_k1gkfoom17g0j8c6bam6uf43j0%40group.calendar.google.com&ctz=America%2FLos_Angeles

[galen-mcandrew]

Based on a further diligence review, this allocator pathway is partially in compliance with their application.

Specifically:

• Mixed evidence of diligence with clients (no verification of client claims)
• Allocations did not match tranche schedule (not scaling trust over time)
• Subsequent allocations given despite noncompliant client deal-making, with minimal allocator intervention through comments
• No retrievability for datasets, despite claims of public open data by both allocator and client (not showing distributed network data storage utility)

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 2.5PiB of DataCap from RKH, to allow this allocator to show increased diligence and alignment.

@CockroachBoss 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.

[galen-mcandrew]

Regarding the client due diligence claims above: if there is nothing public in your bookkeeping repo, then there is nothing for the governance team or others to review and assess diligence. We cannot track down and investigate disparate and scattered databases, spreadsheets, emails, and one-off communications channels to prove compliance. Per your application:

36. Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?:
    GitHub repo, Google spreadsheet

Regarding SP distribution and client-provided SP lists, again please refer to your own allocator application, specifically:

25. Do you require equal percentage distribution for your clients to their chosen SPs? Will you require preliminary SP distribution plans from the client before allocating any DataCap?:
    The allocation ratio of the customer's search SP does not need to be evenly distributed, and the maximum allocation of the customer's lead SP is allowed not to exceed 30%. Customers need to announce the SP of this round in advance before each round of distribution. Each round of packaging will be compared with the website https://datacapstats.io/ and recorded. If a customer has two consecutive rounds of discrepancies, the allocation will not proceed. Customers need to apply again, and the maximum amount for re-application is 1p. Until the 1p quota package meets the standards, you will not be allowed to apply for more quotas.

We are following through with the 2.5PiB and will reassess for greater compliance. In the meantime, I suggest you review your allocator application, as well as the stated client applications coming to your pathway.