The Chronicle Dashboard
The Chronicle Dashboard enables full transparency over where the Oracle-reported data was sourced and who reported/signed it. On the dashboard, you can find details such as the validator set used by Chronicle, the different oracles for the supported chains, and oracle-specific information like update thresholds, contract addresses, and data sources, among others.
The Chronicle Dashboard Tabs and Functionality
In the top left corner, you can find three tabs: Dashboard, Oracles, and Validators.
Dashboard
The Dashboard tab provides an overview of the Chronicle Dashboard. You can see the total number of oracles, a summary of the oracles available, and a snapshot of the validator set.
Oracles
The Oracles tab allows users to find oracle addresses for specific chains. Inside this tab, you can toggle between Mainnets and Testnets to view oracle addresses for production and test environments. For each, you can select the specific chain you're interested in.
Validators
The Validators tab offers an overview of Chronicle’s validator set, which includes reputable Web3 projects such as Sky, Euler, ETHGlobal, and Etherscan, among others.
Where is the Data Sourced From?​
Using the dashboard, users can select a time interval on the graph and, for each validator, use the drop-down arrow to see the different data sources that have been used. Typically, the data sources are a mix of onchain and off-chain data sources with high liquidity.
Verifiability on Every Level​
Users can cryptographically verify in the browser using the Dashboard any Validator's Signature, as well as the Schnorr Signature used to push the price onchain to the corresponding Oracle.
The Validator Signature​
The validator's signature allows users to verify the behaviour of the validator. Users can check the message that has been signed by each validator to calculate the price for the Oracle.
Modifying even one character of the signature will result in invalidating the signature.
The Schnorr Signature of the Oracle​
Users can also verify the authenticity of the Schnorr signature of the Oracle. This value is used to push data onchain. Unlike the validator's signature, the Schnorr signature allows to verify the Oracle instead of a single validator.
