Open Jingana opened 1 year ago
Declaration: Regarding the retrieval rate: For the E-Fil+,We have stated that there is almost no retrieval when applying for this LDN. Due to the privacy and security of the data set, the customer does not want to be retrieved. When the customer needs it, he will contact us, and we will mail the hard disk to help them.
f01940930
f3ukxclzqvz2yid6jh2zupxw7y76jlgft6dnt4c2ucmrrl4q5y55ywiughkj6b74qn2ctchastgmufsmil4pua
400TiB
cbe774b8-a185-4449-b1a3-09e8b1726807
f01940930
f3ukxclzqvz2yid6jh2zupxw7y76jlgft6dnt4c2ucmrrl4q5y55ywiughkj6b74qn2ctchastgmufsmil4pua
200% of weekly dc amount requested
400TiB
181898.9YiB
181898.9YiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
30614 | 5 | 200TiB | 20.01 | 56.48TiB |
checker:manualTrigger
⚠️ All retrieval success ratios are below 1%.
✔️ 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. Click here to view the Retrieval report.
Declaration: Regarding the retrieval rate: For the E-Fil+,We have stated that there is almost no retrieval when applying for this LDN. Due to the privacy and security of the data set, the customer does not want to be retrieved. When the customer needs it, he will contact us, and we will mail the hard disk to help them.
Since this is an E-FIL+ program, customer needs should be considered first. Willing to support this round.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacebt6ec3pg3cvi6tq25q5rbpjk4v7mgndvythlgfktblsvivaejdtg
Address
f3ukxclzqvz2yid6jh2zupxw7y76jlgft6dnt4c2ucmrrl4q5y55ywiughkj6b74qn2ctchastgmufsmil4pua
Datacap Allocated
400.00TiB
Signer Address
f1bp3tzp536edm7dodldceekzbsx7zcy7hdfg6uzq
Id
cbe774b8-a185-4449-b1a3-09e8b1726807
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebt6ec3pg3cvi6tq25q5rbpjk4v7mgndvythlgfktblsvivaejdtg
checker:manualTrigger
⚠️ All retrieval success ratios are below 1%.
✔️ 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. Click here to view the Retrieval report.
声明: 关于检索率:对于E-Fil+,我们已经声明申请该LDN时几乎没有检索。由于数据集的隐私和安全性,客户不希望被检索。当客户需要的时候,他会联系我们,我们会邮寄硬盘来帮助他们。
temporarily supported
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacebatsxe57tpckbgv6yjmgt547b53ccn62p4irtdzxmrq5xfohs5vo
Address
f3ukxclzqvz2yid6jh2zupxw7y76jlgft6dnt4c2ucmrrl4q5y55ywiughkj6b74qn2ctchastgmufsmil4pua
Datacap Allocated
400.00TiB
Signer Address
f1jvvltduw35u6inn5tr4nfualyd42bh3vjtylgci
Id
cbe774b8-a185-4449-b1a3-09e8b1726807
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebatsxe57tpckbgv6yjmgt547b53ccn62p4irtdzxmrq5xfohs5vo
Hello @Jingana, we have a new KYC ID check available on filplus.storage. Please complete when you have a chance as a requirement for E-Fil+ to add additional layer of trust and to verify this GitHub account. See details: LINK
@kevzak Hi, I try to do as you say,but it is always failed. i tried about ten times.
@Jingana thank you for the feedback. Let me ask the team to look at failure code. It might require a different browser or better lighting. I will let you know
@Jingana thank you for the feedback. Let me ask the team to look at failure code. It might require a different browser or better lighting. I will let you know
Thanks!
checker:manualTrigger
⚠️ All retrieval success ratios are below 1%.
✔️ 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. Click here to view the Retrieval report.
checker:manualTrigger
⚠️ All retrieval success ratios are below 1%.
✔️ 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. Click here to view the Retrieval report.
@kevzak
We support retrieval but the Bot shows always 0% retrieval rate. Please help us.
checker:manualTrigger
⚠️ All retrieval success ratios are below 1%.
✔️ 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. Click here to view the Retrieval report.
Why are notaries signing with zero retrievability?
@laurarenpanda @stcouldlisa
checker:manualTrigger
⚠️ All retrieval success ratios are below 1%.
✔️ 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. Click here to view the Retrieval report.
@kevzak We support retrieval but the Bot shows always 0% retrieval rate. Please help us.
Can you help me? I don't know what's wrong.
Why are notaries signing with zero retrievability?
@laurarenpanda @stcouldlisa
Before question others,pls see all the information and check the truth.Ok? We support retrieval but the bot always show 0%, and I asked Kevzak for help. The truth is that retrieval is ok.
checker:manualTrigger
⚠️ All retrieval success ratios are below 1%.
✔️ 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. Click here to view the Retrieval report.
checker:manualTrigger
⚠️ All retrieval success ratios are below 1%.
✔️ 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. Click here to view the Retrieval report.
checker:manualTrigger
⚠️ All retrieval success ratios are below 1%.
✔️ 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. Click here to view the Retrieval report.
f01940930
f3ukxclzqvz2yid6jh2zupxw7y76jlgft6dnt4c2ucmrrl4q5y55ywiughkj6b74qn2ctchastgmufsmil4pua
800TiB
ad599816-063b-4a44-9e87-0a5a11e3d1ef
f01940930
f3ukxclzqvz2yid6jh2zupxw7y76jlgft6dnt4c2ucmrrl4q5y55ywiughkj6b74qn2ctchastgmufsmil4pua
400% of weekly dc amount requested
800TiB
363797880709171445760.0YiB
363797880709171445760.0YiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
75570 | 5 | 400TiB | 22.65 | 101.04TiB |
checker:manualTrigger
⚠️ All retrieval success ratios are below 1%.
✔️ 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. Click here to view the Retrieval report.
Declaration:We totally support retrieval and obey the rules. But don't know why the bot always show 0%,and we contact the PL, get no reponse. Our only way is proof ourself.Here are the evidence. Everyone can check the truth. 归档.zip
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. Click here to view the Retrieval 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. Click here to view the Retrieval report.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzaceapkby2l6sthzclwhjc7cd5uefh2equkin4aqvlref33vmkwro7z4
Address
f3ukxclzqvz2yid6jh2zupxw7y76jlgft6dnt4c2ucmrrl4q5y55ywiughkj6b74qn2ctchastgmufsmil4pua
Datacap Allocated
800.00TiB
Signer Address
f1j3u7crhjzwb2cj5mq7vodlt4o66yoyci7lhcauy
Id
ad599816-063b-4a44-9e87-0a5a11e3d1ef
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceapkby2l6sthzclwhjc7cd5uefh2equkin4aqvlref33vmkwro7z4
Reached out by the client on Slack. Client sample data and distribution plan checks out. As this is a efil+ ldn, the enterprise client seems to be okay with all the storage progress thus far.
The client has effectively improved the retrieval success rate, and according to the current check, other aspects are also healthy.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacedvxapirfwomcixmgjmlioeget6lhz3f6o3aybhd7aegmrzty3hma
Address
f3ukxclzqvz2yid6jh2zupxw7y76jlgft6dnt4c2ucmrrl4q5y55ywiughkj6b74qn2ctchastgmufsmil4pua
Datacap Allocated
800.00TiB
Signer Address
f1tfg54zzscugttejv336vivknmsnzzmyudp3t7wi
Id
ad599816-063b-4a44-9e87-0a5a11e3d1ef
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedvxapirfwomcixmgjmlioeget6lhz3f6o3aybhd7aegmrzty3hma
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. Click here to view the Retrieval 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. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
Data Owner Name
Zhengzhou Jingan Network Technology Co., Ltd.
Data Owner Country/Region
China
Data Owner Industry
Information, Media & Telecommunications
Website
https://www.zzidc.com/
Social Media
Total amount of DataCap being requested
5PiB
Weekly allocation of DataCap requested
200TiB
On-chain address for first allocation
f3ukxclzqvz2yid6jh2zupxw7y76jlgft6dnt4c2ucmrrl4q5y55ywiughkj6b74qn2ctchastgmufsmil4pua
Custom multisig
Identifier
E-fil
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
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
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
What is the expected retrieval frequency for this data
Sporadic
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
How will you be distributing your data to storage providers
HTTP or FTP server, Shipping hard drives
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
Lotus 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