[DataCap Application] <Henan Huandixu Trading Co., LTD., R & D> - <Data Backup>

[zhujiaqi]

Large Dataset Notary Application

To apply for DataCap to onboard your dataset to Filecoin, please fill out the following.

Core Information

• Organization Name: Henan Huandixu Trading Co., LTD., R & D
• Website / Social Media: https://www.huandixu.com/
• Total amount of DataCap being requested (between 500 TiB and 5 PiB): 5 PiB
• Weekly allocation of DataCap requested (usually between 1-100TiB): 100 TiB
• On-chain address for first allocation: f1dmjsw3otkvkh6sy3hygy6ebgs43o3i74qyg52gq

Please respond to the questions below by replacing the text saying "Please answer here". Include as much detail as you can in your answer.

Project details

Share a brief history of your project and organization.

Henan Huandixu Trading Co., LTD., R & D, production and sales of all kinds of doors and Windows products, products cover the series of open doors and Windows, sliding doors and Windows, heavy folding doors, insulation broken bridge window series and other kinds, is a modern private enterprise.

What is the primary source of funding for this project?

Company.

What other projects/ecosystem stakeholders is this project associated with?

None.

Use-case details

Describe the data being stored onto Filecoin

Design video, design pictures, design materials.

Where was the data in this dataset sourced from?

Internal and public resources.

Can you share a sample of the data? A link to a file, an image, a table, etc., are good ways to do this.

https://drive.google.com/drive/folders/15BvUVjsfPy1B0pwbV2gGU5NQdxroJz3H?usp=sharing
https://drive.google.com/drive/folders/1IDBkej46SHhWUK1jYPbLt3SiFywx3m1P?usp=sharing
https://drive.google.com/drive/folders/1RzHJhkwrrmsn1CsNPoSkgn0Q_IZWBRJQ?usp=sharing

Confirm that this is a public dataset that can be retrieved by anyone on the Network (i.e., no specific permissions or access rights are required to view the data).

Yes.

What is the expected retrieval frequency for this data?

1-2 times a year.

For how long do you plan to keep this dataset stored on Filecoin?

540 Days.

DataCap allocation plan

In which geographies (countries, regions) do you plan on making storage deals?

Hongkong/Singapore/Korea/America.

How will you be distributing your data to storage providers? Is there an offline data transfer process?

Offline transfer.

How do you plan on choosing the storage providers with whom you will be making deals? This should include a plan to ensure the data is retrievable in the future both by you and others.

We choose SPs based on geographic location and the quality of service the SPs provide.

How will you be distributing deals across storage providers?

We have about 610t data to store 5 SPs.

Do you have the resources/funding to start making deals as soon as you receive DataCap? What support from the community would help you onboard onto Filecoin?

Yes. f01938665,f01852677,f01851482,f01852325,f01938721

[large-datacap-requests[bot]]

Thanks for your request! Everything looks good. :ok_hand:

A Governance Team member will review the information provided and contact you back pretty soon.

[zhujiaqi]

Hello, how is the progress of our project? Is there any problem?

[large-datacap-requests[bot]]

Thanks for your request!

Heads up, you’re requesting more than the typical weekly onboarding rate of DataCap!

[large-datacap-requests[bot]]

Thanks for your request! Everything looks good. :ok_hand:

A Governance Team member will review the information provided and contact you back pretty soon.

[large-datacap-requests[bot]]

Thanks for your request! Everything looks good. :ok_hand:

A Governance Team member will review the information provided and contact you back pretty soon.

[simonkim0515]

Datacap Request Trigger

Total DataCap requested

5PiB

Expected weekly DataCap usage rate

100TiB

Client address

f1dmjsw3otkvkh6sy3hygy6ebgs43o3i74qyg52gq

[large-datacap-requests[bot]]

DataCap Allocation requested

Multisig Notary address

f02049625

Client address

f1dmjsw3otkvkh6sy3hygy6ebgs43o3i74qyg52gq

DataCap allocation requested

50TiB

Id

