Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DataCap Application] <zinc15 > <2024-06-21T05:04:25.948Z> #39

Open
martapiekarska opened this issue Jun 21, 2024 · 18 comments
Open

[DataCap Application] <zinc15 > <2024-06-21T05:04:25.948Z> #39

martapiekarska opened this issue Jun 21, 2024 · 18 comments

Comments

@martapiekarska
Copy link

martapiekarska commented Jun 21, 2024

Version

2024-06-21T05:04:25.948Z

DataCap Applicant

@dos2un1x

Data Owner Name

zinc15

Data Owner Country/Region

Life Science / Healthcare

Website

zinc15.docking.org

Social Media Handle

https://registry.opendata.aws/zinc15/

Social Media Type

Slack

What is your role related to the dataset

Other

Total amount of DataCap being requested

5PiB

Expected size of single dataset (one copy)

989TiB

Number of replicas to store

4

Weekly allocation of DataCap

1PiB

On-chain address for first allocation

f1deu3dtpvqphtovt2rzwppla2ikkzx334lhtpfpy

Data Type of Application

Public, Open Dataset (Research/Non-Profit)

Identifier

Share a brief history of your project and organization

Welcome to ZINC15, a research tool for ligand discovery, chemical biology and pharmacology. We don't believe documentation should be necessary. Our goal is to make ZINC so blindingly obvious to use that it requires none.

Is this project associated with other projects/ecosystem stakeholders?

No

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

3D models for molecular docking screens.

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

If you are a data preparer. What is your location (Country/Region)

Singapore

If you are a data preparer, how will the data be prepared? Please include tooling used and technical details?

If you are not preparing the data, who will prepare the data? (Provide name and business)

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.

Please share a sample of the data

sudo aws s3 ls --no-sign-request s3://zinc3d/ --recursive --human-readable --summarize | grep Total
Total Objects: 5840977
Total Size: 989.7 TiB

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

Confirm

If you chose not to confirm, what was the reason

What is the expected retrieval frequency for this data

Yearly

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, Africa, North America, South America, Europe, Australia (continent), Antarctica

How will you be distributing your data to storage providers

Cloud storage (i.e. S3)

How did you find your storage providers

Slack, Partners, Others

If you answered "Others" in the previous question, what is the tool or platform you used

Please list the provider IDs and location of the storage providers you will be working with.

1.f02837226 UK
2.f02864300 US
3.f02894286 KR
4.f02870401 ID

How do you plan to make deals to your storage providers

Boost client

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

Can you confirm that you will follow the Fil+ guideline

Yes

Copy link
Contributor

datacap-bot bot commented Jun 21, 2024

Application is waiting for allocator review

@kevzak
Copy link
Contributor

kevzak commented Jun 21, 2024

Hello @dos2un1x

Can you list SP Entity names for each SP.
1.f02837226 UK
2.f02864300 US
3.f02894286 KR
4.f02870401 ID
These SPs are not prepared to provide retrievals. Please confirm or choose other SPs

Copy link
Contributor

datacap-bot bot commented Jun 21, 2024

@kevzak
Copy link
Contributor

kevzak commented Jun 21, 2024

Also we're asking you to complete a gitcoin KYC check above @dos2un1x

The other KYC option is

  • go to filplus.storage
  • Log in with your github account (top right corner)
  • Click on your Profile Icon (Next to a bell icon)
  • Choose "Confirm Identity"
  • Scroll to about middle of the page and follow an external link to togggle third party check.
  • You will need a mobile phone, and an ID.

Copy link
Contributor

datacap-bot bot commented Jun 25, 2024

KYC completed for client address f1deu3dtpvqphtovt2rzwppla2ikkzx334lhtpfpy with Optimism address 0xA2011DC10c4eB5db5600ccC91AB40da093f69897 and passport score 30.

@dos2un1x
Copy link

@kevzak Dear Notary, our KYC has been completed. I need your signature. Thank you!

@kevzak
Copy link
Contributor

kevzak commented Jun 27, 2024

Hi @dos2un1x - KYC is confirmed.

Please reply to this request before we can begin: #39 (comment)

You need to confirm SPs that meet retrieval requirements upfront. Thanks.

@dos2un1x
Copy link

Hi @dos2un1x - KYC is confirmed.

Please reply to this request before we can begin: #39 (comment)

You need to confirm SPs that meet retrieval requirements upfront. Thanks.

I have discussed this issue with SPs, and they support Graphsync/HTTP retrieval mode.
We will also add new SPs later to ensure data distribution.

@kevzak
Copy link
Contributor

kevzak commented Jul 1, 2024

Please provide SP entity information @dos2un1x

#39 (comment)

@dos2un1x
Copy link

dos2un1x commented Jul 4, 2024

1.f02837226 UK Jerry fuqiancheng@kinghash.com kinghash
2.f02864300 US miaozi Cordarell@chainup.com chainup
3.f02894286 KR Lee karl@hs88.kr HS88
4.f02870401 ID akcd4040 Jordan@bitwind.com bitwind

Copy link
Contributor

datacap-bot bot commented Jul 7, 2024

Datacap Request Trigger

Total DataCap requested

5PiB

Expected weekly DataCap usage rate

DataCap Amount - First Tranche

50TiB

Client address

f1deu3dtpvqphtovt2rzwppla2ikkzx334lhtpfpy

Copy link
Contributor

datacap-bot bot commented Jul 7, 2024

DataCap Allocation requested

Multisig Notary address

Client address

f1deu3dtpvqphtovt2rzwppla2ikkzx334lhtpfpy

DataCap allocation requested

50TiB

Id

5c52eb6e-c375-4972-94de-f369ec4de17a

Copy link
Contributor

datacap-bot bot commented Jul 7, 2024

Application is ready to sign

Copy link
Contributor

datacap-bot bot commented Jul 7, 2024

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacedwrmmlacqd33224ykbcdggz7sum7puvfkci7y5ke4mjqkixwju44

Address

f1deu3dtpvqphtovt2rzwppla2ikkzx334lhtpfpy

Datacap Allocated

50TiB

Signer Address

f1v24knjbqv5p6qrmfjj5xmlaoddzqnon2oxkzkyq

Id

5c52eb6e-c375-4972-94de-f369ec4de17a

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

Copy link
Contributor

datacap-bot bot commented Jul 7, 2024

Application is Granted

@kevzak
Copy link
Contributor

kevzak commented Jul 7, 2024

OK @dos2un1x - 50Tibs was allocated - let's see matching SP and retrievals. Thank you

@dos2un1x
Copy link

@kevzak Hi, dear notary, when can we start the next round?The first round is so small!

Copy link
Contributor

datacap-bot bot commented Jul 12, 2024

Issue has been modified. Changes below:

(OLD vs NEW)

State: ChangesRequested vs Granted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants