[DataCap Application] 1000 Genomes Phase 3

[Yazidys]

Data Owner Name

International Genome (EMBL-EBI)

Data Owner Country/Region

United Kingdom

Data Owner Industry

Life Science / Healthcare

Website

https://www.internationalgenome.org/category/phase-3/

Social Media

https://www.ebi.ac.uk/
https://www.facebook.com/illuminainc
https://www.instagram.com/illuminainc/

Total amount of DataCap being requested

5PiB

Weekly allocation of DataCap requested

500TiB

On-chain address for first allocation

f153qu3d3bv2a2imsaicqc37un7krbba7btx73pwq

Custom multisig

• Use Custom Multisig

Identifier

No response

Share a brief history of your project and organization

At Illumina, our goal is to apply innovative technologies to the analysis of genetic variation and function, making studies possible that were not even imaginable just a few years ago. It is mission critical for us to deliver innovative, flexible, and scalable solutions to meet the needs of our customers. As a global company that places high value on collaborative interactions, rapid delivery of solutions, and providing the highest level of quality, we strive to meet this challenge.

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

This dataset contains alignment files and short nucleotide, copy number, repeat expansion (STR) and structural variant call files from the 1000 Genomes Project Phase 3 dataset (n=3202) using Illumina DRAGEN v3.5.7b and v3.7.6 software.

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

How do you plan to prepare the dataset

lotus

If you answered "other/custom tool" in the previous question, enter the details here

No response

Please share a sample of the data

https://registry.opendata.aws/ilmn-dragen-1kgp/

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

Yearly

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

1.5 to 2 years

In which geographies do you plan on making storage deals

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

How will you be distributing your data to storage providers

Cloud storage (i.e. S3), HTTP or FTP server, Shipping hard drives

How do you plan to choose storage providers

Big data exchange

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

No response

How do you plan to make deals to your storage providers

Boost client, 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

[large-datacap-requests]

Thanks for your request!

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

[large-datacap-requests]

Thanks for your request!
Everything looks good. 👌

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

[lvschouwen]

@Yazidys
So what makes this LDN different then #1549 and #485 ?

[Sunnyiscoming]

Datacap Request Trigger

Total DataCap requested

5PiB

Expected weekly DataCap usage rate

500TiB

Client address

f153qu3d3bv2a2imsaicqc37un7krbba7btx73pwq

[large-datacap-requests]

DataCap Allocation requested

Multisig Notary address

f02049625

Client address

f153qu3d3bv2a2imsaicqc37un7krbba7btx73pwq

DataCap allocation requested

250TiB

Id

329c7b75-671b-47ba-b793-122ade7c4edf

[Yazidys]

@lvschouwen My application is indeed different with these application. We just chose the same public dataset to store.

[cryptowhizzard]

Dear applicant,

Thank you for applying for datacap. As Filecoin FIL+ notary i am screening your application and conducting due diligence.

As last question i would like you to fill out this form to provide us with the necessary information to make a educated decision on your LDN request if we would like to support it.

Thanks!

[lvschouwen]

@lvschouwen My application is indeed different with these application. We just chose the same public dataset to store.

To what point?
This public dataset is already stored on Filecoin in countless replica's all over the world.
What would the point be storing the same dataset once again on Filecoin?

[Yazidys]

@lvschouwen
First, it is public data on AWS. Everyone has right to store it.
Second, before I applied, I don't know that there's other applications which used this dataset. But, why can't I store and use it for this application while you can? This probably doesn't make sense.
Hey! Let‘s focus on ourselves and let the world be filled with peace and love.

[herrehesse]

@Yazidys

Please note that we cannot support your request to store the same dataset on Filecoin again, as it has already been stored 10 or more times on chain. The purpose of the datacap from the Filecoin+ program is to enhance the value of the Filecoin network, and duplicating data multiple times (20-100x) does not contribute to that goal.

