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] <ZEN OPENDATA> - <ZOD-USGOD-1> #29

Open Dengminer opened 2 months ago

Dengminer commented 2 months ago

Version

1

DataCap Applicant

ZEN OPENDATA

Project ID

ZOD-USGOD-1

Data Owner Name

U.S. General Services Administration

Data Owner Country/Region

United States

Data Owner Industry

Government

Website

https://www.gsa.gov/

Social Media Handle

X: https://x.com/USGSA

Social Media Type

Twitter

What is your role related to the dataset

Data Preparer

Total amount of DataCap being requested

4.5 PiB

Expected size of single dataset (one copy)

900 TiB

Number of replicas to store

5

Weekly allocation of DataCap requested

600 TiB

On-chain address for first allocation

f1qtxjoxzobjmcxn3aaxn7tyj7e3p24r3d2bw3ygy

Data Type of Application

Public, Open Dataset (Research/Non-Profit)

Custom multisig

Identifier

No response

Share a brief history of your project and organization

Zen OpenData is dedicated to building an open data ecosystem, focusing on the collection, sharing, and management of data. Our organization aims to foster collaboration, transparency, and innovation by providing access to high-quality datasets. Through our initiatives, Zen OpenData empowers individuals, researchers, and organizations to leverage data for informed decision-making and problem-solving, driving progress across various sectors.

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

U.S. Government's Open Data is built by the United States Government and is designed to unleash the power of government open data to inform decisions by the public and policymakers, drive innovation and economic activity, achieve agency missions, and strengthen the foundation of an open and transparent government.

Where was the data currently stored in this dataset sourced from

My Own Storage Infra

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?

We have customized tools to retrieve and convert data to car files.

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

http://www.hud.gov/offices/cpd/systems/census/sf1/Tables.zip

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

2 to 3 years

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, IPFS, Shipping hard drives

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.

f01422327, Japan
f02252023, Japan
f02252024, Japan
f01111110, Vietnam
f01909705, Vietnam
f03224283, Japan
f03224551, Japan
f03230392, Vietnam
f03230423, Malaysia
f03232064, Malaysia
f03232134, 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 2 months ago

Application is waiting for allocator review

joshua-ne commented 2 months ago

Hi @Dengminer , as we have done SP localization verification offline and data sample checks, I have also checked online copies of your dataset. It seems to be a one that has not been stored too many times before.

Before we proceed, please do verify and confirm a few of the questions you missed in the application, like the location and the method you used to prepare your data. Besides, in terms of making deals, you mentioned "lotus client", which I think is no longer an option. Please confirm or correct this. Thanks!

joshua-ne commented 2 months ago

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

Dengminer commented 2 months ago

Thank you for your timely review! I have filled the missing questions and made the corrections you mentioned. Yes, I am sure that the SP I work with will store the unsealed sectors and support public retrieval.

joshua-ne commented 2 months ago

Looks nice, I will allocate a test amount of 256 TiB as a starter. Hope everything goes well and then we can proceed with more.

datacap-bot[bot] commented 2 months ago

Datacap Request Trigger

Total DataCap requested

4.5 PiB

Expected weekly DataCap usage rate

600 TiB

DataCap Amount - First Tranche

256TiB

Client address

f1qtxjoxzobjmcxn3aaxn7tyj7e3p24r3d2bw3ygy

datacap-bot[bot] commented 2 months ago

DataCap Allocation requested

Multisig Notary address

Client address

f1qtxjoxzobjmcxn3aaxn7tyj7e3p24r3d2bw3ygy

DataCap allocation requested

256TiB

Id

bfb26610-9cab-4849-8a70-c5c52d9ee4e3

datacap-bot[bot] commented 2 months ago

Application is ready to sign

datacap-bot[bot] commented 2 months ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzaceabq4w3ho24plxdugogh5dgpwqvuwvueygepgabs4ntuottgr372k

Address

f1qtxjoxzobjmcxn3aaxn7tyj7e3p24r3d2bw3ygy

Datacap Allocated

256TiB

Signer Address

f1sfffys4o2w64rdpd3alpmvpvj4ik6x2iyjsjmry

Id

bfb26610-9cab-4849-8a70-c5c52d9ee4e3

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

datacap-bot[bot] commented 2 months ago

Application is Granted

joshua-ne commented 2 months ago

checker:manualTrigger

datacap-bot[bot] commented 2 months ago

DataCap and CID Checker Report[^1]

No active deals found for this client.

[^1]: To manually trigger this report, add a comment with text checker:manualTrigger

