DataCap and CID Checker Report1
- Organization:
IPFSKDC
- Client:
f13y7egp3cu7o6eog5fliizqt24f5o6qwnedbdq5a
1
nj-steve1
psh06911
zcfil
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 2nd allocation, the following restrictions have been relaxed:
- Storage provider should not exceed 90% 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 |
---|---|---|---|---|---|
f02005421 | Seoul, Seoul, KRAmazon.com, Inc. |
55.03 TiB | 22.61% | 55.03 TiB | 0.00% |
f09848 | Rancho Santa Margarita, California, USCox Communications Inc. |
52.30 TiB | 21.48% | 52.30 TiB | 0.00% |
f01695888 | Gwangju, Gwangju, KRKorea Telecom |
82.19 TiB | 33.76% | 82.19 TiB | 0.00% |
f01227505 | Onam, Gyeonggi-do, KRKorea Telecom |
49.28 TiB | 20.24% | 49.19 TiB | 0.19% |
f01823110 | Jeonju, Jeollabuk-do, KRKorea Telecom |
4.64 TiB | 1.91% | 4.64 TiB | 0.00% |
The below table shows how each many unique data are replicated across storage providers.
Since this is the 2nd allocation, the following restrictions have been relaxed:
- No more than 90% of unique data are stored with less than 2 providers.
✔️ Data replication looks healthy.
Unique Data Size | Total Deals Made | Number of Providers | Deal Percentage |
---|---|---|---|
20.06 TiB | 20.06 TiB | 1 | 8.24% |
4.63 TiB | 9.25 TiB | 2 | 3.80% |
19.97 TiB | 59.94 TiB | 3 | 24.62% |
34.31 TiB | 137.31 TiB | 4 | 56.40% |
3.38 TiB | 16.88 TiB | 5 | 6.93% |
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.
Other Client | Application | Total Deals Affected | Unique CIDs | Approvers |
---|---|---|---|---|
f1pkpa3h4suh77mi3guur25r5u4twkere5r35fjii | CommonCraw | 5.56 TiB | 167 | 1 GaryGJG1 laurarenpanda |