6a3c42f9-acb4-426a-8217-6fa473e8674c

[ipfscn]

Can you email filplus-app-review@fil.org using your official domain name to confirm your identity? Email name should contain Issue ID #1085.

[zhujiaqi]

@ipfscn Hi, I have sent the email. Please help confirm. Thank you!

[ipfscn]

Can your sp meet your retrieval requirements Can you list the SP you work with

[zhujiaqi]

@ipfscn Hi,Thank you for your reply. Yes,Sp can meet retrieval requirements. At present, we have contacted the following sp. f01938665,f01852677,f01851482,f01852325,f01938721

[ipfscn]

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacea67vnivh3ym3x6nb3kucjbugwxusaziwvj5atud4p32r5gknnwoc

Address

f1dmjsw3otkvkh6sy3hygy6ebgs43o3i74qyg52gq

Datacap Allocated

50.00TiB

Signer Address

f1j4n74chme7whbz3yls4a7ixqewb6dijypqg2a3a

Id

6a3c42f9-acb4-426a-8217-6fa473e8674c

You can check the status of the message here: https://filfox.info/en/message/bafy2bzacea67vnivh3ym3x6nb3kucjbugwxusaziwvj5atud4p32r5gknnwoc

[Tom-OriginStorage]

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacedyb2jb7yvgjjpunmk4ve4curlt5s7aywkxxspgf4ihs6ghcm3ysa

Address

f1dmjsw3otkvkh6sy3hygy6ebgs43o3i74qyg52gq

Datacap Allocated

50.00TiB

Signer Address

f1q6bpjlqia6iemqbrdaxr2uehrhpvoju3qh4lpga

Id

6a3c42f9-acb4-426a-8217-6fa473e8674c

You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedyb2jb7yvgjjpunmk4ve4curlt5s7aywkxxspgf4ihs6ghcm3ysa

[cryptowhizzard]

Hello,

Above i see a different email address then stated on the website.

mailto:mail@huandixu.com Seems official per the website. A different one @gmail is used for KYC.

@ipfscn or @Tom-OriginStorage : did you do the KYC here or duedilligence?

Why does this data qualify for FIL+ and not FIL-E where it belongs since this is commercial data? And is 5 PB not way more then needed here for some brochures backup of a private company producing doors and windows?

[herrehesse]

@ipfscn @Tom-OriginStorage

The described data indeed fits as company/business data., which is not suited for a LDN application for the Filecoin+ program. Please assist the applicant towards the FIL-E program.

"Design video, design pictures, design materials."

[zhujiaqi]

Hello, thank you for your reply, do you have any problems with our project? 1.We use the administrator mailbox to send KYC emails, admin@huandixu.com. 2.When we launched the application, there was no FIL-E program. 3.After a long wait, our project has finally started. Do you want us to reapply now? This will cause us unnecessary losses if we have to wait a long time, which is the result we don't want to see. We hope to be able to continue this project, and our data has been transferred to the relevant SPs in a variety of modes, both online and offline, and has been started. Looking forward to your reply, thank you! @cryptowhizzard @herrehesse

[herrehesse]

Best applicant,

It is great to hear how much you have already done regarding the preparation of the dataset in question. It would be an extreme shame to undo all this work so let's work together to make sure it doesn't.

Fortunately, preparation, processing and storage on the Filecoin network is separate from datacap. So you can just continue with the storage providers only now on the basis of:

1. Regular deals (1/100th lower cost compared to AWS)
2. Application for FIL-E

As stated above, the data does not meet the requirements for getting datacap from the Filecoin+ program.

Should I be able to help you further I would be happy to hear from you.

[cryptowhizzard]

@zhujiaqi

As you can see here a @gmail address is used for KYC by you or was that a CC?

[zhujiaqi]

@zhujiaqi

As you can see here a @gmail address is used for KYC by you or was that a CC?

Cc mail is only to ensure that the mail is sent normally. There is no other intention.

[zhujiaqi]

Best applicant,

