There are multiple features unique to the COR platform that are powered by the COR engine.
Each oracle has a profile that displays the data relevant to an oracle. The COR engine analyses all Chainlink oracles. The entity that operates an oracle can verify themselves on-chain such that the COR platform detects the verification and registers an identity to an Ethereum address. An oracle’s profile features multiple pieces of data specific to that oracle such as transactions, response time and unique requesters.
Unique requesteres are the unique Ethereum addresses to which an oracle may deliver data. COR analyses not only oracle specific data, but also the unique requesters for that data. As of May 2020, the primary unique requesters are the Chainlink feeds that update the price reference data for a variety of Defi applications to use. An example of a unique requester would be the ETH/USD Chainlink Contract.
Within each oracle’s profile, you can see which unique requesters that specific oracle serves, as well as the specific data that an oracle has delivered to that address.
Chainlink Network Dashboard
The purpose of the Chainlink network dashboard is to provide a holistic overview of the health of the Chainlink Network. By providing up to date, weekly statistics, the dashboard allows users to become informed on what has occurred on the Chainlink network in the past week - before using the rest of the COR platform to zoom in and discover oracle-specific, granular data.
The Chainlink network dashboard provides two views - an overall snapshot view, with an up to date network history over the last 7 days, as well as a graph view. The graph view provides a rolling 7 day history of the Chainlink network. Each data point represents a summation of a single metric over the last 7 days.
COR can be used to readily compare oracles on a metric by metric basis. This allows for job requesters to carefully sort through oracles to find the most competitive in certain areas and then visualise their performances over time.
API Uptime Service
The COR platform includes an API Uptime Service that monitors the APIs that Chainlink node operators use to provide certain pieces of data. When an oracle is responding erroneously or not responding at all, it may very well be the fault of an API service that it is subscribed to. The API Uptime Service allows for node operators to choose a reliable API provider as well as giving job requesters a reason as to why a node is underperforming and failing to respond to a request or misreporting a piece of data.