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

[DataCap Refresh] <1st> Review of <Tianji Studio Fil+> #268

Open
liyunzhi-666 opened this issue Jan 6, 2025 · 0 comments
Open

[DataCap Refresh] <1st> Review of <Tianji Studio Fil+> #268

liyunzhi-666 opened this issue Jan 6, 2025 · 0 comments
Assignees
Labels
Awaiting Governance/Watchdog Comment DataCap Refresh requests awaiting a public verification of the metrics outlined in Allocator App. Refresh Applications received from existing Allocators for a refresh of DataCap allowance

Comments

@liyunzhi-666
Copy link

liyunzhi-666 commented Jan 6, 2025

Basic info

  1. Type of allocator: [manual]
  1. Paste your JSON number: [1042]

  2. Allocator verification: [yes]

  1. Allocator Application
  2. Compliance Report

Current allocation distribution

Client name DC granted
Encyclopedia of DNA Elements 1.5 PiB
LAMOST DR8 public data 900 TiB
Aiyao 2.5 PiB

I. Encyclopedia of DNA Elements

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

II. Dataset Completion

https://registry.opendata.aws/encode-project/
https://www.encodeproject.org

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

Basic match. If there are additions or changes to the SPs, the client is updated in github.

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

10 vs 7

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

SP ID % retrieval Meet the >75% retrieval?
f03178144 80.79% YES
f03179572 62.62% NO
f03214937 46.79% NO
f03178077 82.50% YES
f03179570 37.88% NO
f0870558 67.58% NO
f03055018 93.67% YES
f01315096 92.11% YES
f03055005 57.46% NO
f03055029 95.41% YES
f01106668 95.00% YES
f03151456 65.19% NO
f03151449 68.98% NO

I. LAMOST DR8 public data(The client commitment to start deals soon)

  • DC requested: 10 PiB
  • DC granted so far: 900 TiB

I. Aiyao

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

II. Dataset Completion

liyunzhi-666/TianjiStudio-Fil#8 (comment)

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

Basic match. If there are additions or changes to the SPs, the client is updated in github.

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

10 vs 5

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

SP ID % retrieval Meet the >75% retrieval?
f03229933 29.22% NO
f03229932 34.83% NO
f03214937 47.40% NO
f03179570 41.87% NO
f03179572 60.78% NO
f03231121 0.00% NO
f03231117 0.00% NO

There are a few SPs's Spark retrieval success rate of 0. Client has updated the description in the comments.
image

Allocation summary

  1. Notes from the Allocator

When the Allocator finds that there is no significant improvement in the success rate of Spark retrieval for SPs working with Client,Allocator takes steps to limit the amount of Datacap approved.Allocator approves 1 PiB instead of approving 2 PiB.
image

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

Yes.The Allocator was malfunctioning during the last signing. An issue has been submitted and is waiting to be resolved by the official team.fidlabs/allocator-tooling#102

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

1.Regular checking. Check the client's application through the CID checker and when the report is unsatisfactory, take appropriate action to limit the approval.
2.Request more data samples from clients.
3.Request client for KYC review. For example, ask client to send document information to allocator official email for further approval.

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

1.Allocator encourages different types of datasets, including public datasets and enterprise open datasets.
2.Allocator is concerned about whether datasets are duplicated on the Filecoin network. Of course, if the client gives a valid reason, we generally adopt a policy of encouragement and tolerance, because it is true that, as the client said, many datasets may have been stored before but are now outdated, or in the case of cooperating SPs, it is the first time for them to store them.

  1. 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

  1. 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 filecoin-watchdog added Refresh Applications received from existing Allocators for a refresh of DataCap allowance Awaiting Governance/Watchdog Comment DataCap Refresh requests awaiting a public verification of the metrics outlined in Allocator App. labels Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Governance/Watchdog Comment DataCap Refresh requests awaiting a public verification of the metrics outlined in Allocator App. Refresh Applications received from existing Allocators for a refresh of DataCap allowance
Projects
None yet
Development

No branches or pull requests

3 participants