Open Timothea01 opened 1 month ago
Due to the increase in the number of copies, a new upcoming co-op SP has been added f0717289 HongKong
(OLD vs NEW)
Please list the provider IDs and location of the storage providers you will be working with: f02866666 Tokyo f03144777 Tokyo f02820000 GuangZhou f02639655 GuangZhou f02588263 Hong Kong f01969779 Santa Clara(US) f02201190 US f02301,f03223,f0240185,f0143858 Santa Clara(US) f03175168 shenzhen f03175111 shenzhen f03166666 Hongkong f03166668 Hongkong f0717289 HongKong vs f02866666 Tokyo f03144777 Tokyo f02820000 GuangZhou f02639655 GuangZhou f02588263 Hong Kong f01969779 Santa Clara(US) f02201190 US f02301,f03223,f0240185,f0143858 Santa Clara(US) f03175168 shenzhen f03175111 shenzhen f03166666 Hongkong f03166668 Hongkong State: ChangesRequested vs Granted
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 27.27% of Storage Providers have retrieval success rate equal to zero.
✔️ 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.
Due to the increase in the number of copies, a new upcoming co-op SP has been added f0717289 HongKong
f0717289 Sector Size :64 GB change f01949267 Sector Size :32 GB
(OLD vs NEW)
Please list the provider IDs and location of the storage providers you will be working with: f02866666 Tokyo f03144777 Tokyo f02820000 GuangZhou f02639655 GuangZhou f02588263 Hong Kong f01969779 Santa Clara(US) f02201190 US f02301,f03223,f0240185,f0143858 Santa Clara(US) f03175168 shenzhen f03175111 shenzhen f03166666 Hongkong f03166668 Hongkong f01949267 HongKong vs f02866666 Tokyo f03144777 Tokyo f02820000 GuangZhou f02639655 GuangZhou f02588263 Hong Kong f01969779 Santa Clara(US) f02201190 US f02301,f03223,f0240185,f0143858 Santa Clara(US) f03175168 shenzhen f03175111 shenzhen f03166666 Hongkong f03166668 Hongkong f0717289 HongKong State: ChangesRequested vs Granted
Client used 75% of the allocated DataCap. Consider allocating next tranche.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 27.27% of Storage Providers have retrieval success rate equal to zero.
✔️ 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.
“⚠️ 27.27% of Storage Providers have retrieval success rate equal to zero.“ Still zero retrieval success rate warning Any action ?
They're checking their configuration to support spark retrieval, and I'll hold off on sealing data to them until there's a retrieval rate
Application is in Refill
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaceatyf5rnpsu5u5ofquc525eb5i52hflyq3jk7syq3hrj2oovi5zw4
Address
f1y4oymm2gj2txlsxx5g6yq6f5ifah6qp2bxcaspa
Datacap Allocated
1.17TiB
Signer Address
f1ez4nfx4lbqmddefk3gpqisf2xcfr3g6qm4qes7i
Id
c73b422f-3179-4304-b515-26b59cc6ad54
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceatyf5rnpsu5u5ofquc525eb5i52hflyq3jk7syq3hrj2oovi5zw4
Application is Granted
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 33.33% of Storage Providers have retrieval success rate equal to zero.
✔️ 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.
Client used 75% of the allocated DataCap. Consider allocating next tranche.
Since got a mistake when granting for 1.17TiB instead of 1.17PiB Will refill again here
Application is in Refill
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacecvuv5wyiligbcj4j37h4ios7mz3j7zjeyjagtp54dgzb7ehanhd4
Address
f1y4oymm2gj2txlsxx5g6yq6f5ifah6qp2bxcaspa
Datacap Allocated
1.17PiB
Signer Address
f1ez4nfx4lbqmddefk3gpqisf2xcfr3g6qm4qes7i
Id
1262a67f-30eb-4007-aa2e-afa21836be72
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecvuv5wyiligbcj4j37h4ios7mz3j7zjeyjagtp54dgzb7ehanhd4
Application is Granted
Client used 75% of the allocated DataCap. Consider allocating next tranche.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 25.00% of Storage Providers have retrieval success rate equal to zero.
⚠️ 100.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.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 14.29% of Storage Providers have retrieval success rate equal to zero.
⚠️ 78.57% 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.
Hey, why are there Deal Data Shared records for this application?
Sorry, just found this, we'll troubleshoot the issue and respond later, thanks!
After 2 days of checking, we found that the information of the car file returned from f01949267 is inconsistent with that of other SP's and the technician did not check it carefully, which led to the CID sharing problem, and we have already terminated the cooperation with this node, and we will check it carefully in the follow-up to prevent it from happening again, thank you!
Data Owner Name
Allen Institute
Data Owner Country/Region
Armenia
Data Owner Industry
Life Science / Healthcare
Website
https://registry.opendata.aws/?search=managedBy:allen%20institute
Social Media Handle
Timothea01
Social Media Type
Other
What is your role related to the dataset
Data Preparer
Total amount of DataCap being requested
5PiB
Expected size of single dataset (one copy)
500TiB
Number of replicas to store
10
Weekly allocation of DataCap requested
2PiB
On-chain address for first allocation
f1y4oymm2gj2txlsxx5g6yq6f5ifah6qp2bxcaspa
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)
Hong Kong
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.
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
2 to 3 years
In which geographies do you plan on making storage deals
Greater China, Asia other than Greater China, North America, Europe
How will you be distributing your data to storage providers
Cloud storage (i.e. S3), HTTP or FTP server, Shipping hard drives
How did you find your storage providers
Slack, Partners
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