Closed Finonaa closed 1 month ago
Application is waiting for allocator review
The information that you offered has been checked. It looks great. Some other questions for you: Can you share more information about SPs? ID and location. As a data preparer, how do you prepare data? Has this data been stored before?
The initial issue can be edited in order to solve the request of the verifier. The changes will be reflected in the application and an automatic comment will be posted in order to let the verifiers know the updated application can be reviewed.
1.f01660008 India f03126600 CN f03096886 CN f03099903 HK f01730296 HK Here are the SP information. 2.Via boost or lotus 3.There have been stored, but currently communicating SPs don't mind continuing to store them. It was invalid by the government. So we have to apply again. You can check the application. https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1039
Total DataCap requested
5PiB
Expected weekly DataCap usage rate
500TiB
DataCap Amount - First Tranche
100TiB
Client address
f15vna2wioxsck3sjzwdgikoeb5fkbrl3wkur3npi
f15vna2wioxsck3sjzwdgikoeb5fkbrl3wkur3npi
100TiB
6063e6bf-b5c2-4ad5-8947-2e8a653216e1
Application is ready to sign
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaceckm7dwlu62vsbb4uzzxmke6zjtg2fxuyuybvgtwxqnwxuym4fit6
Address
f15vna2wioxsck3sjzwdgikoeb5fkbrl3wkur3npi
Datacap Allocated
100TiB
Signer Address
f1mdk7s2vntzm6hu35yuo6vjubtrpfnb2awhgvrri
Id
6063e6bf-b5c2-4ad5-8947-2e8a653216e1
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceckm7dwlu62vsbb4uzzxmke6zjtg2fxuyuybvgtwxqnwxuym4fit6
Application is Granted
checker:manualTrigger
⚠️ 1 storage providers sealed more than 90% of total datacap - f03099903: 100.00%
⚠️ All storage providers are located in the same region.
✔️ 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
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.
Can you show the retrieval rate about your SPs?
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.
@Finonaa Please add more SPs in to the next round.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaceczq6sxrvw3slkf355ct2kgdhn646jdbxmcr2gydhonqyyu3fthb6
Address
f15vna2wioxsck3sjzwdgikoeb5fkbrl3wkur3npi
Datacap Allocated
500TiB
Signer Address
f1mdk7s2vntzm6hu35yuo6vjubtrpfnb2awhgvrri
Id
92011fc9-9a06-4f54-b865-64a668c23772
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceczq6sxrvw3slkf355ct2kgdhn646jdbxmcr2gydhonqyyu3fthb6
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.
@Finonaa CID Checker Report looks healthy. But no retrieval rate show in the report. Can you proof that?
@Finonaa CID Checker Report looks healthy. But no retrieval rate show in the report. Can you proof that?
Yes, maybe something wrong with the bot. We support retrieve. But about spark retrieval, we are waitting for the update from Spark Team. Thank you. ![Uploading 2871ed535195e6d892ef6744c3c0315.png…]()
Thanks for your explanation. But we still need the Spark retrieval rate. As an allocator, i have to make sure the datacap sealing in accordance with the rules. So this round i will not give you 1P but 512T instead.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaced3ww5sbrjhxtsgq2rjofq4xebda7vbizacip4yztugcmoefnqxww
Address
f15vna2wioxsck3sjzwdgikoeb5fkbrl3wkur3npi
Datacap Allocated
512TiB
Signer Address
f1mdk7s2vntzm6hu35yuo6vjubtrpfnb2awhgvrri
Id
fd1aaa38-5264-443a-b204-4eb2f590865d
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaced3ww5sbrjhxtsgq2rjofq4xebda7vbizacip4yztugcmoefnqxww
Application is Granted
Application is in Refill
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 100.00% of Storage Providers have retrieval success rate equal to zero.
⚠️ The average retrieval success rate is 0.00%
✔️ 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.
⚠️ 66.67% 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.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 57.14% of Storage Providers have retrieval success rate equal to zero.
⚠️ The average retrieval success rate is 0.02%
✔️ 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.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacebb6ulhvn4on227keeuufrre2povwfhlhjihl43dnmdcyoqlv5jaa
Address
f15vna2wioxsck3sjzwdgikoeb5fkbrl3wkur3npi
Datacap Allocated
512TiB
Signer Address
f1mdk7s2vntzm6hu35yuo6vjubtrpfnb2awhgvrri
Id
db678af0-576e-4740-9cc1-e7c0d98a1b58
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebb6ulhvn4on227keeuufrre2povwfhlhjihl43dnmdcyoqlv5jaa
Application is Granted
Client used 75% of the allocated DataCap. Consider allocating next tranche.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 71.43% 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.01%
✔️ 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.
The Spark retrieve rate is too low. It will be closed until you make it healthier. Thanks
checker:manualTrigger
⚠️ 1 storage providers sealed too much duplicate data - f02086562: 23.98%
⚠️ 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.
✔️ 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
Ximan Media
Project ID
1
Data Owner Name
FO
Data Owner Country/Region
China
Data Owner Industry
Information, Media & Telecommunications
Website
http://www.cqxmcm.com/index.html
Social Media Handle
http://www.cqxmcm.com/index.html
Social Media Type
WeChat
What is your role related to the dataset
Dataset Owner
Total amount of DataCap being requested
5PiB
Expected size of single dataset (one copy)
200t
Number of replicas to store
4
Weekly allocation of DataCap requested
500TiB
On-chain address for first allocation
f15vna2wioxsck3sjzwdgikoeb5fkbrl3wkur3npi
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
My Own Storage Infra
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)
None
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.
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
1 to 1.5 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, IPFS
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
No response
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