filecoin-plus-large-datasets [DataCap Application] Kernelogic - Open datasets onboarding initiative phase 1 (4/4)

Data Owner Name

Kernelogic

Data Owner Country/Region

Canada

Data Owner Industry

Life Science / Healthcare

Website

https://singularity-browser.kernelogic.ca

Social Media

N/A

Total amount of DataCap being requested

5PiB

Weekly allocation of DataCap requested

1PiB

On-chain address for first allocation

f1z6yigcbg6x7c2o4wasp5vya3jzr63jdjqnzvldi

Custom multisig

[ ] Use Custom Multisig

Identifier

No response

Share a brief history of your project and organization

I have participated every Slingshot phase and is probably the best performing as a "small individual client". 

Even though Slingshot v2 has ended, there are still strong demand from SPs to onboard useful data. This application is to onboard open dataset from AWS.

I have a web UI (https://singularity-browser.kernelogic.ca/) to index all files onboarded and provide ways to retrieve.

I have successfully completed a few LDNs on other datasets and I have record to show I have been following the rules of decentralization and have zero self dealing.

Some of the recent LDNs I completed:
https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1108
https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1107
https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1106
https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1104
https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/983

Is this project associated with other projects/ecosystem stakeholders?

Yes

If answered yes, what are the other projects/ecosystem stakeholders

Storage working groups, BigD exchange, singularity deal making tool.

Describe the data being stored onto Filecoin

Because each LDN requires a separate client address in order for the bot to work properly, in order to onboard more data more smoothly, I am kicking off a series of various open dataset onboarding LDNs to onboard new AWS open datasets that I have not done before. Including but not limited to:

Allen Mouse Brain Atlas
Community Earth System Model Large Ensemble (CESM LENS)
Community Earth System Model v2 Large Ensemble (CESM2 LENS)
Epoch of Reionization Dataset
HIRLAM Weather Model
NIH NCBI Sequence Read Archive (SRA) on AWS
NOAA Global Ensemble Forecast System (GEFS)
NOAA Fundamental Climate Data Records (FCDR)
NOAA Joint Polar Satellite System (JPSS)

All these datasets will be indexed for easy lookup through my website https://singularity-browser.kernelogic.ca

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

singularity

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/allen-mouse-brain-atlas/
https://registry.opendata.aws/ncar-cesm-lens/
https://registry.opendata.aws/epoch-of-reionization/

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

[X] 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

1 to 1.5 years

In which geographies do you plan on making storage deals

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

How will you be distributing your data to storage providers

HTTP or FTP server

How do you plan to choose storage providers

Slack, Big data exchange, 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

No response

How do you plan to make deals to your storage providers

No response

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

Feb 22 '23 02:02 kernelogic

Dear Filecoin+ Github applicant,

We have noticed that some of you are submitting merged datacap requests for datasets that are already (partly) on the chain. While we appreciate your enthusiasm to contribute to the Filecoin network, we want to remind you that this behaviour may not be beneficial to the network in the long run. In fact, this behaviour has been questioned and discussed in issue #832 on the Filecoin notary-governance Github repository.

We encourage you to review the discussions in issue #832. It's important to ensure that your datacap requests are valid, necessary, and add value to the network. By doing so, you can help to maintain the integrity and sustainability of the Filecoin network.

You can find the link to issue #832 here: filecoin-project/notary-governance#832

Thank you for your understanding and cooperation.

Feb 22 '23 10:02 herrehesse

In my defence I provide a better browser for data indexing per dataset than fil-plus bots. It is capable to show what's being stored in each dataset in detail.

With that being said, I am also willing to follow the decision on your proposal https://github.com/filecoin-project/notary-governance/issues/832 should it get accepted.

Feb 23 '23 01:02 kernelogic

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

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

Feb 23 '23 01:02 large-datacap-requests[bot]

See questions in https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1638.

Mar 02 '23 13:03 Sunnyiscoming

Datacap Request Trigger

Total DataCap requested

5PiB

Expected weekly DataCap usage rate

1PiB

Client address

f1z6yigcbg6x7c2o4wasp5vya3jzr63jdjqnzvldi

Mar 04 '23 02:03 Sunnyiscoming

DataCap Allocation requested

Multisig Notary address

f02049625

Client address

f1z6yigcbg6x7c2o4wasp5vya3jzr63jdjqnzvldi

DataCap allocation requested

256TiB

Id

c2abd943-79ff-403e-bf1a-3b502c011f09

Mar 04 '23 02:03 large-datacap-requests[bot]

Related proposal https://github.com/filecoin-project/notary-governance/issues/832 Hope more notaries review this application and comment on this proposal.

Mar 04 '23 02:03 Sunnyiscoming

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacedye5o2xvurn5v2qvni2ibu2yjrbyfqoh2td7iuukly5y4pvuffp6

Address

f1z6yigcbg6x7c2o4wasp5vya3jzr63jdjqnzvldi

Datacap Allocated

256.00TiB

Signer Address

f1krmypm4uoxxf3g7okrwtrahlmpcph3y7rbqqgfa

Id

c2abd943-79ff-403e-bf1a-3b502c011f09

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

Mar 04 '23 08:03 cryptowhizzard

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzaced2upz7rdd5oimzw3plkt63t3occxqjm5errfgf5hpptflgqebyn6

Address

f1z6yigcbg6x7c2o4wasp5vya3jzr63jdjqnzvldi

Datacap Allocated

256.00TiB

Signer Address

f1bp3tzp536edm7dodldceekzbsx7zcy7hdfg6uzq

Id

c2abd943-79ff-403e-bf1a-3b502c011f09

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

Mar 06 '23 02:03 laurarenpanda

checker:manualTrigger

May 20 '23 16:05 kernelogic

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]

