filecoin-project / Allocator-Governance

7 stars 34 forks source link

Community Diligence Review of Bewell Technology Limited Allocator #10

Closed filecoin-watchdog closed 3 months ago

filecoin-watchdog commented 5 months ago

Review of Top Value Allocations from @Aaron01230 Allocator Application: https://github.com/filecoin-project/notary-governance/issues/992

First example: DataCap was given to: https://github.com/filplus-bookkeeping/Bewell-Technology-Limited/issues/1 Public Open Dataset - key compliance requirement: Retrievability

1st point) Allocation schedule unclear of the details in allocator application notes to do a comparison but the allocator awarded this client three times with 500TiB, 1PiB, 2PiB

2nd point) No sign of KYC or KYB of client or dataset as mentioned in allocator application. Questions were asked about previous applications in LDN and also data preparation

3rd point) Client said these were the SPs, no entity, no location. No comment from Allocator about this f02945258 f02941878 f02941888 f02941882 f02941891 f02941885 f02941886
f02945259 f02950965 f02830476 f02830451

Actual data storage report: https://check.allocator.tech/report/filplus-bookkeeping/Bewell-Technology-Limited/issues/1/1715264125065.md

Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals f03028326 | Shenzhen, Guangdong, CNCTGNet | 325.56 TiB | 14.43% | 325.56 TiB | 0.00% f02830476 | Shenzhen, Guangdong, CNCTGNet | 93.50 TiB | 4.14% | 93.50 TiB | 0.00% f03071472 | Hong Kong, Hong Kong, HKHong Kong Beecloud System Technology Services Limited | 400.41 TiB | 17.74% | 400.41 TiB | 0.00% f03028321 | Hong Kong, Hong Kong, HKHong Kong Beecloud System Technology Services Limited | 285.88 TiB | 12.67% | 285.88 TiB | 0.00% f03028315 | Hong Kong, Hong Kong, HKHong Kong Beecloud System Technology Services Limited | 285.84 TiB | 12.67% | 285.84 TiB | 0.00% f03028310 | Hong Kong, Hong Kong, HKHong Kong Beecloud System Technology Services Limited | 284.78 TiB | 12.62% | 284.78 TiB | 0.00% f03028318 | Hong Kong, Hong Kong, HKHong Kong Beecloud System Technology Services Limited | 270.69 TiB | 11.99% | 270.69 TiB | 0.00% f03028325 | Hong Kong, Hong Kong, HKHong Kong Beecloud System Technology Services Limited | 267.16 TiB | 11.84% | 267.13 TiB | 0.01% f01943663 | Hong Kong, Hong Kong, HKHong Kong Beecloud System Technology Services Limited | 34.50 TiB | 1.53% | 34.50 TiB | 0.00% f01928097 | Hong Kong, Hong Kong, HKHong Kong Beecloud System Technology Services Limited | 8.38 TiB | 0.37% | 8.38 TiB | 0.00%

One SP IDs taking deals matches per report. All others were not reported and with unknown details. Looks to be centrailzed in one location , but additional diligence needed to confirm entity and actual storage locations

3rd point) Second, third allocation awarded to this client. However, per Spark dashboard, all SPs are either not available or have 0% retrievability.

The Allocator showed no sign of diligence after 1st allocation and gave the 2nd, 3rd allocation of 3.6PiB to the client.

filecoin-watchdog commented 5 months ago

Second example: DataCap was given to: https://github.com/filplus-bookkeeping/Bewell-Technology-Limited/issues/3 Public Open Dataset - key compliance requirement: Retrievability

1st point) No client KYC or KYB. Allocator asked for KYC after two allocation (1PiB) given. Response was an email screenshot. https://github.com/filplus-bookkeeping/Bewell-Technology-Limited/issues/3#issuecomment-2094644505. Does not match what was said was diligence in application of allocator

2nd point) SPs listed in client application: f02850067 fo2830476 fo2941888 fo2950965 fo2830451

report listing SPs taking deals: https://check.allocator.tech/report/filplus-bookkeeping/Bewell-Technology-Limited/issues/3/1715264582659.md

Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals f02830476 | Shenzhen, Guangdong, CNCTGNet | 12.97 TiB | 1.32% | 12.97 TiB | 0.00% f03028325 | Hong Kong, Hong Kong, HKHong Kong Beecloud System Technology Services Limited | 195.31 TiB | 19.94% | 195.31 TiB | 0.00% f03028315 | Hong Kong, Hong Kong, HKHong Kong Beecloud System Technology Services Limited | 195.31 TiB | 19.94% | 195.31 TiB | 0.00% f03028318 | Hong Kong, Hong Kong, HKHong Kong Beecloud System Technology Services Limited | 195.31 TiB | 19.94% | 195.31 TiB | 0.00% f03028321 | Hong Kong, Hong Kong, HKHong Kong Beecloud System Technology Services Limited | 195.28 TiB | 19.93% | 195.28 TiB | 0.00% f03028310 | Hong Kong, Hong Kong, HKHong Kong Beecloud System Technology Services Limited | 173.03 TiB | 17.66% | 173.03 TiB | 0.00% f01928097 | Hong Kong, Hong Kong, HKHong Kong Beecloud System Technology Services Limited | 12.47 TiB | 1.27% | 12.47 TiB | 0.00%

One SP matches from original list, and is storing 1%. All others unknown, need more diligence to verify location and entity

3rd point) Second allocation awarded to this client. However, per Spark dashboard, all SPs are either not available or have 0% retrievability.

The Allocator showed no sign of diligence after 1st allocation and gave the 2nd, total 1PiB allocated.

filecoin-watchdog commented 5 months ago

Interesting note: Exact same set of unknown SPs used on both applications with no retrievability.

Kevin-FF-USA commented 4 months ago

Hi @Aaron01230

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 https://github.com/filecoin-project/Allocator-Governance/issues/10.

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

image

galen-mcandrew commented 4 months ago

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

Specifically:

Given these details, this allocator will not receive a subsequent allocation request to the root key holders at this time.

Aaron01230 commented 4 months ago

Sorry, we have been busy with other things recently and have not paid attention to this. We have communicated with SPs and they do not support Spark retrieval because they use Venus service for packaging. They will support HTTP retrieval in the future.