Closed QodeNu closed 1 year ago
Thanks for your request! Everything looks good. :ok_hand:
A Governance Team member will review the information provided and contact you back pretty soon.
You are applying for a total amount of 10 PiB, but the single dataset is 2PiB and the number of replicas is 10. (2 PiB x 10 copies) = 20 PiB Why do you apply for 10 PiB and not 20 PiB?
Could you send your business license to filplus-app-review@fil.org in order to confirm your identity? Email name should includes the issue id #2026?
@Sunnyiscoming Cause I wanna go through step by step. I'm not sure whether the process is smooth or not, even though I have much more data. Looking forward your support. Thx!
yup, sure, I have sent the business licences through my email.
Total DataCap requested
10PiB
Expected weekly DataCap usage rate
1PiB
Client address
f1cgqp6ivn2expwksf4hmbv6qp2v6gi4r2qh6umzy
f02049625
f1cgqp6ivn2expwksf4hmbv6qp2v6gi4r2qh6umzy
512TiB
b8fce6c5-8fc8-4ce9-af06-3bd54ef34d85
In support for public data
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacecpba32guma6uqajq5sqczrviorcv7l5ye5cnsjs76y34x4dnvkic
Address
f1cgqp6ivn2expwksf4hmbv6qp2v6gi4r2qh6umzy
Datacap Allocated
512.00TiB
Signer Address
f1bp3tzp536edm7dodldceekzbsx7zcy7hdfg6uzq
Id
b8fce6c5-8fc8-4ce9-af06-3bd54ef34d85
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecpba32guma6uqajq5sqczrviorcv7l5ye5cnsjs76y34x4dnvkic
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacebklrbhq46iqguqwcikuovg7gtdkhj5agm6qvhhhp66q6l5xlt34y
Address
f1cgqp6ivn2expwksf4hmbv6qp2v6gi4r2qh6umzy
Datacap Allocated
512.00TiB
Signer Address
f1yjhnsoga2ccnepb7t3p3ov5fzom3syhsuinxexa
Id
b8fce6c5-8fc8-4ce9-af06-3bd54ef34d85
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebklrbhq46iqguqwcikuovg7gtdkhj5agm6qvhhhp66q6l5xlt34y
checker:manualTrigger
No active deals found for this client.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
checker:manualTrigger
No active deals found for this client.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
checker:manualTrigger
No active deals found for this client.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
No active deals found for this client.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
checker:manualTrigger
No active deals found for this client.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
⚠️ All retrieval success ratios are below 1%.
✔️ Storage provider distribution looks healthy.
⚠️ 100.00% of deals are for data replicated across less than 2 storage providers.
✔️ 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. Click here to view the Retrieval report.
f02049625
f1cgqp6ivn2expwksf4hmbv6qp2v6gi4r2qh6umzy
512TiB
2d18bdcd-0bf0-4b60-af6b-d9c2500c7baf
f02049625
f1cgqp6ivn2expwksf4hmbv6qp2v6gi4r2qh6umzy
100% weekly > 0.5PiB, requesting 0.5PiB
512TiB
512TiB
9.5PiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
10588 | 4 | 512TiB | 27.61 | 121.34TiB |
⚠️ All retrieval success ratios are below 1%.
✔️ Storage provider distribution looks healthy.
⚠️ 100.00% of deals are for data replicated across less than 3 storage providers.
✔️ 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. Click here to view the Retrieval report.
⚠️ All retrieval success ratios are below 1%.
✔️ Storage provider distribution looks healthy.
⚠️ 100.00% of deals are for data replicated across less than 3 storage providers.
✔️ 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. Click here to view the Retrieval report.
checker:manualTrigger
⚠️ All retrieval success ratios are below 1%.
✔️ Storage provider distribution looks healthy.
⚠️ 100.00% of deals are for data replicated across less than 3 storage providers.
✔️ 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. Click here to view the Retrieval report.
Hello @QodeNu Have you contacted the SPs? Are they all in favor of retrieval?The report shows that they all do not support retrieval.
Hello, @nj-steve Thank you for your attention. After I discovered this problem yesterday, I contacted these sps, and I informed them that they all should support retrieval, which is the newest rule in Fil+. It has been confirmed today that the node is retrievable. I hope you can support us and keep an eye on the latest updates, thank you.
⚠️ All retrieval success ratios are below 1%.
✔️ Storage provider distribution looks healthy.
⚠️ 100.00% of deals are for data replicated across less than 3 storage providers.
✔️ 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. Click here to view the Retrieval report.
checker:manualTrigger
⚠️ All retrieval success ratios are below 1%.
✔️ Storage provider distribution looks healthy.
⚠️ 100.00% of deals are for data replicated across less than 3 storage providers.
✔️ 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. Click here to view the Retrieval report.
⚠️ All retrieval success ratios are below 1%.
✔️ Storage provider distribution looks healthy.
⚠️ 100.00% of deals are for data replicated across less than 3 storage providers.
✔️ 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. Click here to view the Retrieval report.
⚠️ All retrieval success ratios are below 1%.
✔️ Storage provider distribution looks healthy.
⚠️ 100.00% of deals are for data replicated across less than 3 storage providers.
✔️ 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. Click here to view the Retrieval report.
checker:manualTrigger
⚠️ All retrieval success ratios are below 1%.
✔️ Storage provider distribution looks healthy.
⚠️ 100.00% of deals are for data replicated across less than 3 storage providers.
✔️ 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. Click here to view the Retrieval report.
✔️ Storage provider distribution looks healthy.
⚠️ 100.00% of deals are for data replicated across less than 3 storage providers.
✔️ 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. Click here to view the Retrieval report.
@QodeNu According to the CID check report, so far all the data has only been sealed on one SP, can you explain this situation? In addition, what plans do you have to solve this problem in the future?
Hi @sxxfuture-official The copies of data have been sent to various SPs through online and offline transfers at different speeds. It will definitely be shown across SPs gradually. Thx.
Gotta fix things soon, I'll support this round, but I'll keep an eye on it.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzaceczv3xcjc2rin3by25khkydpys3uzz7jpnzj46usbsg4ygjpopdsg
Address
f1cgqp6ivn2expwksf4hmbv6qp2v6gi4r2qh6umzy
Datacap Allocated
512.00TiB
Signer Address
f1foiomqlmoshpuxm6aie4xysffqezkjnokgwcecq
Id
2d18bdcd-0bf0-4b60-af6b-d9c2500c7baf
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceczv3xcjc2rin3by25khkydpys3uzz7jpnzj46usbsg4ygjpopdsg
From the recent CID report, it is evident that there has been a significant improvement in Graphsync retrieval. I would like to know what plans you have in improving HTTP/Bitswap retrieval? @QodeNu
It depends. As for now, we may using Lotus combining with the lates HTTP code updating in Boost Market. Will keep in touch with latest news in community.
Hope to see tangible results in these regards in the next round.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacebefhylz73bmecyktmmhgxo6x4ixxkw3awbelw4lfpghkkmmb2r4g
Address
f1cgqp6ivn2expwksf4hmbv6qp2v6gi4r2qh6umzy
Datacap Allocated
512.00TiB
Signer Address
f1inkdoatsbfumdvpctxbgcatscewr3rus5pxmsgi
Id
2d18bdcd-0bf0-4b60-af6b-d9c2500c7baf
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebefhylz73bmecyktmmhgxo6x4ixxkw3awbelw4lfpghkkmmb2r4g
f02049625
f1cgqp6ivn2expwksf4hmbv6qp2v6gi4r2qh6umzy
1PiB
861f77a9-5dbe-4d19-a717-463a26bb3dea
f02049625
f1cgqp6ivn2expwksf4hmbv6qp2v6gi4r2qh6umzy
200% weekly > 1PiB, requesting 1PiB
1PiB
465661.3YiB
465661.3YiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
22132 | 10 | 512TiB | 22.91 | 126.59TiB |
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 97.28% of deals are for data replicated across less than 4 storage providers.
✔️ 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. Click here to view the Retrieval report.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 97.28% of deals are for data replicated across less than 4 storage providers.
✔️ 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. Click here to view the Retrieval report.
what's your plan for fixing this warning?
Hello, @woshidama323 as you can see, data backup has begun to be uploaded by various SPs. Because this application form is in the early stage, SPs have different speeds to process data. In the end, it will be stored in accordance with the description of the application form. Please support, thank you.
Data Owner Name
DataMe
What is your role related to the dataset
Data Preparer
Data Owner Country/Region
Hong Kong
Data Owner Industry
IT & Technology Services
Website
http://www.econostatistics.co.za/
Social Media
Total amount of DataCap being requested
10PiB
Expected size of single dataset (one copy)
2P
Number of replicas to store
10
Weekly allocation of DataCap requested
1PiB
On-chain address for first allocation
f1cgqp6ivn2expwksf4hmbv6qp2v6gi4r2qh6umzy
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
How do you plan to prepare the dataset
IPFS, lotus, singularity
If you answered "other/custom tool" in the previous question, enter the details here
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, Asia other than Greater China, North America, South America, Europe
How will you be distributing your data to storage providers
Cloud storage (i.e. S3), HTTP or FTP server, IPFS, Shipping hard drives, Lotus built-in data transfer
How do you plan to choose storage providers
Slack, Partners
If you answered "Others" in the previous question, what is the tool or platform you plan to use
No response
If you already have a list of storage providers to work with, fill out their names and provider IDs below
How do you plan to make deals to your storage providers
Boost client, Lotus client, Droplet client, Singularity
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