⚠️ CID sharing has been observed. (Top 3)

30.44 TiB - f1qvbe2vppq7jqo3umkl3rnx4uggkxtxi6f7f2zgi - Kernelogic
22.22 TiB - f1rylwniokpxpziavwvtvf7qgbj6p23iqgfu26iea - Kernelogic
19.31 TiB - f1yvbub3wqjcd2bkayk72ace3fopgxog6ix36l7ka - Kernelogic

[^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.

May 20 '23 16:05 filplus-checker-app[bot]

DataCap Allocation requested

Request number 2

Multisig Notary address

f02049625

Client address

f1z6yigcbg6x7c2o4wasp5vya3jzr63jdjqnzvldi

DataCap allocation requested

512TiB

Id

83abdd55-d56f-4619-bb0e-17dd7be680ad

May 23 '23 02:05 large-datacap-requests[bot]

Stats & Info for DataCap Allocation

Multisig Notary address

f02049625

Client address

f1z6yigcbg6x7c2o4wasp5vya3jzr63jdjqnzvldi

Rule to calculate the allocation request amount

10% of total dc amount requested

DataCap allocation requested

512TiB

Total DataCap granted for client so far

256TiB

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

4.75PiB

Stats

Number of deals	Number of storage providers	Previous DC Allocated	Top provider	Remaining DC
5650	4	256TiB	39.08	68.28TiB

May 23 '23 02:05 large-datacap-requests[bot]

checker:manualTrigger

May 25 '23 06:05 sxxfuture-official

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]

⚠️ CID sharing has been observed. (Top 3)

70.88 TiB - f1rylwniokpxpziavwvtvf7qgbj6p23iqgfu26iea - Kernelogic
68.81 TiB - f1yvbub3wqjcd2bkayk72ace3fopgxog6ix36l7ka - Kernelogic
38.06 TiB - f1qvbe2vppq7jqo3umkl3rnx4uggkxtxi6f7f2zgi - Kernelogic

[^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.

May 25 '23 06:05 filplus-checker-app[bot]

CID Checker looks healthy.

May 25 '23 06:05 sxxfuture-official

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzaceah7gs7ghvk7c5gk6bqh57ggyucnm6675bngoblc3dovgoljmx5du

Address

f1z6yigcbg6x7c2o4wasp5vya3jzr63jdjqnzvldi

Datacap Allocated

512.00TiB

Signer Address

f1foiomqlmoshpuxm6aie4xysffqezkjnokgwcecq

Id

83abdd55-d56f-4619-bb0e-17dd7be680ad

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

May 25 '23 06:05 sxxfuture-official

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacebcnyup72b3dkruwyoi35jy7t7bhj2qyubzw464idws4fc4xo7w7q

Address

f1z6yigcbg6x7c2o4wasp5vya3jzr63jdjqnzvldi

Datacap Allocated

512.00TiB

Signer Address

f12mckci3omexgzoeosjvstcfxfe4vqw7owdia3da

Id

83abdd55-d56f-4619-bb0e-17dd7be680ad

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

May 25 '23 07:05 SuperChaiChai

checker:manualTrigger

Jul 13 '23 08:07 herrehesse

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

⚠️ All retrieval success ratios are below 1%.

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

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^3]

⚠️ CID sharing has been observed. (Top 3)

774.59 TiB - f1yvbub3wqjcd2bkayk72ace3fopgxog6ix36l7ka - Kernelogic
276.63 TiB - f1qvbe2vppq7jqo3umkl3rnx4uggkxtxi6f7f2zgi - Kernelogic
264.06 TiB - f1rylwniokpxpziavwvtvf7qgbj6p23iqgfu26iea - Kernelogic

[^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> ...