While you are entitled to store your data on Filecoin, we encourage you to find a dataset that has not been stored on chain multiple times. Therefore, we cannot provide support for storing this dataset since it has already been stored multiple times.

Thank you for your understanding.

[Destore2023]

We can Support your request.

[Destore2023]

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacedzrsj2bfjorrtz7po7psfpmptl7xztvaeje3kro4ayhdwahfe3bu

Address

f153qu3d3bv2a2imsaicqc37un7krbba7btx73pwq

Datacap Allocated

250.00TiB

Signer Address

f1yh6q3nmsg7i2sys7f7dexcuajgoweudcqj2chfi

Id

329c7b75-671b-47ba-b793-122ade7c4edf

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

[lvschouwen]

We can Support your request.

How ... ?

[herrehesse]

Tagging for visibility: @Sunnyiscoming @raghavrmadya @dkkapur @galen-mcandrew @cryptowhizzard

The notary above @swatchliu will be added to our list of notaries who are on dispute. We can not tolerate this behaviour any longer. filecoin-project/notary-governance#826

Revoke your signature immediately @swatchliu.

[Destore2023]

@lvschouwen Every notary has an independent view, this is an open web3 community, not yours. IMO, it's a very normal application and does not violate any rules. Please leave voluntarily for any unreasonable behavior that interferes with my signature.

@Yazidys ,please find another notary to sign. If some guys make trouble again, you can complain about them on salck.

[lvschouwen]

@swatchliu I can choice where to reply to or not.
I do not need your opinion.

[large-datacap-requests]

DataCap Allocation requested

Request number 4

Multisig Notary address

f02049625

Client address

f153qu3d3bv2a2imsaicqc37un7krbba7btx73pwq

DataCap allocation requested

1.95PiB

Id

8c70f23b-d04d-4023-ac08-d8df8b8a612a

[large-datacap-requests]

Stats & Info for DataCap Allocation

Multisig Notary address

f02049625

Client address

f153qu3d3bv2a2imsaicqc37un7krbba7btx73pwq

Rule to calculate the allocation request amount

400% of weekly dc amount requested

DataCap allocation requested

1.95PiB

Total DataCap granted for client so far

909494701772928712704.0YiB

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

909494701772928712704.0YiB

Stats

Number of deals	Number of storage providers	Previous DC Allocated	Top provider	Remaining DC
36117	16	1000.0TiB	22.72	245.71TiB

[spaceT9]

checker:manualTrigger

[filplus-checker-app]

DataCap and CID Checker Report Summary¹

Retrieval Statistics

⚠️ All retrieval success ratios are below 1%.

• Overall Graphsync retrieval success rate: 0.00%
• Overall HTTP retrieval success rate: 0.00%
• Overall Bitswap retrieval success rate: 0.00%

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

⚠️ 31.26% of deals are for data replicated across less than 4 storage providers.

Deal Data Shared with other Clients²

✔️ No CID sharing has been observed.

Full report

Click here to view the CID Checker report.
Click here to view the Retrieval 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> ... ↩

[spaceT9]

Please increase the retrieval rate before next tranche

[github-actions]

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.

[Yazidys]

checker:manualTrigger

[filplus-checker-app]

DataCap and CID Checker Report Summary¹

Retrieval Statistics

• Overall Graphsync retrieval success rate: 0.00%
• Overall HTTP retrieval success rate: 1.57%
• Overall Bitswap retrieval success rate: 0.00%

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

⚠️ 31.26% of deals are for data replicated across less than 4 storage providers.

Deal Data Shared with other Clients²

✔️ No CID sharing has been observed.

Full report

Click here to view the CID Checker report.
Click here to view the Retrieval Dashboard.
Click here to view the Retrieval 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> ... ↩

[Yazidys]

@spaceT9 OK. We're working on it.

[cryptowhizzard]

Seems like all the SP's you have been working with have been flagged for Abuse/Cid sharing and non-retrievability against rules and guidelines of Fil+.

Can you explain?

[github-actions]

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]

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!