[DataCap Application] <RongYIn Open Data Project 2>

[datalove2]

Data Owner Name

RongYIn Open Data Project 2

Data Owner Country/Region

China

Data Owner Industry

IT & Technology Services

Website

https://www.qcc.com/firm/3380acbb3101bd58394d1ba4be51e877.html

Social Media

https://www.qcc.com/firm/3380acbb3101bd58394d1ba4be51e877.html

Total amount of DataCap being requested

5PiB

Weekly allocation of DataCap requested

500TiB

On-chain address for first allocation

f13prg74xg56peezyogauhkbomx4x4jzajyczh34q

Custom multisig

• Use Custom Multisig

Identifier

No response

Share a brief history of your project and organization

RongYin was established in 2019 in HK. We were provided with a storage capacity in total of 100PiB. Now, we are planning to engage in onboard humanity data which is useful for the network. <RongYin Open Data Project> estimated onboard 10PiB storage capacity to the network, which is about 1.5P raw 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

We are going to onboard open data of agriculture from AWS. 
Agriculture datasets covers 86 matching datasets. In total about 5PiB. 
Including USGS Landsat, NOAA, ESA WorldCover, Digital Earth Africa, Rice Genomes Project, SILO Climate data and so on.

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

IPFS, lotus, singularity, graphsplit

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/deafrica-geomad/
https://registry.opendata.aws/deafrica-wofs/
https://registry.opendata.aws/afsis/
https://registry.opendata.aws/3kricegenome/
https://registry.opendata.aws/isdasoil/
https://registry.opendata.aws/noaa-goes

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

Greater China, Asia other than Greater China, North America, South America, Europe, Australia (continent)

How will you be distributing your data to storage providers

HTTP or FTP server, IPFS, Shipping hard drives, Lotus built-in data transfer

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

In communicating

How do you plan to make deals to your storage providers

Boost client, Lotus client, Singularity

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]

See questions in #1579

[simonkim0515]

Datacap Request Trigger

Total DataCap requested

5PiB

Expected weekly DataCap usage rate

500TiB

Client address

f13prg74xg56peezyogauhkbomx4x4jzajyczh34q

[large-datacap-requests]

DataCap Allocation requested

Multisig Notary address

f01858410

Client address

f13prg74xg56peezyogauhkbomx4x4jzajyczh34q

DataCap allocation requested

250TiB

Id

89596cc0-2f7b-45a3-8c94-9a43c5e36f32

[herrehesse]

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.

[kernelogic]

DD performed in #1579 (comment)

[kernelogic]

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzaced7sjtrppbl2m6q2nbuwgo26te5w5xy6p2a4xjwj6jv2idgbysddo

Address

f13prg74xg56peezyogauhkbomx4x4jzajyczh34q

Datacap Allocated

250.00TiB

Signer Address

f1yjhnsoga2ccnepb7t3p3ov5fzom3syhsuinxexa

Id

89596cc0-2f7b-45a3-8c94-9a43c5e36f32

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

[Tom-OriginStorage]

DD performed in 1579

[Tom-OriginStorage]

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzaced7uezpfnwidokiednbr3e7xke636k4rt6sf2zlnnozgsq7bg75d6

Address

f13prg74xg56peezyogauhkbomx4x4jzajyczh34q

Datacap Allocated

250.00TiB

Signer Address

f1q6bpjlqia6iemqbrdaxr2uehrhpvoju3qh4lpga

Id

89596cc0-2f7b-45a3-8c94-9a43c5e36f32

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

[large-datacap-requests]

DataCap Allocation requested

Request number 2

Multisig Notary address

f02049625

Client address

f13prg74xg56peezyogauhkbomx4x4jzajyczh34q

DataCap allocation requested

500TiB

Id

f2e2b36d-f439-41a2-a3dc-f48a5391dc50

[large-datacap-requests]

Stats & Info for DataCap Allocation

Multisig Notary address

f02049625

Client address

f13prg74xg56peezyogauhkbomx4x4jzajyczh34q

Rule to calculate the allocation request amount

800% of weekly dc amount requested

DataCap allocation requested

1.34PiB

Total DataCap granted for client so far

1.8160790205001833e+37YiB

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

-2.19B

Stats

Number of deals	Number of storage providers	Previous DC Allocated	Top provider	Remaining DC
85706	18	1.95PiB	26.14	566.48TiB

[sxxfuture-official]

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.02%
• 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

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

Deal Data Shared with other Clients²

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

• 14.47 TiB - f1es3jnh7ivhvc32s23mro7wuktehjkxlc7yjac6a - RongYInOpen Data Project 1
• 6.56 TiB - f1opjqkoajys7fr4yajwcpj2bhuf4akh4s4ppdjwq - Hepta
• 3.44 TiB - f17nerghj2kmg7b4e6asft3xexga5qbzbqe3hi4gy - NDLABS

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> ... ↩

[sxxfuture-official]

Refer to my reply in #1579

[sxxfuture-official]

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzaceam5qlyopto5dwj4uyf75uovvlcgp4dbbmvfyxu4swv5q2nzmuzys

Address

f13prg74xg56peezyogauhkbomx4x4jzajyczh34q

Datacap Allocated

1.34PiB

Signer Address

f1foiomqlmoshpuxm6aie4xysffqezkjnokgwcecq

Id

d7fd1696-2ea6-4def-b780-40ebf1a2d17e

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

[zcfil]

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.02%
• 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

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

Deal Data Shared with other Clients²

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

• 14.47 TiB - f1es3jnh7ivhvc32s23mro7wuktehjkxlc7yjac6a - RongYInOpen Data Project 1
• 6.56 TiB - f1opjqkoajys7fr4yajwcpj2bhuf4akh4s4ppdjwq - Hepta
• 3.44 TiB - f17nerghj2kmg7b4e6asft3xexga5qbzbqe3hi4gy - NDLABS

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> ... ↩

[mikezli]

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacebqkn3e2y5v2j3halwts42zyxedtt75ehqle7gds643g4pc2ubvvi

Address

f13prg74xg56peezyogauhkbomx4x4jzajyczh34q

Datacap Allocated

1.34PiB

Signer Address

f1dnb3uz7sylxk6emti3ififcvu3nlufnnsjui6ea

Id

d7fd1696-2ea6-4def-b780-40ebf1a2d17e

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