[DataCap Application] AWS-ENCODE

[alyssa32M]

Data Owner Name

NHGRI

Data Owner Country/Region

United States

Data Owner Industry

Life Science / Healthcare

Website

https://www.encodeproject.org/

Social Media Handle

Alyssa

Social Media Type

Slack

What is your role related to the dataset

Data Preparer

Total amount of DataCap being requested

5PiB

Expected size of single dataset (one copy)

1.32PiB

Number of replicas to store

8

Weekly allocation of DataCap requested

1PiB

On-chain address for first allocation

f17h6wblshweb7uj4ijxkdroqsdjcl7qijjzi6n3i

Data Type of Application

Public, Open Dataset (Research/Non-Profit)

Custom multisig

• Use Custom Multisig

Identifier

No response

Share a brief history of your project and organization

Project-The ENCODE Consortium not only produces high-quality data, but also analyzes the data in an integrative fashion. The ENCODE Encyclopedia organizes the most salient analysis products into annotations and provides tools to search and visualize them.
organization-We are a web3 organization named dataup. We help data owner to store data.

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

ENCODE investigators employ a variety of assays and methods to identify functional elements. The discovery and annotation of gene elements is accomplished primarily by sequencing a diverse range of RNA sources, comparative genomics, integrative bioinformatic methods, and human curation. Regulatory elements are typically investigated through DNA hypersensitivity assays, assays of DNA methylation, and immunoprecipitation (IP) of proteins that interact with DNA and RNA, i.e., modified histones, transcription factors, chromatin regulators, and RNA-binding proteins, followed by sequencing.

Where was the data currently stored in this dataset sourced from

AWS Cloud

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?

We use Lotus to prepare data. We transfer car files to SPs.

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.

No response

Please share a sample of the data

aws s3 ls --no-sign-request s3://encode-public/

Confirm that this is a public dataset that can be retrieved by anyone on the Network

• I confirm

If you chose not to confirm, what was the reason

No response

What is the expected retrieval frequency for this data

Sporadic

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

More than 3 years

In which geographies do you plan on making storage deals

Greater China, Asia other than Greater China, North America, South America

How will you be distributing your data to storage providers

HTTP or FTP server, Shipping hard drives, Lotus built-in data transfer

How did you find your storage providers

Slack

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.

f03100009 Hong Kong
f01084941 Hong Kong
f03100002 Shenzhen
f03100000 Shenzhen
f01975299 Shenzhen
f01084413 Changsha
f03161261 New York
f03192503 Hong Kong
f03189917 Dulles

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

[datacap-bot]

Application is waiting for allocator review

[alyssa32M]

@luhong123 Dear allocator, this is my application. Please give us feedback. Thank you.

[luhong123]

Please read the contents of filecoin-project/notary-governance#1071 (comment) for details on the rule, thank you!

[luhong123]

If you don't need any help,Please pay a total of 101 FIL to f1apw6of55wzdbpjpnnyenv56ensi4iisaxgmigzi for information verification (1 FIL) and data pledge fees (100 FIL).

[luhong123]

1. Are you uploading this open data on behalf of an individual or a company?
2. Are the data as well as the SP sealed ready?
3. Do all SPs support retrieval or spark retrieval？

[alyssa32M]

@luhong123 Dear allocator, we've read all contents you provided to me, thank you.

We've paid Fil to your account, please check it.

We are a web3 organization and I'm the op of our organization.
Yes, we have stored this dataset in our servers. The sps in our application are ready for our deals. If we have more sps to cooperation, we will provide the update to you.
Yes, we provided spark retrieval rules to sps and they have updated their code. We will keep focusing on their ability of retrieval.

[luhong123]

f01843994 US

Please provide proof of the geographic location of the SPs to [email protected]

[alyssa32M]

@luhong123 OK. I have sent it.

[luhong123]

confirmed

[datacap-bot]

Datacap Request Trigger

Total DataCap requested

5PiB

Expected weekly DataCap usage rate

1PiB

DataCap Amount - First Tranche

256TiB

Client address

f17h6wblshweb7uj4ijxkdroqsdjcl7qijjzi6n3i

[datacap-bot]

DataCap Allocation requested

Multisig Notary address

Client address

f17h6wblshweb7uj4ijxkdroqsdjcl7qijjzi6n3i

DataCap allocation requested

256TiB

Id

261c2300-e5ea-4d05-8290-e7a299df42dd

[datacap-bot]

Application is ready to sign

