Skip to content

Latest commit

 

History

History
61 lines (42 loc) · 3.82 KB

1687255546031.md

File metadata and controls

61 lines (42 loc) · 3.82 KB
Raw

DataCap and CID Checker Report1

  • Organization: reachauto
  • Client: f1gsvxh5lqvayqgaoxkjwie7swc2lgihgdgjdnaca

Approvers

1bq1024
1stcouldlisa

Storage Provider Distribution

The below table shows the distribution of storage providers that have stored data for this client.

If this is the first time a provider takes verified deal, it will be marked as new.

For most of the datacap application, below restrictions should apply.

Since this is the 3rd allocation, the following restrictions have been relaxed:

  • Storage provider should not exceed 70% of total datacap.
  • Storage provider should not be storing duplicate data for more than 20%.
  • Storage provider should have published its public IP address.
  • All storage providers should be located in different regions.

✔️ Storage provider distribution looks healthy.

Provider Location Total Deals Sealed Percentage Unique Data Duplicate Deals
f01981571 Shanghai, Shanghai, CN
China Telecom (Group)		 39.09 TiB 28.60% 39.09 TiB 0.00%
f02029115 Shanghai, Shanghai, CN
China Telecom (Group)		 39.03 TiB 28.56% 39.03 TiB 0.00%
f02182251 Stockholm, Stockholm, SE
The Constant Company, LLC		 39.09 TiB 28.60% 39.03 TiB 0.16%
f02098007 Toronto, Ontario, CA
The Constant Company, LLC		 19.47 TiB 14.24% 19.47 TiB 0.00%

Deal Data Replication

The below table shows how each many unique data are replicated across storage providers.

Since this is the 3rd allocation, the following restrictions have been relaxed:

  • No more than 70% of unique data are stored with less than 3 providers.

✔️ Data replication looks healthy.

Unique Data Size Total Deals Made Number of Providers Deal Percentage
2.00 GiB 2.00 GiB 1 0.00%
64.00 GiB 128.00 GiB 2 0.09%
19.63 TiB 58.88 TiB 3 43.07%
19.41 TiB 77.69 TiB 4 56.83%

Deal Data Shared with other Clients2

The below table shows how many unique data are shared with other clients. Usually different applications owns different data and should not resolve to the same CID.

However, this could be possible if all below clients use same software to prepare for the exact same dataset or they belong to a series of LDN applications for the same dataset.

✔️ No CID sharing has been observed.

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