Closed alyssa32M closed 1 month ago
Application is waiting for allocator review
@luhong123 Dear allocator, this is my application. Please give us feedback. Thank you.
Please read the contents of https://github.com/filecoin-project/notary-governance/issues/1071#issuecomment-1902740577 for details on the rule, thank you!
If you don't need any help,Please pay a total of 101 FIL
to f1apw6of55wzdbpjpnnyenv56ensi4iisaxgmigzi
for information verification (1 FIL) and data pledge fees (100 FIL).
@luhong123 Dear allocator, we've read all contents you provided to me, thank you.
We've paid Fil to your account, please check it.
We are a web3 organization and I'm the op of our organization. Yes, we have stored this dataset in our servers. The sps in our application are ready for our deals. If we have more sps to cooperation, we will provide the update to you. Yes, we provided spark retrieval rules to sps and they have updated their code. We will keep focusing on their ability of retrieval.
f01843994 US
Please provide proof of the geographic location of the SPs to m4a1i233@gmail.com
@luhong123 OK. I have sent it.
confirmed
Total DataCap requested
5PiB
Expected weekly DataCap usage rate
1PiB
DataCap Amount - First Tranche
256TiB
Client address
f17h6wblshweb7uj4ijxkdroqsdjcl7qijjzi6n3i
f17h6wblshweb7uj4ijxkdroqsdjcl7qijjzi6n3i
256TiB
261c2300-e5ea-4d05-8290-e7a299df42dd
Application is ready to sign
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaceaomqclzsf6zpoihf7kalpli2klmacld2svrokzfxp3hu3qeskc2c
Address
f17h6wblshweb7uj4ijxkdroqsdjcl7qijjzi6n3i
Datacap Allocated
256TiB
Signer Address
f1apw6of55wzdbpjpnnyenv56ensi4iisaxgmigzi
Id
261c2300-e5ea-4d05-8290-e7a299df42dd
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceaomqclzsf6zpoihf7kalpli2klmacld2svrokzfxp3hu3qeskc2c
Application is Granted
Client used 75% of the allocated DataCap. Consider allocating next tranche.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 50.00% of Storage Providers have retrieval success rate less than 75%.
✔️ Data replication looks healthy.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger
[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...
Click here to view the CID Checker report.
Nice retrieval rate.
But it doesn't match what was first disclosed, so please confirm the SP you're working with and rework it!
@luhong123 Dear allocator, sorry for the late reply. When we were ready to distribute the data to the sp in our original plan, they were temporarily unable to help us with the packaging due to some update about their machines. We then contacted other sps that met the requirements to work with us first. We will continue to reach out to more sp's to get involved, and will make sure that the retrieval rate and the number of sps under the standard. We will give you the list as soon. Please give us a chance to improve our process and give us one more round of datacap. Thank you!
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 50.00% of Storage Providers have retrieval success rate less than 75%.
✔️ Data replication looks healthy.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger
[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...
Click here to view the CID Checker report.
Got it
Good retrieval rate, would like to see more SPs join in the next round with early disclosure
Application is in Refill
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacecegthi2l3zh77zwghfbrb5sd7f5cvfckl4aw5nynuz73h6vlvukq
Address
f17h6wblshweb7uj4ijxkdroqsdjcl7qijjzi6n3i
Datacap Allocated
512TiB
Signer Address
f1apw6of55wzdbpjpnnyenv56ensi4iisaxgmigzi
Id
1173ec9e-f87e-4c21-84da-7eed54f7976a
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecegthi2l3zh77zwghfbrb5sd7f5cvfckl4aw5nynuz73h6vlvukq
Application is Granted
checker:manualTrigger
⚠️ 1 storage providers sealed more than 50% of total datacap - f03161261: 53.75%
⚠️ 50.00% of Storage Providers have retrieval success rate less than 75%.
⚠️ 100.00% of deals are for data replicated across less than 3 storage providers.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger
[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...
Click here to view the CID Checker report.
@luhong123 Dear allocator, we provide several sps to our work. f03100002 SZ f01975299 China f03192503 HongKong f01084413 China f01084941 HongKong
Client used 75% of the allocated DataCap. Consider allocating next tranche.
checker:manualTrigger
⚠️ 2 storage providers sealed too much duplicate data - f03161261: 49.88%, f03189917: 49.89%
⚠️ 42.86% of Storage Providers have retrieval success rate equal to zero.
⚠️ 85.71% of Storage Providers have retrieval success rate less than 75%.
✔️ Data replication looks healthy.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger
[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...
Click here to view the CID Checker report.
checker:manualTrigger
⚠️ 2 storage providers sealed too much duplicate data - f03161261: 49.88%, f03189917: 49.89%
⚠️ 42.86% of Storage Providers have retrieval success rate equal to zero.
⚠️ 85.71% of Storage Providers have retrieval success rate less than 75%.
✔️ Data replication looks healthy.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger
[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...
Click here to view the CID Checker report.
@luhong123 Dear allocator, I noticed that the retrieval results for the new sps added to the list are not very good at the moment. I've already communicated with sps, and they promise to show better results in the next cid report. Also, I've got experience with previous sp's that I've worked with to share with new ones. Better results will be shown in subsequent reports.
(OLD vs NEW)
Please list the provider IDs and location of the storage providers you will be working with: f03100009 Hong Kong f01084941 Hong Kong f03100002 Shenzhen f03100000 Shenzhen f01975299 Shenzhen f01084413 Changsha f03161261 New York f03192503 Hong Kong f03189917 Dulles vs f02196792 HongKong f01843994 US f01392600 GZ f01270684 GD f01860256 HongKong State: ChangesRequested vs Granted
Got it
@luhong123 Dear allocator, I noticed that the retrieval results for the new sps added to the list are not very good at the moment. I've already communicated with sps, and they promise to show better results in the next cid report. Also, I've got experience with previous sp's that I've worked with to share with new ones. Better results will be shown in subsequent reports.
Number of replicas to store 4
The current number of copies is 8. Please confirm.
2 storage providers sealed too much duplicate data - f03161261: 49.88%, f03189917: 49.89%
Same bug. https://github.com/fidlabs/allocator-tooling/issues/73
Two retrievals are good so far, will be watching for changes in retrieval rates and hope to see good retrievals before the next round is triggered
Application is in Refill
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacectzxp4yvrv35ornckpza4f6pcyk7vt6wx2chm5nexkfxm4yjzcom
Address
f17h6wblshweb7uj4ijxkdroqsdjcl7qijjzi6n3i
Datacap Allocated
1PiB
Signer Address
f1apw6of55wzdbpjpnnyenv56ensi4iisaxgmigzi
Id
45001a57-53b3-4812-b122-9cc7af3e23ef
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacectzxp4yvrv35ornckpza4f6pcyk7vt6wx2chm5nexkfxm4yjzcom
Application is Granted
(OLD vs NEW)
Replicas: 8 vs 4 State: ChangesRequested vs Granted
checker:manualTrigger
⚠️ 2 storage providers sealed too much duplicate data - f03161261: 45.06%, f03189917: 41.37%
⚠️ 27.27% of Storage Providers have retrieval success rate equal to zero.
⚠️ 81.82% of Storage Providers have retrieval success rate less than 75%.
✔️ Data replication looks healthy.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger
[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...
Click here to view the CID Checker report.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 27.27% of Storage Providers have retrieval success rate equal to zero.
⚠️ 72.73% of Storage Providers have retrieval success rate less than 75%.
✔️ Data replication looks healthy.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger
[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...
Click here to view the CID Checker report.
Multiple occurrences of undisclosed SPs, although the retrieval rate is good, it violates the relevant rules, please give a reasonable explanation, or else consider suspending the distribution of datacap
Data Owner Name
NHGRI
Data Owner Country/Region
United States
Data Owner Industry
Life Science / Healthcare
Website
https://www.encodeproject.org/
Social Media Handle
Alyssa
Social Media Type
Slack
What is your role related to the dataset
Data Preparer
Total amount of DataCap being requested
5PiB
Expected size of single dataset (one copy)
1.32PiB
Number of replicas to store
8
Weekly allocation of DataCap requested
1PiB
On-chain address for first allocation
f17h6wblshweb7uj4ijxkdroqsdjcl7qijjzi6n3i
Data Type of Application
Public, Open Dataset (Research/Non-Profit)
Custom multisig
Identifier
No response
Share a brief history of your project and organization
Is this project associated with other projects/ecosystem stakeholders?
No
If answered yes, what are the other projects/ecosystem stakeholders
No response
Describe the data being stored onto Filecoin
Where was the data currently stored in this dataset sourced from
AWS Cloud
If you answered "Other" in the previous question, enter the details here
No response
If you are a data preparer. What is your location (Country/Region)
China
If you are a data preparer, how will the data be prepared? Please include tooling used and technical details?
If you are not preparing the data, who will prepare the data? (Provide name and business)
No response
Has this dataset been stored on the Filecoin network before? If so, please explain and make the case why you would like to store this dataset again to the network. Provide details on preparation and/or SP distribution.
No response
Please share a sample of the data
Confirm that this is a public dataset that can be retrieved by anyone on the Network
If you chose not to confirm, what was the reason
No response
What is the expected retrieval frequency for this data
Sporadic
For how long do you plan to keep this dataset stored on Filecoin
More than 3 years
In which geographies do you plan on making storage deals
Greater China, Asia other than Greater China, North America, South America
How will you be distributing your data to storage providers
HTTP or FTP server, Shipping hard drives, Lotus built-in data transfer
How did you find your storage providers
Slack
If you answered "Others" in the previous question, what is the tool or platform you used
No response
Please list the provider IDs and location of the storage providers you will be working with.
How do you plan to make deals to your storage providers
Lotus client
If you answered "Others/custom tool" in the previous question, enter the details here
No response
Can you confirm that you will follow the Fil+ guideline
Yes