joshua-ne commented 2 months ago

trigger:run_retrieval_test method=lassie sp_list=f03068013,f03035686,f01926635,f01999119,f03136267,f01422327,f02252023,f02252024,f01111110,f01909705 client=f1qtxjoxzobjmcxn3aaxn7tyj7e3p24r3d2bw3ygy limit=10

myfil512 commented 2 months ago
miner_id retrieval_rate retrieval_success_counts retrieval_fail_counts
f03068013 NA 0 0
f03035686 NA 0 0
f01926635 NA 0 0
f01999119 NA 0 0
f03136267 NA 0 0
f01422327 NA 0 0
f02252023 NA 0 0
f02252024 NA 0 0
f01111110 90% 9 1
f01909705 80% 8 2
joshua-ne commented 2 months ago

It seems only two SP's are participating the sealing right now. Are we expecting more to join any soon? @Dengminer

Dengminer commented 2 months ago

Yes, we are still working with SP's to coordinate the DC usage. Soon more will onboard! And since the amount is running low, hope you can support with more, since the retrieval of current SP's are looking good. Thanks!

datacap-bot[bot] commented 2 months ago

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

joshua-ne commented 2 months ago

trigger:run_retrieval_test method=lassie sp_list=f03068013,f03035686,f01926635,f01999119,f03136267,f01422327,f02252023,f02252024,f01111110,f01909705 client=f1qtxjoxzobjmcxn3aaxn7tyj7e3p24r3d2bw3ygy limit=10

myfil512 commented 2 months ago
miner_id retrieval_rate retrieval_success_counts retrieval_fail_counts
f03068013 NA 0 0
f03035686 NA 0 0
f01926635 NA 0 0
f01999119 NA 0 0
f03136267 NA 0 0
f01422327 80% 8 2
f02252023 80% 8 2
f02252024 80% 8 2
f01111110 100% 10 0
f01909705 100% 10 0
joshua-ne commented 2 months ago

The retrieval rate looks good! I will support with another 1PiB for the next round.

datacap-bot[bot] commented 2 months ago

Application is in Refill

datacap-bot[bot] commented 2 months ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacebpyy6vqvt56mjyqeq7wfzufyiwbhjgx4aiq4q5gdtk5oixrrxsog

Address

f1qtxjoxzobjmcxn3aaxn7tyj7e3p24r3d2bw3ygy

Datacap Allocated

1PiB

Signer Address

f1sfffys4o2w64rdpd3alpmvpvj4ik6x2iyjsjmry

Id

a7e9ae11-570d-4149-a5bb-46a643dfd6c0

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

datacap-bot[bot] commented 2 months ago

Application is Granted

datacap-bot[bot] commented 2 months ago

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

Dengminer commented 1 month ago

Hi, as we start to onboard more data now, we are working with two other SP's from Japan: f03224283, Japan f03224551, Japan

I have updated the application form with these two additional SP's. Thank you. Please support and please let me know if you have any questions.

datacap-bot[bot] commented 1 month 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: f03068013, Hongkong f03035686, Guangdong f01926635, Sichuang f01999119, Sichuang f03136267, Hongkong f01422327, Japan f02252023, Japan f02252024, Japan f01111110, Vietnam f01909705, Vietnam f03224283, Japan f03224551, Japan vs f03068013, Hongkong f03035686, Guangdong f01926635, Sichuang f01999119, Sichuang f03136267, Hongkong f01422327, Japan f02252023, Japan f02252024, Japan f01111110, Vietnam f01909705, Vietnam State: ChangesRequested vs Granted

joshua-ne commented 1 month ago

checker:manualTrigger

datacap-bot[bot] commented 1 month ago

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

⚠️ 1 storage providers sealed too much duplicate data - f01111110: 49.86%

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

⚠️ 71.43% 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 1 month ago

@Dengminer Okay, from our investigation, the duplicate data problem with f01111110 is from something wrong with the bot, the real deal info is okay from our end. Maybe you can ask this SP to contact some support to correct this.

The retrieval rate is not perfect to me, and from our offline communication, I can understand there are some problems with some of the SP's you are working with, which is fine. But please make sure that the following onboarding data are retrievable.

As a test, I will approve you with only 256TiB of Datacap, and I will approve more if the SPs behave well on this batch.

datacap-bot[bot] commented 1 month ago

Issue information change request has been approved.

datacap-bot[bot] commented 1 month ago

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

datacap-bot[bot] commented 1 month ago

Application is in Refill

joshua-ne commented 1 month ago

checker:manualTrigger

datacap-bot[bot] commented 1 month ago

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

⚠️ 1 storage providers sealed too much duplicate data - f01111110: 49.86%

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

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

⚠️ The average retrieval success rate is 5.90%

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 1 month ago

trigger:run_retrieval_test method=lassie sp_list=f03224283,f03224551 client=f1qtxjoxzobjmcxn3aaxn7tyj7e3p24r3d2bw3ygy limit=10

myfil512 commented 1 month ago
miner_id retrieval_rate retrieval_success_counts retrieval_fail_counts
f03224283 100% 10 0
f03224551 100% 10 0
joshua-ne commented 1 month ago

checker:manualTrigger

datacap-bot[bot] commented 1 month ago

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

⚠️ 1 storage providers sealed too much duplicate data - f01111110: 49.86%

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

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

⚠️ The average retrieval success rate is 8.97%

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 1 month ago

trigger:run_retrieval_test method=lassie sp_list=f03068013,f03035686,f01926635,f01999119,f03136267,f01422327,f02252023,f02252024,f01111110,f01909705,f03224283,f03224551 client=f1qtxjoxzobjmcxn3aaxn7tyj7e3p24r3d2bw3ygy limit=10 start_datetime="2024-08-01 00:00:00" end_datetime="2024-10-15 00:00:00"

myfil512 commented 1 month ago
miner_id retrieval_rate retrieval_success_counts retrieval_fail_counts
f03068013 NA 0 0
f03035686 NA 0 0
f01926635 NA 0 0
f01999119 NA 0 0
f03136267 NA 0 0
f01422327 80% 8 2
f02252023 80% 8 2
f02252024 80% 8 2
f01111110 0% 0 10
f01909705 0% 0 10
f03224283 100% 10 0
f03224551 100% 10 0
joshua-ne commented 1 month ago

Okay, from what I can see here, SP's of the following haven't taken any deals: f03068013,f03035686,f01926635,f01999119,f03136267. So I will omit the retrieval data from these SP's.

Like I said last time, the duplication of f01111110 is a statistic error, which I will also be sure to ignore.

The retrieval with f01422327,f02252023,f02252024 is not perfect, but acceptable to me.

The newly added SP's are good from my end, the SPARK may take some additional time to collect the data.

However, please contact the operator of f01111110 and f01909705to make sure they are retrievable, until wich I will not continue to support you with any more Datacap. @Dengminer

Dengminer commented 1 month ago

Hi, I have contacted the operator of f01111110 and f01909705, and they seemed to have a problem with their Yugabyte database. They have restored the database and they are retrievable now. Please check again and let me know if you have any further questions or concerns.

joshua-ne commented 1 month ago

trigger:run_retrieval_test method=lassie sp_list=f03068013,f03035686,f01926635,f01999119,f03136267,f01422327,f02252023,f02252024,f01111110,f01909705,f03224283,f03224551 client=f1qtxjoxzobjmcxn3aaxn7tyj7e3p24r3d2bw3ygy limit=10 start_datetime="2024-08-01 00:00:00" end_datetime="2024-10-15 00:00:00"

myfil512 commented 1 month ago
miner_id retrieval_rate retrieval_success_counts retrieval_fail_counts
f03068013 NA 0 0
f03035686 NA 0 0
f01926635 NA 0 0
f01999119 NA 0 0
f03136267 NA 0 0
f01422327 80% 8 2
f02252023 80% 8 2
f02252024 80% 8 2
f01111110 100% 10 0
f01909705 100% 10 0
f03224283 100% 10 0
f03224551 100% 10 0
joshua-ne commented 1 month ago

Okay, the retrieval looks good to me now. Would be able to support for another round.

datacap-bot[bot] commented 1 month ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacedazrebyy2j3ybyaj77ld4q64shpxfs2lz6xgz5hsmnpgoycja6ng

Address

f1qtxjoxzobjmcxn3aaxn7tyj7e3p24r3d2bw3ygy

Datacap Allocated

256TiB

Signer Address

f1sfffys4o2w64rdpd3alpmvpvj4ik6x2iyjsjmry

Id

e159b7c5-d5d9-4cc7-9f54-cb3acef68d99

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

datacap-bot[bot] commented 1 month ago

Application is Granted

datacap-bot[bot] commented 1 month ago

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

joshua-ne commented 1 month ago

checker:manualTrigger

datacap-bot[bot] commented 1 month ago

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

⚠️ 1 storage providers sealed too much duplicate data - f01111110: 49.86%

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

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

⚠️ The average retrieval success rate is 16.07%

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.