You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/Intro/dashboard.md
+28-4Lines changed: 28 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,11 +3,11 @@ sidebar_position: 4
3
3
---
4
4
5
5
# The Chronicle Dashboard
6
-
The [Chronicle Dashboard](https://chroniclelabs.org/dashboard) enables full transparency over where the Oracle-reported data was sourced and who reported/signed it.
6
+
The **[Chronicle Dashboard](https://chroniclelabs.org/dashboard)** enables full transparency over where the Oracle-reported data was sourced and who reported/signed it.
7
7
8
-
## Where is the data sourced from?
8
+
## Where is the Data Sourced From?
9
9
10
-
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 on-chain and off-chain data sources with high liquidity.
10
+
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.
11
11
12
12
13
13
<divstyle={{textAlign:'center'}}>
@@ -24,7 +24,13 @@ Using the dashboard, users can select a time interval on the graph and, for each
24
24
width="500"
25
25
/>
26
26
</div>
27
-
In addition, users can cryptographically verify in the browser that the validator's signature has not been tampered with.
27
+
28
+
## Verifiability on Every Level
29
+
30
+
Users can cryptographically verify in the browser using the Dashboard any **Validator's Signature**, as well as the the **Schnorr Signature** used for pushing data onchain for the corresponding Oracle.
31
+
32
+
### The Validator Signature
33
+
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.
28
34
29
35
<divstyle={{textAlign:'center'}}>
30
36
<img
@@ -43,5 +49,23 @@ Modifying even one character of the signature will result in invalidating the si
43
49
/>
44
50
</div>
45
51
52
+
### The Schnorr Signature
53
+
54
+
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.
0 commit comments