search

filecoin-project / filecoin-plus-large-datasets

Hub for client applications for DataCap at a large scale
110 stars 62 forks source link

[DataCap Application] <Long An Law Firm> - < Long An University Hall> #1205

Closed Swift-scouts closed 1 year ago

Swift-scouts commented 1 year ago

Large Dataset Notary Application

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

Core Information

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.

Founded in 1992, Long An is one of the earliest partnership law firms in China, and was successfully restructured into a special general partnership law firm in 2017. At present, we have offices in more than 30 cities in China, including Beijing, Shanghai, Shenyang and Shenzhen, and Longan is expanding further. In order to make the new partner better serve customers, we set up video courses to help Long An'er learn legal knowledge and provide a way for the Grand Duke to learn law.

What is the primary source of funding for this project?

Ourselves.

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

No

Use-case details

Describe the data being stored onto Filecoin

Law teaching video

Where was the data in this dataset sourced from?

Some of them came from our staff's live recording ,as well as joint discussions with other teachers,and we also had public interest legal courses accumulated from the Internet

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://pan.baidu.com/s/1g9vJFY1EAoyS2q3F0FHRSA 
提取码：gg58
It has 30-day access

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?

Maybe twice a year is enough

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

We hope it will last a long time, in Filecoin maybe 3-5 years

DataCap allocation plan

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

Hong Kong

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

We will negotiate with SP, both online and offline are acceptable

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'll choose storage providers based on the price and geography and other aspects affect the storage service. Currenct candidates are: f01938665,f01859603,f01909429,f01938721,f01851482

How will you be distributing deals across storage providers?

We plan to have 5 replicas and each providers should keep more than 50%  source data.

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, we have enough resources and funds to start trading.
large-datacap-requests[bot] commented 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.

large-datacap-requests[bot] commented 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.

simonkim0515 commented 1 year ago

Datacap Request Trigger

Total DataCap requested

5PiB

Expected weekly DataCap usage rate

100TiB

Client address

f1u7l2fksfm6hoqcdss4yabrg2l52hx55vcnc7hiq

large-datacap-requests[bot] commented 1 year ago

DataCap Allocation requested

Multisig Notary address

f02049625

Client address

f1u7l2fksfm6hoqcdss4yabrg2l52hx55vcnc7hiq

DataCap allocation requested

50TiB

Id

ba1d80b8-49a6-4071-8bd8-647c15a4364f

cryptowhizzard commented 1 year ago

Hello,

The sample data link has expired. Can you please re-upload it so i can take a look at it?

Swift-scouts commented 1 year ago

OK， 链接：https://pan.baidu.com/s/1R5LNd0zjANlgXf1rB0Nn_g 提取码：18d2 Thanks for checking

newwebgroup commented 1 year ago

Hey Client， About KYC&KYB 1：Could you send an email to filplus-app-review@fil.org ？

The content should include the number of the LDN application.

2：Can you provide more detailed information about other storage providers participated in this program, such as you can list SPs you have contacted with at present?

3.How large is your existing dataset? How much is the data growth per month?

Swift-scouts commented 1 year ago
图片

1，Hi,Email has been sent, please check

2，Currently contacted SPs are f01965334，f01966534，f01967473，f01901379，f01901765，f01907545 and son on 3，Our accumulated data is almost 2PiB, and the amount of data generated every month is about 50~100TiB. thank you!

newwebgroup commented 1 year ago

Because it was the first round, the Client answered my relevant questions, and the conditions for triggering signature had been met, so I chose to pass. If anyone has more questions about the application, they can keep watching and checking.

newwebgroup commented 1 year ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzaceay7us6ee2hzlvxnmtfmzfuw6rqxuluzelezo2gmzydhs32kybgf4

Address

f1u7l2fksfm6hoqcdss4yabrg2l52hx55vcnc7hiq

Datacap Allocated

50.00TiB

Signer Address

f1e77zuityhvvw6u2t6tb5qlnsegy2s67qs4lbbbq

Id

ba1d80b8-49a6-4071-8bd8-647c15a4364f

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

Tom-OriginStorage commented 1 year ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacebyyin77g2tzsx4ruugl5mubzmfegt72agacbacrlp6g4ukjla77u

Address

f1u7l2fksfm6hoqcdss4yabrg2l52hx55vcnc7hiq

Datacap Allocated

50.00TiB

Signer Address

f1q6bpjlqia6iemqbrdaxr2uehrhpvoju3qh4lpga

Id

ba1d80b8-49a6-4071-8bd8-647c15a4364f

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

large-datacap-requests[bot] commented 1 year ago