It is great to hear how much you have already done regarding the preparation of the dataset in question. It would be an extreme shame to undo all this work so let's work together to make sure it doesn't.

Fortunately, preparation, processing and storage on the Filecoin network is separate from datacap. So you can just continue with the storage providers only now on the basis of:

1. Regular deals (1/100th lower cost compared to AWS)
2. Application for FIL-E

As stated above, the data does not meet the requirements for getting datacap from the Filecoin+ program.

Should I be able to help you further I would be happy to hear from you.

I don't quite understand what I need to do to ensure the smooth progress of my project. I think I hope your help! thank you! @herrehesse

[large-datacap-requests[bot]]

DataCap Allocation requested

Request number 2

Multisig Notary address

f02049625

Client address

f1dmjsw3otkvkh6sy3hygy6ebgs43o3i74qyg52gq

DataCap allocation requested

100TiB

Id

6a25de97-9389-4fa1-a338-f5b463aea9f9

[large-datacap-requests[bot]]

Stats & Info for DataCap Allocation

Multisig Notary address

f01858410

Client address

f1dmjsw3otkvkh6sy3hygy6ebgs43o3i74qyg52gq

Last two approvers

llifezou & ipfscn

Rule to calculate the allocation request amount

100% of weekly dc amount requested

DataCap allocation requested

100TiB

Total DataCap granted for client so far

50TiB

Datacap to be granted to reach the total amount requested by the client (5 PiB)

4.95PiB

Stats

Number of deals	Number of storage providers	Previous DC Allocated	Top provider	Remaining DC
1144	9	50TiB	13.99	6.59TiB

[filplus-checker-app[bot]]

DataCap and CID Checker Report[^1]

• Organization: Henan Huandixu Trading Co., LTD., R & D
• Client: f1dmjsw3otkvkh6sy3hygy6ebgs43o3i74qyg52gq

  Approvers

  1ipfscn
  1Tom-OriginStorage

Storage Provider Distribution

The below table shows the distribution of storage providers that have stored data for this client.

If this is the first time a provider takes verified deal, it will be marked as new.

For most of the datacap application, below restrictions should apply.

Since this is the 3rd allocation, the following restrictions have been relaxed:

• Storage provider should not exceed 70% of total datacap.
• Storage provider should not be storing duplicate data for more than 20%.
• Storage provider should have published its public IP address.
• All storage providers should be located in different regions.

✔️ Storage provider distribution looks healthy.

Provider	Location	Total Deals Sealed	Percentage	Unique Data	Duplicate Deals
f01852325	Hong Kong, Central and Western, HK BIH-Global Internet Harbor	4.84 TiB	12.45%	4.84 TiB	0.00%
f01852023	Busan, Busan, KR Korea Telecom	5.00 TiB	12.85%	5.00 TiB	0.00%
f01851482	Busan, Busan, KR Korea Telecom	3.66 TiB	9.40%	3.66 TiB	0.00%
f01852664	Singapore, Singapore, SG StarHub Ltd	4.91 TiB	12.61%	4.91 TiB	0.00%
f01852677	Morrisville, North Carolina, US TierPoint, LLC	4.88 TiB	12.53%	4.88 TiB	0.00%
f01966534	Bangkok, Bangkok, TH Zenlayer Inc	4.81 TiB	12.37%	4.81 TiB	0.00%
f01965334	Mumbai, Maharashtra, IN Zenlayer Inc	4.13 TiB	10.60%	4.13 TiB	0.00%
f01964073	Jakarta, Jakarta, ID Zenlayer Inc	3.56 TiB	9.16%	3.56 TiB	0.00%
f01969202	London, England, GB Zenlayer Inc	3.13 TiB	8.03%	3.13 TiB	0.00%

Deal Data Replication

The below table shows how each many unique data are replicated across storage providers.

Since this is the 3rd allocation, the following restrictions have been relaxed:

• No more than 70% of unique data are stored with less than 3 providers.

✔️ Data replication looks healthy.

