search

joshua-ne / FIL_DC_Allocator_1022

This repo serves as a bookkeeping tool for DC allocation from Allocator_1022
0 stars 0 forks source link

[DataCap Application] <Byte Tunneling> - <ByteTunneling_data_store_bc_fil_01> #39

Open ws1214921 opened 3 weeks ago

ws1214921 commented 3 weeks ago

Version

1

DataCap Applicant

Byte Tunneling

Project ID

ByteTunneling_data_store_bc_fil_01

Data Owner Name

European Organization for Nuclear Research

Data Owner Country/Region

Switzerland

Data Owner Industry

Other

Website

https://opendata.cern.ch/

Social Media Handle

https://x.com/cernopendata

Social Media Type

Twitter

What is your role related to the dataset

Data Preparer

Total amount of DataCap being requested

5 PiB

Expected size of single dataset (one copy)

1 PiB

Number of replicas to store

5

Weekly allocation of DataCap requested

1000 TiB

On-chain address for first allocation

f1a67akstc5ksz6q5jiaumnabmk7svdbcmqwk3axa

Data Type of Application

Public, Open Dataset (Research/Non-Profit)

Custom multisig

Identifier

No response

Share a brief history of your project and organization

Byte Tunneling was founded in 2020 with a mission to facilitate open scientific research by preparing and managing large-scale datasets. With a background in handling high-energy physics data, Byte Tunneling has been trying to collaborate with global research institutions to prepare and organize public 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

CERN Open Data is provided by CERN, the European Organization for Nuclear Research. The datasets contain high-energy physics data collected from experiments conducted at the Large Hadron Collider (LHC). These datasets include raw and processed collision data, simulations, and supporting materials for educational and research purposes.

Where was the data currently stored in this dataset sourced from

Other

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)

Singapore

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

A partner we met at a meetup provided tools that were re-engineered using components from IPFS.

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.

Please share a sample of the data

https://opendata.cern.ch/record/80030/files/assets/atlas/datascience/CERN-EP-2024-159/angular_000.h5.gz

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

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

Permanently

In which geographies do you plan on making storage deals

Asia other than Greater China

How will you be distributing your data to storage providers

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

How did you find your storage providers

Partners

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.

f01422327, Japan
f02252024, Japan
f02252023, Japan
f01111110, Vietnam
f01909705, Vietnam
f03215853, US
f03218576, US
f03230392, Vietnam
f03230423, Malaysia

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

No response

Can you confirm that you will follow the Fil+ guideline

Yes

datacap-bot[bot] commented 3 weeks ago

Application is waiting for allocator review

joshua-ne commented 3 weeks ago

Hi @ws1214921 , as we have done SP localization verification offline and sample checks, I have also checked online copies of your dataset. It seems to be a new set.

However, before we move on, I have a few extra questions for you:

  1. Have you or your team previously onboarded any data to the Filecoin network?
  2. The amount of Datacap you requested seems pretty large if you are new to the Filecoin network, I would recommend you adjust downward a little bit for this application and apply for more if needed later
joshua-ne commented 3 weeks ago

And can you double confirm that all the SP's you are working with shall store the unsealed files of the sectors and support public retrieval, like SPARK?

ws1214921 commented 3 weeks ago
  1. Yes, we have experience in Filecoin network and we are working with very good hands.
  2. Okay, I have made adjustment to the amount of DC requested. Please let us know if you have any other questions or concerns.
  3. We confirm that all the SP's you are working with shall store the unsealed files of the sectors and support public retrieval, like SPARK.
joshua-ne commented 3 weeks ago

Everything looks good so far. So I will start signing 50TiB of Datacap to kickoff, and we will assign more as our trust build up.

datacap-bot[bot] commented 3 weeks ago

Datacap Request Trigger

Total DataCap requested

5 PiB

Expected weekly DataCap usage rate

1000 TiB

DataCap Amount - First Tranche

50TiB

Client address

f1a67akstc5ksz6q5jiaumnabmk7svdbcmqwk3axa

datacap-bot[bot] commented 3 weeks ago

DataCap Allocation requested

Multisig Notary address

Client address

f1a67akstc5ksz6q5jiaumnabmk7svdbcmqwk3axa

DataCap allocation requested

50TiB

Id

5d1c3257-6b7f-4374-8117-3f2a9037aca4

datacap-bot[bot] commented 3 weeks ago

Application is ready to sign

datacap-bot[bot] commented 3 weeks ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacebuolsqpiirdl4jjkxe727sc7xtjlo6otr6fzxbvbsornnh4oek2g

Address

f1a67akstc5ksz6q5jiaumnabmk7svdbcmqwk3axa

Datacap Allocated

50TiB

Signer Address

f1sfffys4o2w64rdpd3alpmvpvj4ik6x2iyjsjmry

Id

5d1c3257-6b7f-4374-8117-3f2a9037aca4

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

datacap-bot[bot] commented 3 weeks ago

Application is Granted

datacap-bot[bot] commented 3 weeks ago

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

joshua-ne commented 3 weeks ago

checker:manualTrigger

datacap-bot[bot] commented 3 weeks ago

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

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

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

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 CID Checker report.

joshua-ne commented 3 weeks ago

trigger:run_retrieval_test method=lassie sp_list=f03230392,f03230423,f01422327,f02252023,f02252024 client=f1a67akstc5ksz6q5jiaumnabmk7svdbcmqwk3axa limit=10

myfil512 commented 3 weeks ago
miner_id retrieval_rate retrieval_success_counts retrieval_fail_counts
f03230392 100% 10 0
f03230423 0% 0 10
f01422327 80% 8 2
f02252023 80% 8 2
f02252024 80% 8 2
joshua-ne commented 3 weeks ago

Hey, we have some problems detected here, please explain and solve them before we can move on:

  1. Your listed SPs do not include f03230392 and f03230423, however, from our database, they are also sealing your deals. It is okay to have changes of plans, but you should always APPLY BEFORE YOU CHANGE. Please explain this and confirm that you will apply first and only send deals to SPs after the allocator's approval.

  2. f03230423 is not retrievable now, please contact the operator to repair and improve.

Please take care of the problems listed above. And without promising solutions, I will not sign the next round.

joshua-ne commented 2 weeks ago

checker:manualTrigger

datacap-bot[bot] commented 2 weeks ago

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

⚠️ 1 storage providers sealed too much duplicate data - f02252023: 21.67%

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

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

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 CID Checker report.

joshua-ne commented 2 weeks ago

trigger:run_retrieval_test method=lassie sp_list=f03230392,f03230423,f01422327,f02252023,f02252024 client=f1a67akstc5ksz6q5jiaumnabmk7svdbcmqwk3axa limit=10

myfil512 commented 2 weeks ago
miner_id retrieval_rate retrieval_success_counts retrieval_fail_counts
f03230392 100% 10 0
f03230423 100% 10 0
f01422327 80% 8 2
f02252023 80% 8 2
f02252024 80% 8 2
ws1214921 commented 2 weeks ago

Hi, thank you for your support and check.

  1. We are sorry that we did not contact beforehand about the change of SP list. We are working hard to find good SPs who can receive our data fast, support public retrieval, and can match our onboarding schedule. So there can be quite some back-and-forth in the beginning stage. But I promise if similar situation happens, we will applay before we change. And we have updated our applicaiton with newly added SPs, please approve. Thank you.

  2. We are working with f03230423, it seems that they lost some entries in their Yugabyte database. Hopefully they will be back online very soon. Please help with another round, so that we can improve our data.

datacap-bot[bot] commented 2 weeks ago

Issue has been modified. Changes below:

(OLD vs NEW)

Please list the provider IDs and location of the storage providers you will be working with: f01422327, Japan f02252024, Japan f02252023, Japan f01111110, Vietnam f01909705, Vietnam f03215853, US f03218576, US f03230392, Vietnam f03230423, Malaysia vs f01422327, Japan f02252024, Japan f02252023, Japan f01111110, Vietnam f01909705, Vietnam f03215853, US f03218576, US State: ChangesRequested vs Granted

datacap-bot[bot] commented 2 weeks ago

Issue information change request has been approved.

joshua-ne commented 2 weeks ago

Okay, the application for change is approved. And since you broke some rules last time, I will only sign 50TiB this round and will support more if everything checks out.

datacap-bot[bot] commented 2 weeks ago

Application is in Refill

datacap-bot[bot] commented 2 weeks ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacedhpq3uc5h5e7xp3ibt76apdexsue5dblst2gmvoaezai2nba2via

Address

f1a67akstc5ksz6q5jiaumnabmk7svdbcmqwk3axa

Datacap Allocated

50TiB

Signer Address