DataCap Allocation requested

Request number 2

Multisig Notary address

f02049625

Client address

f1u7l2fksfm6hoqcdss4yabrg2l52hx55vcnc7hiq

DataCap allocation requested

100TiB

Id

232a4d2d-3cfc-4ebb-a351-6495aea3ec92

large-datacap-requests[bot] commented 1 year ago

Stats & Info for DataCap Allocation

Multisig Notary address

f01858410

Client address

f1u7l2fksfm6hoqcdss4yabrg2l52hx55vcnc7hiq

Last two approvers

llifezou & newwebgroup

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 (5PiB)

4.95PiB

Stats

Number of deals Number of storage providers Previous DC Allocated Top provider Remaining DC
1140 9 50TiB 14.04 6.84TiB
filplus-checker-app[bot] commented 1 year ago

DataCap and CID Checker Report[^1]

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 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.81 TiB 12.48% 4.81 TiB 0.00%
f01852023 Busan, Busan, KR
Korea Telecom		 4.97 TiB 12.88% 4.97 TiB 0.00%
f01851482 Busan, Busan, KR
Korea Telecom		 3.78 TiB 9.81% 3.78 TiB 0.00%
f01852664 Singapore, Singapore, SG
StarHub Ltd		 4.78 TiB 12.40% 4.78 TiB 0.00%
f01852677 Morrisville, North Carolina, US
TierPoint, LLC		 4.75 TiB 12.32% 4.75 TiB 0.00%
f01966534 Bangkok, Bangkok, TH
Zenlayer Inc		 4.91 TiB 12.72% 4.91 TiB 0.00%
f01965334 Mumbai, Maharashtra, IN
Zenlayer Inc		 3.91 TiB 10.13% 3.91 TiB 0.00%
f01964073 Jakarta, Jakarta, ID
Zenlayer Inc		 3.59 TiB 9.32% 3.59 TiB 0.00%
f01969202 London, England, GB
Zenlayer Inc		 3.06 TiB 7.94% 3.06 TiB 0.00%

Provider Distribution

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:

✔️ Data replication looks healthy.

Unique Data Size Total Deals Made Number of Providers Deal Percentage
832.00 GiB 832.00 GiB 1 2.11%
512.00 GiB 1.00 TiB 2 2.59%
1.03 TiB 3.09 TiB 3 8.02%
4.16 TiB 16.63 TiB 4 43.11%
3.41 TiB 17.03 TiB 5 44.17%

Replication Distribution

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

herrehesse commented 1 year ago

Dear Applicant @Swift-scouts,

Due to the increased amount of erroneous/wrong Filecoin+ data recently, on behalf of the entire community, we feel compelled to go deeper into datacap requests. Hereby to ensure that the overall value of the Filecoin network and Filecoin+ program increases and is not abused.

Please answer the questions below as comprehensively as possible.

Customer data

We expect that for the onboarding of customers with the scale of an LDN there would have been at least multiple email and perhaps several chat conversations preceding it. A single email with an agreement does not qualify here.

Should this only be soley for acquiring datacap this is of course out of the question. The customer must have a legitimate reason for wanting to use the Filecoin+ program which is intended as a program to store useful and public datasets on the network.

(As an intermediate solution Filecoin offers the FIL-E program or the glif.io website for business datasets that do not meet the requirements for a Filecoin+ dataset)

Files and Processing

Hopefully you understand the caution the overall community has for onboarding the wrong data. We understand the increased need for Filecoin+, however, we must not allow the program to be misused. Everything depends on a valuable and useful network, let's do our best to make this happen. Together.

Swift-scouts commented 1 year ago

We and our friends from Long 'an Law Firm prepared the data transmission plan several months ago and contacted the storage service provider in Hong Kong. The data is transferred to the storage server in Hong Kong through the network. In this way, when storing a copy of data in Hong Kong, it is more convenient to provide data transmission services to storage providers in different regions. Now 1P of data has been transferred to the storage server in Hong Kong. Hong Kong is a very powerful financial and information center with sufficient hardware and software capabilities to provide data transmission services. Filecoin+ is a very good project. Our partners are very happy to put their own teaching and popular science data on this project and lick the bricks for filecoin project. We also take data quality very seriously in filecoin+. In data transfer and download, data is de-duplicated so you don't have to worry about duplicate data.

NDLABS-Leo commented 1 year ago

Willing to support.

NDLABS-Leo commented 1 year ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacebukp2jdchfjaf4af2nz43cuyozwb2fjlzwfgglvm3iy27wp7wy56

Address

f1u7l2fksfm6hoqcdss4yabrg2l52hx55vcnc7hiq