Unique Data Size	Total Deals Made	Number of Providers	Deal Percentage
1.16 TiB	1.16 TiB	1	2.97%
480.00 GiB	960.00 GiB	2	2.41%
1.19 TiB	3.56 TiB	3	9.16%
4.56 TiB	18.25 TiB	4	46.91%
3.00 TiB	15.00 TiB	5	38.55%

Deal Data Shared with other Clients

The below table shows how many unique data are shared with other clients. Usually different applications owns different data and should not resolve to the same CID.

However, this could be possible if all below clients use same software to prepare for the exact same dataset or they belong to a series of LDN applications for the same dataset.

✔️ No CID sharing has been observed.

[^1]: To manually trigger this report, add a comment with text checker:manualTrigger

[BDEio]

@zhujiaqi Hi! Congratulations on your DataCap approval！ BDE is a trusted deals auction house helping you to get paid storing your data with reliable storage providers. If you need any help, please get in touch.

[NDLABS-Leo]

The data storage situation looks good and is willing to support

[NDLABS-Leo]

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzaced4zcnxijvectro4ejgrtphrechzten53ptkspuhw4bxdwfv53vcy

Address

f1dmjsw3otkvkh6sy3hygy6ebgs43o3i74qyg52gq

Datacap Allocated

100.00TiB

Signer Address

f1yayfsv6whu3rheviucvventj3y6t542xfpb47ei

Id

6a25de97-9389-4fa1-a338-f5b463aea9f9

You can check the status of the message here: https://filfox.info/en/message/bafy2bzaced4zcnxijvectro4ejgrtphrechzten53ptkspuhw4bxdwfv53vcy

[stcloudlisa]

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzaceble632libl3yga3atkix6hxzp3jtv5237y2m72h5vb4ibh7echmo

Address

f1dmjsw3otkvkh6sy3hygy6ebgs43o3i74qyg52gq

Datacap Allocated

100.00TiB

Signer Address

f1jvvltduw35u6inn5tr4nfualyd42bh3vjtylgci

Id

6a25de97-9389-4fa1-a338-f5b463aea9f9

You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceble632libl3yga3atkix6hxzp3jtv5237y2m72h5vb4ibh7echmo

[stcloudlisa]

I received the customer's request. This is the second round of the customer. I tend to support it. However, once I find that the customer has not complied with the rules, I will never help him again,

[large-datacap-requests[bot]]

DataCap Allocation requested

Request number 3

Multisig Notary address

f02049625

Client address

f1dmjsw3otkvkh6sy3hygy6ebgs43o3i74qyg52gq

DataCap allocation requested

200TiB

Id

8c911108-7ea9-4caa-baa2-6b7436dcbf52

[large-datacap-requests[bot]]

Stats & Info for DataCap Allocation

Multisig Notary address

f01858410

Client address

f1dmjsw3otkvkh6sy3hygy6ebgs43o3i74qyg52gq

Last two approvers

1LISA2 & not found

Rule to calculate the allocation request amount

200% of weekly dc amount requested

DataCap allocation requested

200TiB

Total DataCap granted for client so far

50TiB

Datacap to be granted to reach the total amount requested by the client (5 PiB)

4.95PiB

Stats

Number of deals	Number of storage providers	Previous DC Allocated	Top provider	Remaining DC
1593	10	100TiB	10.04	224GiB

[filplus-checker-app[bot]]

DataCap and CID Checker Report[^1]

• Organization: Henan Huandixu Trading Co., LTD., R & D
• Client: f1dmjsw3otkvkh6sy3hygy6ebgs43o3i74qyg52gq

  Approvers

  1ipfscn
  1NDLABS-OFFICE
  1stcouldlisa
  1Tom-OriginStorage

Storage Provider Distribution

The below table shows the distribution of storage providers that have stored data for this client.

If this is the first time a provider takes verified deal, it will be marked as new.

For most of the datacap application, below restrictions should apply.

• Storage provider should not exceed 30% of total datacap.
• Storage provider should not be storing duplicate data for more than 20%.
• Storage provider should have published its public IP address.
• All storage providers should be located in different regions.

