Open liruior opened 2 months ago
Application is in Refill
Last pending allocation reverted for an application f1rbeabu5yjok6gicq757344w3w6wlbuujpomccua
.
Assigning 1P again, hoping to see the retrieval rate of the other three sp's in the next round
Application is in Refill
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacedijwup7anw6meiauee7uguegk2fv2ywetbl2iuubyeo5ilknab4q
Address
f1rbeabu5yjok6gicq757344w3w6wlbuujpomccua
Datacap Allocated
1PiB
Signer Address
f1apw6of55wzdbpjpnnyenv56ensi4iisaxgmigzi
Id
5623c47b-97a4-459c-a561-11ac7176d91c
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedijwup7anw6meiauee7uguegk2fv2ywetbl2iuubyeo5ilknab4q
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.
Nice to see excellent retrieval rates
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.
Randomized data retrieval has been verified to be consistent with the sample data and the sample presentation
Can you explain the lower retrieval rate for these two sps?
Can you explain the lower retrieval rate for these two sps?
I asked them, they explained that the first in line with the spark team testing, so lost part of the data, are now supported spark, the subsequent data has been done to back up the
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
bafy2bzacea3c5brjsiz74l6kenrkhclkaykexhtgtbkxk2mocugdhkuwdgnik
Address
f1rbeabu5yjok6gicq757344w3w6wlbuujpomccua
Datacap Allocated
2PiB
Signer Address
f1apw6of55wzdbpjpnnyenv56ensi4iisaxgmigzi
Id
d9f47b46-1c4e-488a-9286-508d960aff6c
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacea3c5brjsiz74l6kenrkhclkaykexhtgtbkxk2mocugdhkuwdgnik
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.
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.
2 SPs temporarily replaced for partial reasons
f02819999 Guangzhou f03144888 Guangzhou replace with f03166666 Hongkong f03166668 Hongkong
Latest listings f02363181 Huhehaote f02368946 Huhehaote f02362412 California f02639492 California f03166666 Hongkong f03166668 Hongkong f02822222 Hong Kong f02588263 Hong Kong
(OLD vs NEW)
Please list the provider IDs and location of the storage providers you will be working with: f02363181 Huhehaote f02368946 Huhehaote f02362412 California f02639492 California f03166666 Hongkong f03166668 Hongkong f02822222 Hong Kong f02588263 Hong Kong vs f02363181 Huhehaote f02368946 Huhehaote f02362412 California f02639492 California f02819999 Guangzhou f03144888 Guangzhou f02822222 Hong Kong f02588263 Hong Kong State: ChangesRequested vs 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.
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.
Data Owner Name
Yunnan Yimiao Environmental Protection Technology Co., Ltd
Data Owner Country/Region
China
Data Owner Industry
Environment
Website
www.yimiaohb.net
Social Media Handle
www.yimiaohb.net
Social Media Type
Other
What is your role related to the dataset
Dataset Owner
Total amount of DataCap being requested
12PiB
Expected size of single dataset (one copy)
2PiB
Number of replicas to store
6
Weekly allocation of DataCap requested
2PiB
On-chain address for first allocation
f1rbeabu5yjok6gicq757344w3w6wlbuujpomccua
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)
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.
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
Permanently
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
HTTP or FTP server, Shipping hard drives
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
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