[datacap-bot]

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzaceaomqclzsf6zpoihf7kalpli2klmacld2svrokzfxp3hu3qeskc2c

Address

f17h6wblshweb7uj4ijxkdroqsdjcl7qijjzi6n3i

Datacap Allocated

256TiB

Signer Address

f1apw6of55wzdbpjpnnyenv56ensi4iisaxgmigzi

Id

261c2300-e5ea-4d05-8290-e7a299df42dd

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

[datacap-bot]

Application is Granted

[datacap-bot]

Client used 75% of the allocated DataCap. Consider allocating next tranche.

[luhong123]

checker:manualTrigger

[datacap-bot]

DataCap and CID Checker Report Summary¹

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

⚠️ 50.00% of Storage Providers have retrieval success rate less than 75%.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients²

✔️ No CID sharing has been observed.

Full report

Click here to view the CID Checker report.

Footnotes

1. To manually trigger this report, add a comment with text checker:manualTrigger ↩

2. To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ... ↩

[luhong123]

Nice retrieval rate.

But it doesn't match what was first disclosed, so please confirm the SP you're working with and rework it!

[alyssa32M]

@luhong123 Dear allocator, sorry for the late reply.
When we were ready to distribute the data to the sp in our original plan, they were temporarily unable to help us with the packaging due to some update about their machines. We then contacted other sps that met the requirements to work with us first.
We will continue to reach out to more sp's to get involved, and will make sure that the retrieval rate and the number of sps under the standard. We will give you the list as soon.
Please give us a chance to improve our process and give us one more round of datacap. Thank you!

[luhong123]

Got it

@luhong123 Dear allocator, I noticed that the retrieval results for the new sps added to the list are not very good at the moment. I've already communicated with sps, and they promise to show better results in the next cid report. Also, I've got experience with previous sp's that I've worked with to share with new ones. Better results will be shown in subsequent reports.

[luhong123]

Number of replicas to store
4

The current number of copies is 8. Please confirm.

[luhong123]

2 storage providers sealed too much duplicate data - f03161261: 49.88%, f03189917: 49.89%

Same bug.
fidlabs/allocator-tooling#73

[luhong123]

Two retrievals are good so far, will be watching for changes in retrieval rates and hope to see good retrievals before the next round is triggered

[datacap-bot]

Issue information change request has been approved.

[datacap-bot]

Application is in Refill

[datacap-bot]

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacectzxp4yvrv35ornckpza4f6pcyk7vt6wx2chm5nexkfxm4yjzcom

Address

f17h6wblshweb7uj4ijxkdroqsdjcl7qijjzi6n3i

Datacap Allocated

1PiB

Signer Address

f1apw6of55wzdbpjpnnyenv56ensi4iisaxgmigzi

Id

45001a57-53b3-4812-b122-9cc7af3e23ef

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

[datacap-bot]

Application is Granted

[datacap-bot]

Issue has been modified. Changes below:

(OLD vs NEW)

Replicas: 8 vs 4
State: ChangesRequested vs Granted

[luhong123]

checker:manualTrigger

[datacap-bot]

DataCap and CID Checker Report Summary¹

Storage Provider Distribution

⚠️ 2 storage providers sealed too much duplicate data - f03161261: 45.06%, f03189917: 41.37%

⚠️ 27.27% of Storage Providers have retrieval success rate equal to zero.

⚠️ 81.82% of Storage Providers have retrieval success rate less than 75%.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients²

✔️ No CID sharing has been observed.

Full report

Click here to view the CID Checker report.

Footnotes

1. To manually trigger this report, add a comment with text checker:manualTrigger ↩

2. To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ... ↩

[luhong123]

checker:manualTrigger

[datacap-bot]

DataCap and CID Checker Report Summary¹

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

⚠️ 27.27% of Storage Providers have retrieval success rate equal to zero.

⚠️ 72.73% of Storage Providers have retrieval success rate less than 75%.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients²

✔️ No CID sharing has been observed.

Full report

Click here to view the CID Checker report.

Footnotes

1. To manually trigger this report, add a comment with text checker:manualTrigger ↩

2. To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ... ↩

[luhong123]

Multiple occurrences of undisclosed SPs, although the retrieval rate is good, it violates the relevant rules, please give a reasonable explanation, or else consider suspending the distribution of datacap

[alyssa32M]

@luhong123 Dear allocator, that is because sps have some different plan that delayed our process, we've just have to find new sps to work.

[luhong123]

Repeated failure to disclose information about SPs in advance and inconsistencies with the information provided in the application.
The issue is closed.