✔️ Storage provider distribution looks healthy.

Provider	Location	Total Deals Sealed	Percentage	Unique Data	Duplicate Deals
f01852325	Hong Kong, Central and Western, HK BIH-Global Internet Harbor	5.00 TiB	10.18%	5.00 TiB	0.00%
f01852023	Busan, Busan, KR Korea Telecom	5.00 TiB	10.18%	5.00 TiB	0.00%
f01851482	Busan, Busan, KR Korea Telecom	4.78 TiB	9.74%	4.78 TiB	0.00%
f01852664	Singapore, Singapore, SG StarHub Ltd	5.00 TiB	10.18%	5.00 TiB	0.00%
f01852677	Morrisville, North Carolina, US TierPoint, LLC	5.00 TiB	10.18%	5.00 TiB	0.00%
f01965334	Mumbai, Maharashtra, IN Zenlayer Inc	5.00 TiB	10.18%	5.00 TiB	0.00%
f01966534	Bangkok, Bangkok, TH Zenlayer Inc	5.00 TiB	10.18%	5.00 TiB	0.00%
f01969202	London, England, GB Zenlayer Inc	5.00 TiB	10.18%	5.00 TiB	0.00%
f01964002	Kuala Lumpur, Kuala Lumpur, MY Zenlayer Inc	4.78 TiB	9.74%	4.78 TiB	0.00%
f01964073	Jakarta, Jakarta, ID Zenlayer Inc	4.53 TiB	9.23%	4.53 TiB	0.00%

Deal Data Replication

The below table shows how each many unique data are replicated across storage providers.

• No more than 30% of unique data are stored with less than 4 providers.

✔️ Data replication looks healthy.

Unique Data Size	Total Deals Made	Number of Providers	Deal Percentage
1.34 TiB	1.34 TiB	1	2.74%
2.25 TiB	9.00 TiB	4	18.33%
7.75 TiB	38.75 TiB	5	78.93%

Deal Data Shared with other Clients

The below table shows how many unique data are shared with other clients. Usually different applications owns different data and should not resolve to the same CID.

However, this could be possible if all below clients use same software to prepare for the exact same dataset or they belong to a series of LDN applications for the same dataset.

✔️ No CID sharing has been observed.

[^1]: To manually trigger this report, add a comment with text checker:manualTrigger

[newwebgroup]

checker:manualTrigger

[filplus-checker-app[bot]]

DataCap and CID Checker Report[^1]

• Organization: Henan Huandixu Trading Co., LTD., R & D
• Client: f1dmjsw3otkvkh6sy3hygy6ebgs43o3i74qyg52gq

  Approvers

  1ipfscn
  1NDLABS-OFFICE
  1stcouldlisa
  1Tom-OriginStorage

Storage Provider Distribution

The below table shows the distribution of storage providers that have stored data for this client.

If this is the first time a provider takes verified deal, it will be marked as new.

For most of the datacap application, below restrictions should apply.

• Storage provider should not exceed 30% of total datacap.
• Storage provider should not be storing duplicate data for more than 20%.
• Storage provider should have published its public IP address.
• All storage providers should be located in different regions.

✔️ Storage provider distribution looks healthy.

Provider	Location	Total Deals Sealed	Percentage	Unique Data	Duplicate Deals
f01852325	Hong Kong, Central and Western, HK BIH-Global Internet Harbor	13.50 TiB	9.89%	13.47 TiB	0.23%
f01852023	Busan, Busan, KR Korea Telecom	13.84 TiB	10.15%	13.81 TiB	0.23%
f01851482	Busan, Busan, KR Korea Telecom	13.06 TiB	9.57%	13.03 TiB	0.24%
f01852664	Singapore, Singapore, SG StarHub Ltd	13.72 TiB	10.05%	13.69 TiB	0.23%
f01852677	Morrisville, North Carolina, US TierPoint, LLC	13.81 TiB	10.12%	13.78 TiB	0.23%
f01969202	London, England, GB Zenlayer Inc	14.69 TiB	10.77%	14.69 TiB	0.00%
f01966534	Bangkok, Bangkok, TH Zenlayer Inc	14.22 TiB	10.42%	14.22 TiB	0.00%
f01965334	Mumbai, Maharashtra, IN Zenlayer Inc	13.72 TiB	10.05%	13.72 TiB	0.00%
f01964002	Kuala Lumpur, Kuala Lumpur, MY Zenlayer Inc	13.22 TiB	9.69%	13.22 TiB	0.00%
f01964073	Jakarta, Jakarta, ID Zenlayer Inc	12.66 TiB	9.28%	12.66 TiB	0.00%

