Open Philoooo9 opened 2 weeks ago
Application is waiting for allocator review
Please fill in this form to complete your information. https://www.wenjuan.com/s/qAVFfuN/
Can you see my form?
@Philoooo9 Good. Got it.
There used to have someone who tried to store this dataset. Why do you want to store the dataset?
When you want to use datacap to store data, you'd better to select sps in different regions. Also, please make your sps support retrieval! We will check it from time to time.
@Destore2023 We have stored this dataset for 2 years. Due to the large size of this dataset, our local storage space is becoming insufficient to keep this dataset all the time. We want to store this dataset into filecoin network. We just want to keep the part we have downloaded. It is from NLM and useful to research. Could we store this data here?
@Philoooo9 Filecoin welcomes all kinds of valuable data being stored. But please take the storage process seriously and use datacap in a careful way. We will check cid report from time to time.
Thanks allocator. We will actively communicate with sps and you! @Destore2023 Please let us try our best.
Total DataCap requested
12PiB
Expected weekly DataCap usage rate
512TiB
DataCap Amount - First Tranche
512TiB
Client address
f1mp4xe27l46wl5vq4qdmedj5k5qm7twsewbgkgvy
f1mp4xe27l46wl5vq4qdmedj5k5qm7twsewbgkgvy
512TiB
3b32aff0-6c50-4869-b2e5-81d67989e4f3
Application is ready to sign
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaceawlopcoylseoae6gjuildcd7i65wpt7gmozu2vix34nigj7nlbrg
Address
f1mp4xe27l46wl5vq4qdmedj5k5qm7twsewbgkgvy
Datacap Allocated
512TiB
Signer Address
f1rppfznglfb7uyn3k6sfzeh47yq54ptvia5ixwsq
Id
3b32aff0-6c50-4869-b2e5-81d67989e4f3
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceawlopcoylseoae6gjuildcd7i65wpt7gmozu2vix34nigj7nlbrg
Application is Granted
Dear allocator @Destore2023, we'd add three sps into our plan. f01084413 Hunan f03100009 Guangdong f03233966 Zhejiang
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.
⚠️ 75.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.
@Philoooo9 Seems there's one sp do not support retrieval yet. Please remind this sp or change sp who is supporting retrieval. Also, please add sps to store more replicas.
@Destore2023 Thank you allocator. Thanks for your tips. We contacted with that sp. They found out it was a network problem and are fixing it.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 75.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.
@Destore2023 allocator, this sp is repairing the node and it supports retrieval in spark again. Please approve us next round.
@Philoooo9 Happy to see the improvement.
Application is in Refill
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaced53s2bv734ojdqajgelaa5eqlifxpdvbfrnmdynmst7qdn35r2s4
Address
f1mp4xe27l46wl5vq4qdmedj5k5qm7twsewbgkgvy
Datacap Allocated
1PiB
Signer Address
f1rppfznglfb7uyn3k6sfzeh47yq54ptvia5ixwsq
Id
f76e4dda-6836-42dc-ba4f-d8b551d11e49
You can check the status here https://filfox.info/en/message/bafy2bzaced53s2bv734ojdqajgelaa5eqlifxpdvbfrnmdynmst7qdn35r2s4
Application is Granted
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 66.67% 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.
Version
1
DataCap Applicant
Philoooo9
Project ID
x
Data Owner Name
National Library of Medicine
Data Owner Country/Region
United States
Data Owner Industry
Life Science / Healthcare
Website
https://www.nlm.nih.gov/
Social Media Handle
@NLM_NIH
Social Media Type
Twitter
What is your role related to the dataset
Data Preparer
Total amount of DataCap being requested
12PiB
Expected size of single dataset (one copy)
1592.4TiB
Number of replicas to store
8
Weekly allocation of DataCap requested
512TiB
On-chain address for first allocation
f1mp4xe27l46wl5vq4qdmedj5k5qm7twsewbgkgvy
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)
Malaysia
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
Daily
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, Europe
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, 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
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