This report provides information on a client's distribution and data replication of the storage providers being used.
The results from this report should only be used as a guide for analyzing a particular client. When using this report in conjunction with the individual context of a client, there could be a completely valid explaination that negates the client from being flagged in the first place. This should be determined on a case by case basis.
If you have any questions or feedback for the cid-checker open an issue.
this report can be triggered on applications in the open data pathway repo for a specific client application using the following methods:
- label trigger - when a label of
state:Approvedis added to the github issue. - manually trigger - add a comment to an application with this text:
checker:manualTrigger - combine with other addresses - add a comment to an application with this text:
checker:manualTrigger <other_address_1> <other_address_2> .... This is useful if those addresses belong to the same series of LDN applications.
all assets for these reports are uploaded to filplus-checker-assets.
A table showing the distribution of storage providers that have stored data for the client, along with approximate location, total deals sealed, unique data stored, and percentage of duplicate deals for each provider. Criteria for flaggable events is listed in the report itself.
A table showing the replication of unique data across storage providers, along with information on the size of the unique data, total deals made, number of providers, and deal percentage for each data replication category. In general, a healthy data replication chart would show higher number of replication counts across providers moving towards the right side of the x-axis (colored green). If there is a large amount of data that is only replicated between a smaller provider set, this is viewed as a flaggable condition.
A table showing the provider breakdown and number of CIDs that have been shared across providers. CID sharing can be seen as an flaggable condition.