Deal Data Replication

The below table shows how each many unique data are replicated across storage providers.

• No more than 30% of unique data are stored with less than 4 providers.

✔️ Data replication looks healthy.

Unique Data Size	Total Deals Made	Number of Providers	Deal Percentage
1.34 TiB	1.34 TiB	1	0.98%
704.00 GiB	1.38 TiB	2	1.01%
576.00 GiB	1.69 TiB	3	1.24%
3.13 TiB	12.50 TiB	4	9.16%
23.88 TiB	119.53 TiB	5	87.61%

Deal Data Shared with other Clients

The below table shows how many unique data are shared with other clients. Usually different applications owns different data and should not resolve to the same CID.

However, this could be possible if all below clients use same software to prepare for the exact same dataset or they belong to a series of LDN applications for the same dataset.

✔️ No CID sharing has been observed.

[^1]: To manually trigger this report, add a comment with text checker:manualTrigger

[newwebgroup]

After checking the CID Checker report, there is no CID sharing, the SP location is very scattered, and the proportion distribution is healthy.

[newwebgroup]

Canceled Request

The following request has been canceled by the notary, thus should not be considered as valid anymore.

Message sent to Filecoin Network

bafy2bzaceawdmwlixmpp424lj3jotyq42nrlh4uvdtkagusgvcpkrbx7yhzbw

Address

f1dmjsw3otkvkh6sy3hygy6ebgs43o3i74qyg52gq

Datacap Allocated

200.00TiB

Signer Address

f1e77zuityhvvw6u2t6tb5qlnsegy2s67qs4lbbbq

You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceawdmwlixmpp424lj3jotyq42nrlh4uvdtkagusgvcpkrbx7yhzbw

[cryptowhizzard]

Hello

None of the data is retrievable. This is agains FIL+ LDN rules and should have been checked first @newwebgroup

ERROR: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid bafykbzacedifko2xuu4zd7fvcfvnkm6artbum22ui7zqsnhcn733nhk3nzega: getting pieces containing block bafykbzacedifko2xuu4zd7fvcfvnkm6artbum22ui7zqsnhcn733nhk3nzega: failed to lookup index for mh a0e40220d0553b57a53991fcb5116ad533c08cc3466b5447f30934e26ff7b69d5b6e4860, err: datastore: key not found

ERROR: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid bafykbzaceccd32zuhvvkpzqc7zh2tpqcs6mcd57g2vd4ggx7y5zhowncjzbna: getting pieces containing block bafykbzaceccd32zuhvvkpzqc7zh2tpqcs6mcd57g2vd4ggx7y5zhowncjzbna: failed to lookup index for mh a0e40220843deb343d6aa7e602fe4fa9be02979821f7e6d547c31affc7727759a24e42d0, err: datastore: key not found

ERROR: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid bafykbzaceahgraachjp4ztwdp3cu2fzaerzjuz6svh22eev2cr4mngsz6xate: getting pieces containing block bafykbzaceahgraachjp4ztwdp3cu2fzaerzjuz6svh22eev2cr4mngsz6xate: failed to lookup index for mh a0e402200e6880023a5fcccec37ec54d172024729a67d2a9f5a212ba1478c69a59f5c132, err: datastore: key not found

