Open ssnks1 opened 3 months ago
Application is waiting for allocator review
Thank you for your application, please fill in https://github.com/nicelove666/IPFSTT-Client-Due-Diligence-Form/issues/new/choose.
Our main focus is:
You need to provide comprehensive SP information, including SP, geographical location, and company name. Why do you want to put the data on Filecoin? Do you have relevant data processing experience? Can you confirm Spark retrievals for these miner IDs?
Any updates here?
We have filled out https://github.com/nicelove666/IPFSTT-Client-Due-Diligence-Form/issues/new/choose. This is the sp we cooperate with, f03068013-HK f03035686-GuangDong f01926635-SiChuang f01999119-SiChuang We are already preparing to download this data. We require SP to search based on Spark code matching and support Spark
Total DataCap requested
10PiB
Expected weekly DataCap usage rate
512TiB
DataCap Amount - First Tranche
256TiB
Client address
f1jctjr7yb6exwheiizud2darc3xa427vbzrtxrai
f1jctjr7yb6exwheiizud2darc3xa427vbzrtxrai
256TiB
33fa3777-1bca-45e3-ad6e-ea20210d1aff
Application is ready to sign
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaceaptps3ipcjvaubuegwfkiy5sgyjyazpop3i5hoiigzyhc5k4oejm
Address
f1jctjr7yb6exwheiizud2darc3xa427vbzrtxrai
Datacap Allocated
256TiB
Signer Address
f16hmuu3w247dkkhsrbbcbeqbugmpjbxpkrpcdatq
Id
33fa3777-1bca-45e3-ad6e-ea20210d1aff
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceaptps3ipcjvaubuegwfkiy5sgyjyazpop3i5hoiigzyhc5k4oejm
Application is Granted
checker:manualTrigger
No active deals found for this client.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
Any updates here?
Client used 75% of the allocated DataCap. Consider allocating next tranche.
checker:manualTrigger
No active deals found for this client.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
Sorry for the delayed response.
We have used up the 256T of DC that you provided in the first round, and we hope you can bring down the next round for us.
It's possible that the data delay caused us to miss the check on the data.
I noticed that other LDNs in the first round also did not check the data, but were still able to get approval.
So, can you help us with this?
Application is in Refill
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaceb7gilbteitsafqkgsmzkm5cptxpjk63im44ekmvl72p2kqwhr4x2
Address
f1jctjr7yb6exwheiizud2darc3xa427vbzrtxrai
Datacap Allocated
512TiB
Signer Address
f16hmuu3w247dkkhsrbbcbeqbugmpjbxpkrpcdatq
Id
0aec2238-69e5-4c64-8a02-eb80893ff49f
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceb7gilbteitsafqkgsmzkm5cptxpjk63im44ekmvl72p2kqwhr4x2
Application is Granted
Client used 75% of the allocated DataCap. Consider allocating next tranche.
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
bafy2bzacea6qpweomdsx63u7h4xevi7s2h2r4blgpuzk7qfhb3vr2enqw7gii
Address
f1jctjr7yb6exwheiizud2darc3xa427vbzrtxrai
Datacap Allocated
1PiB
Signer Address
f16hmuu3w247dkkhsrbbcbeqbugmpjbxpkrpcdatq
Id
c282410f-5803-40bd-9ca7-803ccb17253f
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacea6qpweomdsx63u7h4xevi7s2h2r4blgpuzk7qfhb3vr2enqw7gii
Application is Granted
Client used 75% of the allocated DataCap. Consider allocating next tranche.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 80.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.
First, there is a difference between the reported SP and the actual cooperative SP. Please provide an explanation. Second, f03174685 does not seem to support spark. Please find the reason and provide a solution.
Dear, the f03174685 is not included by spark, the data of other SPs are normal, and we are actively communicating with spark.
f03068013--HK f03162991--HK f01999119--Chengdu, Sichuan f01926635--Chengdu, Sichuan f03035686--Shenzhen f03174685--Shanghai
If possible, I hope to get your help. In the next round, I think spark data will be greatly improved.
It's Friday, any updates here?
Application is in Refill
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacea6cmsndrgsgzotk66vhqc7fau54364r5fiyg7b5xvwemo6x2btr4
Address
f1jctjr7yb6exwheiizud2darc3xa427vbzrtxrai
Datacap Allocated
2PiB
Signer Address
f16hmuu3w247dkkhsrbbcbeqbugmpjbxpkrpcdatq
Id
6e93ead2-be50-4e22-a848-47d92e21f71b
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacea6cmsndrgsgzotk66vhqc7fau54364r5fiyg7b5xvwemo6x2btr4
Application is Granted
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 16.67% of Storage Providers have retrieval success rate equal to zero.
⚠️ 83.33% 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.
We are working hard to get this resolved.
checker:manualTrigger
With the help of the Spark team, we should be able to see data updated soon.
✔️ Storage provider distribution looks healthy.
⚠️ 16.67% of Storage Providers have retrieval success rate equal to zero.
⚠️ 83.33% 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.
⚠️ 16.67% of Storage Providers have retrieval success rate equal to zero.
⚠️ 83.33% 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.
Hope to see spark data improvement
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 28.57% of Storage Providers have retrieval success rate equal to zero.
⚠️ 71.43% 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
ssnks1
Project ID
1
Data Owner Name
LAMOST DR7
Data Owner Country/Region
United States
Data Owner Industry
Life Science / Healthcare
Website
http://www.lamost.org/dr7/v2.0/
Social Media Handle
http://www.lamost.org/dr7/v2.0/
Social Media Type
Slack
What is your role related to the dataset
Data Preparer
Total amount of DataCap being requested
8PiB
Expected size of single dataset (one copy)
1024TiB
Number of replicas to store
8
Weekly allocation of DataCap requested
512TiB
On-chain address for first allocation
f1jctjr7yb6exwheiizud2darc3xa427vbzrtxrai
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?
No response
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
Yearly
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, North America, Europe
How will you be distributing your data to storage providers
Cloud storage (i.e. S3), 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
Boost client, Lotus client, Bidbot
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