Datacap Allocated

100.00TiB

Signer Address

f1yayfsv6whu3rheviucvventj3y6t542xfpb47ei

Id

232a4d2d-3cfc-4ebb-a351-6495aea3ec92

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

stcloudlisa commented 1 year ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzaceb27umesi3cuaebf7lc3mox425nvuz3mawkh2rv3brjzqupaimzzi

Address

f1u7l2fksfm6hoqcdss4yabrg2l52hx55vcnc7hiq

Datacap Allocated

100.00TiB

Signer Address

f1jvvltduw35u6inn5tr4nfualyd42bh3vjtylgci

Id

232a4d2d-3cfc-4ebb-a351-6495aea3ec92

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

large-datacap-requests[bot] commented 1 year ago

DataCap Allocation requested

Request number 3

Multisig Notary address

f02049625

Client address

f1u7l2fksfm6hoqcdss4yabrg2l52hx55vcnc7hiq

DataCap allocation requested

200TiB

Id

be3fdb2c-3741-43ce-8e62-d915c7015a2b

large-datacap-requests[bot] commented 1 year ago

Stats & Info for DataCap Allocation

Multisig Notary address

f01858410

Client address

f1u7l2fksfm6hoqcdss4yabrg2l52hx55vcnc7hiq

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 (5PiB)

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] commented 1 year ago

DataCap and CID Checker Report[^1]

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 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.22% 5.00 TiB 0.00%
f01852023 Busan, Busan, KR
Korea Telecom		 5.00 TiB 10.22% 5.00 TiB 0.00%
f01851482 Busan, Busan, KR
Korea Telecom		 4.94 TiB 10.10% 4.94 TiB 0.00%
f01852664 Singapore, Singapore, SG
StarHub Ltd		 5.00 TiB 10.22% 5.00 TiB 0.00%
f01852677 Morrisville, North Carolina, US
TierPoint, LLC		 5.00 TiB 10.22% 5.00 TiB 0.00%
f01966534 Bangkok, Bangkok, TH
Zenlayer Inc		 5.00 TiB 10.22% 5.00 TiB 0.00%
f01965334 Mumbai, Maharashtra, IN
Zenlayer Inc		 4.91 TiB 10.03% 4.91 TiB 0.00%
f01969202 London, England, GB
Zenlayer Inc		 4.84 TiB 9.90% 4.84 TiB 0.00%
f01964002 Kuala Lumpur, Kuala Lumpur, MY
Zenlayer Inc		 4.78 TiB 9.78% 4.78 TiB 0.00%
f01964073 Jakarta, Jakarta, ID
Zenlayer Inc		 4.44 TiB 9.07% 4.44 TiB 0.00%

Provider Distribution

Deal Data Replication

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

✔️ Data replication looks healthy.

Unique Data Size Total Deals Made Number of Providers Deal Percentage
32.00 GiB 96.00 GiB 3 0.19%
1.03 TiB 4.13 TiB 4 8.43%
8.94 TiB 44.69 TiB 5 91.37%

Replication Distribution

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 commented 1 year ago

checker:manualTrigger

filplus-checker-app[bot] commented 1 year ago

DataCap and CID Checker Report[^1]

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 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.38 TiB 9.84% 13.38 TiB 0.00%
f01852023 Busan, Busan, KR
Korea Telecom		 13.84 TiB 10.19% 13.84 TiB 0.00%
f01851482 Busan, Busan, KR
Korea Telecom		 13.03 TiB 9.59% 13.03 TiB 0.00%
f01852664 Singapore, Singapore, SG
StarHub Ltd		 13.84 TiB 10.19% 13.84 TiB 0.00%
f01852677 Morrisville, North Carolina, US
TierPoint, LLC		 13.69 TiB 10.07% 13.69 TiB 0.00%
f01969202 London, England, GB
Zenlayer Inc		 14.56 TiB 10.72% 14.56 TiB 0.00%
f01966534 Bangkok, Bangkok, TH
Zenlayer Inc		 14.19 TiB 10.44% 14.19 TiB 0.00%
f01965334 Mumbai, Maharashtra, IN
Zenlayer Inc		 13.63 TiB 10.03% 13.63 TiB 0.00%
f01964002 Kuala Lumpur, Kuala Lumpur, MY
Zenlayer Inc		 13.28 TiB 9.77% 13.28 TiB 0.00%
f01964073 Jakarta, Jakarta, ID
Zenlayer Inc		 12.47 TiB 9.17% 12.47 TiB 0.00%

Provider Distribution

Deal Data Replication

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

✔️ Data replication looks healthy.

