This new view allows users to fetch an overview of all past values retrieved by the same data request. Instead of looking up a specific hash value, you can look up the SHA256 hash of the data request bytecode. The bytecode of a request can be read from the smart contract launching the data request or by compiling a data request using the witnet-toolkit as specified in the documentation.
There are two possible variations for the history overview. The first one will show only exact matches for a data request. This implies that both the sources and data request parameters such as number of witnesses and defined fees have to be an exact match. It is also possible to retrieve an overview where only the sources match.
An example of a data request history overview for a Bitcoin price request can be found in below screenshot:
In the card on the top left, the history type (data request bytes hash or RAD bytes hash) and hashes are shown as well as how many matches there are. The top right card shows the relevant parameters for this data request. In the bottom card there are two tabs. The first tab shows the data requests which have been completed up until now. It details the data request timestamp, transaction hash, number of errors, number of liars and final result. The second tab shows the RAD script. The RAD script details the queried sources, how they are filtered and aggregated.
Note that only the 100 most recent matches are shown. The API endpoint allows to control which section of the data request history is fetched through supplying start, stop and amount parameters. The start and stop parameters are the epochs boundaries between which you want to fetch historical requests.
The data request report which was introduced in the first release of the explorer now also contains links to these overviews.
This view is particularly useful for developers who want to peruse the results of their past data requests.
