Open GameBoy200906 opened 6 months ago
Application is waiting for allocator review
Total DataCap requested
10PiB
Expected weekly DataCap usage rate
800TiB
DataCap Amount - First Tranche
1PiB
Client address
f1iwpuardscd66iajf7h665koadkfk7tmkuwokwyq
f1iwpuardscd66iajf7h665koadkfk7tmkuwokwyq
1PiB
ed9b2c8f-a7a2-4146-bba6-dd2fe594885d
Application is ready to sign
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacechgpxul47ubj7scdojrkraxhw6xczqpezdx4swjtyvwfrki6y4qa
Address
f1iwpuardscd66iajf7h665koadkfk7tmkuwokwyq
Datacap Allocated
1PiB
Signer Address
f1a2lia2cwwekeubwo4nppt4v4vebxs2frozarz3q
Id
ed9b2c8f-a7a2-4146-bba6-dd2fe594885d
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacechgpxul47ubj7scdojrkraxhw6xczqpezdx4swjtyvwfrki6y4qa
Application is Granted
checker:manualTrigger
⚠️ 1 storage providers sealed more than 90% of total datacap - f03083319: 100.00%
⚠️ All storage providers are located in the same region.
⚠️ 100.00% of Storage Providers have retrieval success rate equal to zero.
⚠️ The average retrieval success rate is 0.00%
✔️ Data replication looks healthy.
⚠️ CID sharing has been observed. (Top 3)
[^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.
Client used 75% of the allocated DataCap. Consider allocating next tranche.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 100.00% of Storage Providers have retrieval success rate equal to zero.
⚠️ 100.00% of Storage Providers have retrieval success rate less than 75%.
⚠️ The average retrieval success rate is 0.00%
✔️ Data replication looks healthy.
⚠️ CID sharing has been observed. (Top 3)
[^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
⚠️ 1 storage providers sealed too much duplicate data - f02035252: 25.60%
⚠️ 33.33% of Storage Providers have retrieval success rate equal to zero.
⚠️ 100.00% of Storage Providers have retrieval success rate less than 75%.
⚠️ The average retrieval success rate is 13.78%
✔️ Data replication looks healthy.
⚠️ CID sharing has been observed. (Top 3)
[^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
⚠️ 1 storage providers sealed too much duplicate data - f02035252: 25.60%
⚠️ 33.33% of Storage Providers have retrieval success rate equal to zero.
⚠️ 100.00% of Storage Providers have retrieval success rate less than 75%.
⚠️ The average retrieval success rate is 19.21%
✔️ Data replication looks healthy.
⚠️ CID sharing has been observed. (Top 3)
[^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.
"I understand that you were one of the Storage Providers who previously engaged in deals with me regarding the HRRR dataset, which clarifies the anomalies in the Deal Data Shared section. However, to move forward, I kindly request an explanation for the other anomalies highlighted in the CID Checker Report, particularly those concerning retrieval rates and duplicate data. @GameBoy200906
checker:manualTrigger
⚠️ 1 storage providers sealed too much duplicate data - f02035252: 43.93%
⚠️ 75.00% of Storage Providers have retrieval success rate equal to zero.
⚠️ 75.00% of Storage Providers have retrieval success rate less than 75%.
✔️ Data replication looks healthy.
⚠️ CID sharing has been observed. (Top 3)
[^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
⚠️ 1 storage providers sealed too much duplicate data - f02035252: 45.80%
⚠️ 75.00% of Storage Providers have retrieval success rate equal to zero.
⚠️ 75.00% of Storage Providers have retrieval success rate less than 75%.
✔️ Data replication looks healthy.
⚠️ CID sharing has been observed. (Top 3)
[^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
⚠️ 1 storage providers sealed too much duplicate data - f02035252: 25.60%
⚠️ 50.00% of Storage Providers have retrieval success rate equal to zero.
⚠️ 75.00% of Storage Providers have retrieval success rate less than 75%.
✔️ Data replication looks healthy.
⚠️ CID sharing has been observed. (Top 3)
[^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
⚠️ 1 storage providers sealed too much duplicate data - f02035252: 25.60%
⚠️ 50.00% of Storage Providers have retrieval success rate equal to zero.
⚠️ 75.00% of Storage Providers have retrieval success rate less than 75%.
✔️ Data replication looks healthy.
⚠️ CID sharing has been observed. (Top 3)
[^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.
⚠️ 50.00% of Storage Providers have retrieval success rate equal to zero.
⚠️ 50.00% of Storage Providers have retrieval success rate less than 75%.
✔️ Data replication looks healthy.
⚠️ CID sharing has been observed. (Top 3)
[^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.
⚠️ 50.00% of Storage Providers have retrieval success rate equal to zero.
⚠️ 50.00% of Storage Providers have retrieval success rate less than 75%.
✔️ Data replication looks healthy.
⚠️ CID sharing has been observed. (Top 3)
[^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.
Hi @NiwanDao 1) Regarding the retrieval problem, we noticed it a few months ago, but the report at that time was too bad, so we wanted to make the retrieval rate look better first. Now it looks okay, half and half. The few recent orders were all issued after the 5256 and 5252 nodes made retrieval commitments. 5256 performed very well, and 5252 must have encountered some problems. I will ask them to solve them as soon as possible. 2) Deal data sharing issue, you know, we had a pleasant cooperation before. When using the hrrr dataset, we found that various reasons led to some differences in the number of backups of the data of each piececid, and then the DC of the hrrr dataset had been used up, so we reused some car files with fewer backups in the hrrr dataset as new datasets for re-encapsulation. This is the main reason. Looking forward to better communication.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 50.00% of Storage Providers have retrieval success rate equal to zero.
⚠️ 50.00% of Storage Providers have retrieval success rate less than 75%.
✔️ Data replication looks healthy.
⚠️ CID sharing has been observed. (Top 3)
[^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.
⚠️ 25.00% of Storage Providers have retrieval success rate equal to zero.
⚠️ 75.00% of Storage Providers have retrieval success rate less than 75%.
✔️ Data replication looks healthy.
⚠️ CID sharing has been observed. (Top 3)
[^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
⚠️ 1 storage providers sealed too much duplicate data - f02128661: 25.66%
⚠️ 20.00% of Storage Providers have retrieval success rate equal to zero.
⚠️ 60.00% of Storage Providers have retrieval success rate less than 75%.
✔️ Data replication looks healthy.
⚠️ CID sharing has been observed. (Top 3)
[^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.
Data Owner Name
The High-Resolution Rapid Refresh (HRRR)
Data Owner Country/Region
United States
Data Owner Industry
Government
Website
https://rapidrefresh.noaa.gov/hrrr/
Social Media Handle
https://rapidrefresh.noaa.gov/hrrr/
Social Media Type
Slack
What is your role related to the dataset
Data Preparer
Total amount of DataCap being requested
10PiB
Expected size of single dataset (one copy)
2PiB
Number of replicas to store
5
Weekly allocation of DataCap requested
800TiB
On-chain address for first allocation
f1iwpuardscd66iajf7h665koadkfk7tmkuwokwyq
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)
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.
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
Daily
For how long do you plan to keep this dataset stored on Filecoin
1.5 to 2 years
In which geographies do you plan on making storage deals
Greater China, Asia other than Greater China
How will you be distributing your data to storage providers
HTTP or FTP server, Shipping hard drives
How did you find your storage providers
Partners, Others
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
Boost 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