Unique Data Size Total Deals Made Number of Providers Deal Percentage
1.41 TiB 1.41 TiB 1 1.03%
672.00 GiB 1.31 TiB 2 0.97%
480.00 GiB 1.41 TiB 3 1.03%
3.06 TiB 12.25 TiB 4 9.01%
23.91 TiB 119.53 TiB 5 87.95%

Replication Distribution

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

cryptowhizzard commented 1 year ago

Hello,

None of this data is available for retrieval. This is against the FIL+ / LDN rules. Please contact your SP's and make the data retrievable before we can continue allocating datacap.

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

ERROR: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid bafykbzacedghdivbilivdvdyndedsit2oxxrgw7gp5uaukkz4w2a66itmcrc6: getting pieces containing block bafykbzacedghdivbilivdvdyndedsit2oxxrgw7gp5uaukkz4w2a66itmcrc6: failed to lookup index for mh a0e40220cc71a2a142d151d47868c839227a75ef135be67f680a2959e5b40f791360a22f, 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 bafybeie5szlgl5joyjerpwuqb6dojicdrxruo2pra7r422ybd5q4lnrx64: getting pieces containing block bafybeie5szlgl5joyjerpwuqb6dojicdrxruo2pra7r422ybd5q4lnrx64: failed to lookup index for mh 12209d965665f52ec24917da900f86e4a0438de34769f107e3cd6b011f61c5b637f7, err: datastore: key not found

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

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

ERROR: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid bafykbzaceclrlluzhlnoashnedevtfow3cal5ouhdq352ywqqfbq5zwxhfycq: getting pieces containing block bafykbzaceclrlluzhlnoashnedevtfow3cal5ouhdq352ywqqfbq5zwxhfycq: failed to lookup index for mh a0e402209715ae993adae048ed20c95995d6d880beba871c37dd62d081430ee6d7397028, 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 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 bafybeihm57xysyijidtldkujnbmp26dffbpqo562b6zb76gnoyyidp3r4e: getting pieces containing block bafybeihm57xysyijidtldkujnbmp26dffbpqo562b6zb76gnoyyidp3r4e: failed to lookup index for mh 1220ecefef89610940e6b1aa896858fd7865285f0777da0fb21ff8cd763081bf71e1, err: datastore: key not found

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

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

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

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

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

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

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

cryptowhizzard commented 1 year ago

checker:manualTrigger

filplus-checker-app[bot] commented 1 year ago

DataCap and CID Checker Report[^1]

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 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.41 TiB 9.82% 13.41 TiB 0.00%
f01852023 Busan, Busan, KR
Korea Telecom		 13.94 TiB 10.21% 13.94 TiB 0.00%
f01851482 Busan, Busan, KR
Korea Telecom		 13.16 TiB 9.64% 13.16 TiB 0.00%
f01852664 Singapore, Singapore, SG
StarHub Ltd		 13.88 TiB 10.17% 13.88 TiB 0.00%
f01852677 Morrisville, North Carolina, US
TierPoint, LLC		 13.88 TiB 10.17% 13.88 TiB 0.00%
f01969202 London, England, GB
Zenlayer Inc		 14.56 TiB 10.67% 14.56 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.66 TiB 10.01% 13.66 TiB 0.00%
f01964002 Kuala Lumpur, Kuala Lumpur, MY
Zenlayer Inc		 13.28 TiB 9.73% 13.28 TiB 0.00%
f01964073 Jakarta, Jakarta, ID
Zenlayer Inc		 12.50 TiB 9.16% 12.50 TiB 0.00%

Provider Distribution

Deal Data Replication

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

✔️ Data replication looks healthy.

Unique Data Size Total Deals Made Number of Providers Deal Percentage
1.44 TiB 1.44 TiB 1 1.05%
672.00 GiB 1.31 TiB 2 0.96%
448.00 GiB 1.31 TiB 3 0.96%
2.59 TiB 10.38 TiB 4 7.60%
24.41 TiB 122.03 TiB 5 89.42%

Replication Distribution

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

C00kies77 commented 1 year ago

checker:manualTrigger

filplus-checker-app[bot] commented 1 year ago

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.

github-actions[bot] commented 1 year ago

This application has not seen any responses in the last 10 days. This issue will be marked with Stale label and will be closed in 4 days. Comment if you want to keep this application open.

github-actions[bot] commented 1 year ago

This application has not seen any responses in the last 14 days, so for now it is being closed. Please feel free to contact the Fil+ Gov team to re-open the application if it is still being processed. Thank you!

Swift-scouts commented 9 months ago

Can you open this issue please? @Sunnyiscoming