Open bluketalk opened 6 months ago
Application is waiting for allocator review
Ready for review, please wait for the review result
Could you send an email to mike1999_fil@qq.com with your official domain in order to confirm your identity?
Best practice for storing large datasets includes ideally, storing it in 3 or more regions, with 3 or more storage provider operators or owners.So far it looks like you've only offered 2, will there be more?
If you are a data preparer, how will the data be prepared? Please include tooling used and technical details?
Could you send an email to mike1999_fil@qq.com with your official domain in order to confirm your identity?
Best practice for storing large datasets includes ideally, storing it in 3 or more regions, with 3 or more storage provider operators or owners.So far it looks like you've only offered 2, will there be more?
If you are a data preparer, how will the data be prepared? Please include tooling used and technical details?
There will be more regional storage service providers. We use go-graphsplit to split a large dataset into graph slices to make deals. storage and retrieval use droplet
Received mail
Once again, please be aware that you and #23 are the same organization with different datasets, Please note that there can be no CID sharing or no new datacap will be added!
Once again, please be aware that you and #23 are the same organization with different datasets, Please note that there can be no CID sharing or no new datacap will be added!
ok! We handle data that has not been traded before.
The information is correct.50 TiB will be issued in the first round as data validation.
Total DataCap requested
1PiB
Expected weekly DataCap usage rate
200TiB
DataCap Amount - First Tranche
50TiB
Client address
f1ros77tqminx2v5ni3ley526333m3rdj7gg43hna
f1ros77tqminx2v5ni3ley526333m3rdj7gg43hna
50TiB
43081a16-d110-4cce-a6cd-38534291db97
Application is ready to sign
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaceabmfqwl3i4duolblzjf4gtlxlsntz22sui4ljpbajhvp7s6y6yhm
Address
f1ros77tqminx2v5ni3ley526333m3rdj7gg43hna
Datacap Allocated
50TiB
Signer Address
f1uci7zkbdvscvu5mklxwwafkqqn7qo7rwc6rfoxi
Id
43081a16-d110-4cce-a6cd-38534291db97
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceabmfqwl3i4duolblzjf4gtlxlsntz22sui4ljpbajhvp7s6y6yhm
Application is Granted
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
✔️ 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.
✔️ 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.
A transaction has been generated, and the data is being retrieved for validation, please wait.
The customer explained that due to the update of the sample data, the retrieved data did not exist in the sample, and the customer has provided relevant screenshots to prove it Here is the data I retrieved Screenshot of the previous download data provided by the customer
The latest data will be retrieved again to verify
Again
Checked a couple of directories.Confirmation that the retrieved data and data samples are correct https://noaa-ghe-pds.s3.amazonaws.com/index.html#rain_rate/2024/03/27/
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
✔️ 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.
✔️ 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.
Application is in Refill
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacecak23f3vcu3bov6m4ysetqx2sq7awxvgi7dafldt25klwqvfc5vg
Address
f1ros77tqminx2v5ni3ley526333m3rdj7gg43hna
Datacap Allocated
100TiB
Signer Address
f1uci7zkbdvscvu5mklxwwafkqqn7qo7rwc6rfoxi
Id
b99f4147-505a-4fe4-8f7b-839f7e8e1b85
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecak23f3vcu3bov6m4ysetqx2sq7awxvgi7dafldt25klwqvfc5vg
Application is Granted
Application is in Refill
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
✔️ 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.
✔️ 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.
✔️ 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.
✔️ 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.
Wait for the sp to have an Increase in retrieval rate rate in the spark console and start approving the next round of
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
✔️ 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.
✔️ 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.
✔️ 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.
Still no retrieval rate
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
✔️ 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.
✔️ 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
yann-y
Project ID
1
Data Owner Name
noaa
Data Owner Country/Region
American Samoa
Data Owner Industry
Environment
Website
https://www.mty.wang
Social Media Handle
yann
Social Media Type
Slack
What is your role related to the dataset
Dataset Owner
Total amount of DataCap being requested
1PiB
Expected size of single dataset (one copy)
200TiB
Number of replicas to store
5
Weekly allocation of DataCap requested
200TiB
On-chain address for first allocation
f1ros77tqminx2v5ni3ley526333m3rdj7gg43hna
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
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
Weekly
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, North America
How will you be distributing your data to storage providers
Cloud storage (i.e. S3)
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
Droplet 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