ERROR: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid bafykbzaceaqbrbc2ghpz5z6orys3owru73tvvlku5a4teugaxzutwqec4ibvi: getting pieces containing block bafykbzaceaqbrbc2ghpz5z6orys3owru73tvvlku5a4teugaxzutwqec4ibvi: failed to lookup index for mh a0e402202018845a31df9ee7ce8e25b75a34fee75aad54e8393250c0be693b4082e20354, err: datastore: key not found

ERROR: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid bafykbzaceagjjjh2k6r7tj3bi32e32bf7dkvjfxc357mri57qqk3h4os5l4qu: getting pieces containing block bafykbzaceagjjjh2k6r7tj3bi32e32bf7dkvjfxc357mri57qqk3h4os5l4qu: failed to lookup index for mh a0e402200c94a4fa57a3f9a76146f44de825f8d55496e2df7ec8a3bf8415b3f1d2eaf90a, err: datastore: key not found

ERROR: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid bafykbzacecq63yxlctm5bbk6y6rb7udmgcxfxp5hgykyr4rlxsr2obyxkkicg: getting pieces containing block bafykbzacecq63yxlctm5bbk6y6rb7udmgcxfxp5hgykyr4rlxsr2obyxkkicg: failed to lookup index for mh a0e40220a1ede2eb14d9d0855ec7a21fd06c30ae5bbfa7361588f22bbca3a70717529023, err: datastore: key not found

ERROR: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid bafykbzacecuxdi3wpfa4iwrflux3q6fik4rzc4chlb27jfnaidq2usybhoyau: getting pieces containing block bafykbzacecuxdi3wpfa4iwrflux3q6fik4rzc4chlb27jfnaidq2usybhoyau: failed to lookup index for mh a0e40220a971a3767941c45a255d2fb878a857239170475875f495a040e1aa4b013bb00a, err: datastore: key not found

ERROR: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid QmerqgTmo2yhJzuuj56U1uTsE4Bi19on26vT5iSYBQWkku: getting pieces containing block QmerqgTmo2yhJzuuj56U1uTsE4Bi19on26vT5iSYBQWkku: failed to lookup index for mh 1220f576d21e9978f23a34465837d14988371d0db5638bb190e2e099072e62105376, err: datastore: key not found

ERROR: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid bafykbzaceanm643tepzexb7hlpyup2uw4eybiakhczfsvepjmy6zoppejozeq: getting pieces containing block bafykbzaceanm643tepzexb7hlpyup2uw4eybiakhczfsvepjmy6zoppejozeq: failed to lookup index for mh a0e402201acf737323f24b87e75bf147ea96e130140147164b2a91e9663d973de44bb248, err: datastore: key not found

ERROR: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid bafykbzacecuxdi3wpfa4iwrflux3q6fik4rzc4chlb27jfnaidq2usybhoyau: getting pieces containing block bafykbzacecuxdi3wpfa4iwrflux3q6fik4rzc4chlb27jfnaidq2usybhoyau: failed to lookup index for mh a0e40220a971a3767941c45a255d2fb878a857239170475875f495a040e1aa4b013bb00a, err: datastore: key not found

ERROR: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid bafykbzacedikma7b66heawdg5epnjbk76apvbq32fcfyayxpta5re7azje6a4: getting pieces containing block bafykbzacedikma7b66heawdg5epnjbk76apvbq32fcfyayxpta5re7azje6a4: failed to lookup index for mh a0e40220d0a603e1f78e405866e91ed4855ff01f50c37a288b8062ef983b127c19493c0e, err: datastore: key not found

ERROR: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid bafykbzacec6denb2djieletf2zejdheaxnutrppic6pjbbpml3mqhwhm4un7s: getting pieces containing block bafykbzacec6denb2djieletf2zejdheaxnutrppic6pjbbpml3mqhwhm4un7s: failed to lookup index for mh a0e40220bc32343a1a50459265d648919c80bb6938bde8179e9085ec5ed903d8ece51bf9, err: datastore: key not found

