Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2nd Community Review of Bitengine-Reeta Allocator #221

Open
Bitengine-reeta opened this issue Nov 7, 2024 · 1 comment
Open

2nd Community Review of Bitengine-Reeta Allocator #221

Bitengine-reeta opened this issue Nov 7, 2024 · 1 comment
Assignees
Labels
Awaiting Response from Allocator If there is a question that was raised in the issue that requires comment before moving forward. Refresh Applications received from existing Allocators for a refresh of DataCap allowance

Comments

@Bitengine-reeta
Copy link

Latest report:https://compliance.allocator.tech/report/f03014781/1730765561/report.md

Currently, a total of 5 clients have applied to us, of which 1 is a public dataset and 4 are enterprise datasets (2 have been approved and the other 2 are still under communication).
image

The average Spark search success rate is 47%, which is a medium level. The main reason is that some customers use the DDO model. In the future, we plan to reduce or stop cooperation with customers who use the DDO order model. For customers with low Spark search rates, our technical team is also helping customers improve the Spark search success rate. We look forward to our continued improvement in the future.

@Kevin-FF-USA Kevin-FF-USA self-assigned this Nov 7, 2024
@Kevin-FF-USA Kevin-FF-USA added the Awaiting Governance/Watchdog Comment DataCap Refresh requests awaiting a public verification of the metrics outlined in Allocator App. label Nov 7, 2024
@filecoin-watchdog
Copy link
Collaborator

@Bitengine-reeta
Allocator Application
Compliance Report
1st Review
1st Review score: 5PiB

5 PiB granted to existing clients:

Client Name DC status
NOAA 2PiB Existing
BeijingMipai Culture Media 2PiB Existing
JuQing Media 0.5PiB New
sxqiaonao 0.2PiB New

NOAA

  • SPs list updated in this round:
    f03055005 HK Chris
    f01315096 HK Chris
    f03091739 USA Lanxin
    f03156617 Australia Tongkun
    f03148356 Japan Linyun
    f01106668 HK Chris
    f03144037 South Korea Cary
    f0870558 HK Chris
    f03151456 HTY Shenzhen
    f03055018 Chris HK
    f01889668 Mike US
    f03151449 HTY Shenzhen
    f01518369 Mike US
    f03179570 YunSD Singapore
    f03055029 Chris HK
    f03188440 Fei Vancouver, Canada
    f03190614 Laibin Dubai
    f03190616 YM Japan
    f03066836 、
    f03081958

  • SPs list used for deals:
    f03055005
    f0870558
    f01315096
    f01106668
    f03055029
    f03055018
    f03091739
    f03091738
    f03074589
    f03074586
    f03074587
    f03074583
    f02199999
    f03156617
    f03148356
    f03144037
    f01518369
    f01889668

  • 6SPs don’t match provided list

  • 8 out of 18 SPs have retrieval rate of 0%.

BeijingMipai Culture Media

  • In this round, the client updated 22 SPs (top 10 match the previous allocation). Most SPs out of the following list were used for deals (except f03151456 and f0317957):
    f01106668 Hong Kong, Hong Kong, HK
    f0870558 Hong Kong, Hong Kong, HK
    f03091739 Dallas, Texas, US
    f03091738 Dallas, Texas, US
    f03074589 Hong Kong, Hong Kong, HK
    f03074587 Seoul, Seoul, KR
    f02199999 Singapore, Singapore, SG
    f03144037 Paripark, Seoul, KR
    f03156617 Sydney, New South Wales, AU
    f03148356 Ōi, Saitama, JP
    f01518369 US
    f01889668 US
    f03055018 Hong Kong
    f03055029 Hong Kong
    f02013352 Hong Kong
    f03151449 CN,Shenzhen HTY
    f03151456 CN,Shenzhen HTY
    f0317957 Singapore, Singapore YunSD
    f03178077 JP,Tokyo Gong
    f03178144 JP,Tokyo Gong
    f03179572 US Flycloud
    f03214937 US Flycloud

  • 20 new SPs were used to make deals(total 30). List of added SPs:
    f03179570
    f03178077
    f03179572
    f03178144
    f03214937
    f03229933
    f03229932
    f03055029
    f03055018
    f03055005
    f01315096
    f03151449
    f03188440
    f03173127
    f02013352
    f01928097
    f03190614
    f03190616
    f01518369
    f01889668

  • 10 newly added SPs don’t match updated list.

  • 10 SPs have retrieval rate of 0%, 8 SPs have retrieval of >75%, and the rest have retrieval below the acceptable level.

  • The client declared 6 replicas, while there are already 9.

JuQing Media

  • The client said they applied for DC in behalf of their clients. Could that be explained more?
  • The client said:

“Initial storage will be on Filecoin. Future data storage plans: We will be launching in the next two weeks.”

What does it mean? Initial storage on filecoin and what after that?

  • Why did the allocator grant 500TiB in the first allocation? What's the allocation schedule here?
  • the client sealed around 20% of DC so far, and the report shows all of data was sealed with one SP and retrieval rate of it is at 34%

sxqiaonao

  • SPs list provided in the form:
    SP ID:f03091738 Location:US
    SP ID:f02199999 Location:Singapore
    SP ID:f03074583 Location:Japan
    SP ID:f03000070 Location:China
  • This data was already stored on the filecoin: [DataCap Application] Qiaonao Enterprise Management - Course Data filecoin-plus-large-datasets#975 What is the reason for store it again?
  • KYC was not completed from my perspective. The client said someone else has passes it previously. That’s not the best explanation.
  • the client sealed around 25% of DC so far, and the report shows all of data was sealed with one SP and retrieval rate of it is at 18%
  • the only SP used for the deals doesn’t match the provided SPs list (f03179572).
  • Why did the allocator grant 200TiB in the first allocation? What's the allocation schedule here?

@filecoin-watchdog filecoin-watchdog added Awaiting Response from Allocator If there is a question that was raised in the issue that requires comment before moving forward. Refresh Applications received from existing Allocators for a refresh of DataCap allowance and removed Awaiting Governance/Watchdog Comment DataCap Refresh requests awaiting a public verification of the metrics outlined in Allocator App. labels Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Response from Allocator If there is a question that was raised in the issue that requires comment before moving forward. Refresh Applications received from existing Allocators for a refresh of DataCap allowance
Projects
None yet
Development

No branches or pull requests

3 participants