f1sfffys4o2w64rdpd3alpmvpvj4ik6x2iyjsjmry

Id

b0f9e854-4af4-4e3c-ae27-d8c8f74688fe

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

datacap-bot[bot] commented 2 weeks ago

Application is Granted

datacap-bot[bot] commented 2 weeks ago

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

joshua-ne commented 2 weeks ago

trigger:run_retrieval_test method=lassie sp_list=f01422327,f02252024,f02252023,f01111110,f01909705,f03215853,f03218576,f03230392,f03230423 client=f1a67akstc5ksz6q5jiaumnabmk7svdbcmqwk3axa limit=10

myfil512 commented 2 weeks ago
miner_id retrieval_rate retrieval_success_counts retrieval_fail_counts
f01422327 80% 8 2
f02252024 80% 8 2
f02252023 80% 8 2
f01111110 NA 0 0
f01909705 NA 0 0
f03215853 NA 0 0
f03218576 NA 0 0
f03230392 100% 10 0
f03230423 100% 10 0
joshua-ne commented 2 weeks ago

The retrieval rate looks okay for those SPs onboarded. 2 minor points to notice:

  1. f01111110 f01909705 f03215853 f03218576 have not been onboarded yet, are they expected to onboard soon?
  2. for the SPs located in Japan, could you ask SPs to check why the following two CIDs are not retrievable: bafybeigxdgdqnwvh3mpgy5wrvuc76orzkapgkwnyadmq4llixmq6hwj66i bafybeie47m5prigltscmh464d6fp46lk66wkzpefkjlanariuzokaepoly
joshua-ne commented 2 weeks ago

I will continue with another round of 256TiB for now.

datacap-bot[bot] commented 2 weeks ago

Application is in Refill

datacap-bot[bot] commented 2 weeks ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzaceb2hvmx6pqp67ijgs7u67qmxpd47u4jmyjwy5w7vlgkt6qxk4jbhg

Address

f1a67akstc5ksz6q5jiaumnabmk7svdbcmqwk3axa

Datacap Allocated

256TiB

Signer Address

f1sfffys4o2w64rdpd3alpmvpvj4ik6x2iyjsjmry

Id

5f00e538-f01a-46a2-b37a-3dcbbe8bc171

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

datacap-bot[bot] commented 2 weeks ago

Application is Granted

datacap-bot[bot] commented 2 weeks ago

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

ws1214921 commented 1 week ago

Hi, for your concerning questions:

  1. We have onboarded f01111110 and f01909705 over the weekend, for f03215853 and f03218576, I think we are onboarding soon, maybe next week, as they have change of plans of sealing.

  2. These two CIDs are retrievable now. I think the reason was that they haven't submitted the sector by the time you checked.

Willing to see another round of support soon, thanks!

joshua-ne commented 1 week ago

trigger:run_retrieval_test method=lassie sp_list=f01422327,f02252024,f02252023,f01111110,f01909705,f03215853,f03218576,f03230392,f03230423 client=f1a67akstc5ksz6q5jiaumnabmk7svdbcmqwk3axa limit=10

myfil512 commented 1 week ago
miner_id retrieval_rate retrieval_success_counts retrieval_fail_counts
f01422327 100% 10 0
f02252024 100% 10 0
f02252023 100% 10 0
f01111110 100% 10 0
f01909705 100% 10 0
f03215853 NA 0 0
f03218576 NA 0 0
f03230392 100% 10 0
f03230423 100% 10 0
datacap-bot[bot] commented 1 week ago

Application is in Refill

datacap-bot[bot] commented 1 week ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacebhezyxjvrgeebhsark3noo64bfo76ya6wxor5v3mbq34pnrtjojo

Address

f1a67akstc5ksz6q5jiaumnabmk7svdbcmqwk3axa

Datacap Allocated

512TiB

Signer Address

f1sfffys4o2w64rdpd3alpmvpvj4ik6x2iyjsjmry

Id

81388b5f-4cd5-4cec-8a42-7e12d84be5f8

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

datacap-bot[bot] commented 1 week ago

Application is Granted

datacap-bot[bot] commented 5 days ago

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

joshua-ne commented 4 days ago

Hi can you please submit your dataset card by the end of next week. Thank you. This will be mandatory for the following allocation of datacap.

https://github.com/joshua-ne/FIL_DC_Allocator_1022_Dataset_Card/issues/new/choose