ERROR: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid bafykbzacebyzwl6ougy7fl3uiykqxzgzplm5jmcqzxuswp527zayd3pjz7qy6: getting pieces containing block bafykbzacebyzwl6ougy7fl3uiykqxzgzplm5jmcqzxuswp527zayd3pjz7qy6: failed to lookup index for mh a0e40220719b2fcea1b1f2af7446150be4d97ad9d4b050cde92b3fbafe4181ede9cfe18f, err: datastore: key not found

ERROR: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid bafykbzacebqbncnedh4rstjbtlfrnbijoggzujpop2dy5fgiivdnspmdww74g: getting pieces containing block bafykbzacebqbncnedh4rstjbtlfrnbijoggzujpop2dy5fgiivdnspmdww74g: failed to lookup index for mh a0e40220601689a419f9194d219acb168509718d9a25ee7e878e94c84546d93d83b5bfc3, err: datastore: key not found

ERROR: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid bafykbzacec6denb2djieletf2zejdheaxnutrppic6pjbbpml3mqhwhm4un7s: getting pieces containing block bafykbzacec6denb2djieletf2zejdheaxnutrppic6pjbbpml3mqhwhm4un7s: failed to lookup index for mh a0e40220bc32343a1a50459265d648919c80bb6938bde8179e9085ec5ed903d8ece51bf9, err: datastore: key not found

ERROR: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid bafykbzacedaxgbcugwuxj6rua3etmschobj3zm35uqxnoiiyj72tedvijhw2g: getting pieces containing block bafykbzacedaxgbcugwuxj6rua3etmschobj3zm35uqxnoiiyj72tedvijhw2g: failed to lookup index for mh a0e40220c173045435a974fa3406c93648477053bcb37da42ed721184ff5320ea849eda3, err: datastore: key not found

ERROR: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid QmaGWane68RnxmyWHL1hekpvY8Mv6nKUE1w2Up2n3PWruU: getting pieces containing block QmaGWane68RnxmyWHL1hekpvY8Mv6nKUE1w2Up2n3PWruU: failed to lookup index for mh 1220b13cbb481eeafb603e89c5b060cbcc32db8c0d918b83aa24da542330abbbf5af, err: datastore: key not found

[newwebgroup]

@cryptowhizzard Sincere thanks for your flags and reminders, I'm sorry, because I don't know the language development, so I don't have the ability to do some deeper inspections through Lotus. I will unsign this until further improvements and explanations are made by the Client.

[zhujiaqi]

@cryptowhizzard Thank you for your reply to let me find the problem. Can you tell me how to carry out this inspection? I want to try it myself, and then find the SP that serves us to solve it.

[cryptowhizzard]

Hi @zhujiaqi

You are confusing me. If you don’t know how to retrieve your data, what is the use of doing this exercise then?

[zhujiaqi]

Sorry, maybe my expression is not accurate, I think you have a better way to help me retrieve the data, I want to learn it to better ensure that our project goes smoothly. lotus client retrieve is the way I currently use it. Thank you for the problem you found. We have actively contacted sp to solve it. @cryptowhizzard

[cryptowhizzard]

Hello,

"lotus client retrieve" is the same way i do it here.

Please let us know when this is resolved so i can test retrievals and we can get this application on track again in line with the FIL+ rules.

[zhujiaqi]

checker:manualTrigger

[filplus-checker-app[bot]]

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^3]

✔️ 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> ...

Full report

Click here to view the full report.

[C00kies77]

checker:manualTrigger

[filplus-checker-app[bot]]

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^3]

✔️ 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> ...

Full report

Click here to view the full report.

[large-datacap-requests[bot]]

Thanks for your request! :exclamation: We have found some problems in the information provided. We could not find Website \/ Social Media field in the information provided We could not find Total amount of DataCap being requested (between 500 TiB and 5 PiB) field in the information provided We could not find Weekly allocation of DataCap requested (usually between 1-100TiB) field in the information provided We could not find On-chain address for first allocation field in the information provided We could not find Data Type of Application field in the information provided

Please, take a look at the request and edit the body of the issue providing all the required information.

[large-datacap-requests[bot]]

RootKeyHolders have approved multisig account. You can now request first datacap release