# tellorscan

## Goal

The goal of tellorscan is to revamp the current DisputeCenter into a site that present the liveliness of the Tellor network in an easy overview, serving as a one-stop-shop for all the data regarding the Tellor network.

Besides this, the site also aims to be a single point of contact for TRB-holders for all interactions w the network (disputing a value, voting on a dispute and voting on a TIP).

## Setup

The site should have a modular setup, both in UI and tech stack. Each individual module will contain its specific set of information and/or related actions. Modules should easily be added or removed as the network evolves.

So far, we want to include these modals:

- Pricelist module ( A )
- Mining events module ( B )
- TIP-module ( C )
- Dispute-module ( D )
- Dev-module ( E )
- TRBholder-module ( F )

Lofi UX-sketch:

[See as clickmodel](https://xd.adobe.com/view/71e7ef03-5900-4bf1-be17-788b44f3ba79-24b4/screen/9a52ec04-78d8-45f9-ae3c-27960a4ab035)

### A. Pricelist module
= filterable list of all price-events. The most recent onces will be visible on first 'page', the pagination will show the user to the older ones. Columns "item" and "date" will be searchable, value will be a sorting filter.

Each item contains:
- the describing symbol + the id number + a "tip ID"-button
- the submission date/timestamp
- the value, expressed in the right currency (e.g. ETH/USD > value expressed in USD)

### B. Mining events module
= filterable list of mining events. The current mining event is indicated with a "current" label on the left side, and also an indicator of how many accepted submissions this event already has ( "3/5" in the example). Each mining event will have a "+"-button on the right, to expand that mining event (expanded view seen on the right hand side on the sketch below). The accepted values will be seen in this expand area. (The current event will also show an "in Progress" and a spinner, to underline that it doesn't have 5 miners yet.)


### C. TIP-module
= module existing of 2 components: component 1 presents the current TIP that is live (or an 'empty' msg when there is no TIP live), and component 2 presents a filterable list of past TIP. Each of the items in this list contains:
- date when the TIP was decided
- title/description of the TIP ( w link 'more' to where the user can find more on this TIP)
- the percentage of votes that were casted
- how the community voted ( ="V passed!" or "X rejected" )

### D. Dispute-module
= module existing of 2 components: component 1 presents any current dispute that is live (or an 'empty' msg when there is no dispute live), and component 2 presents a filterable list of past TIP. Each of the items in this list contains:
- date when the TIP was decided
- title/description of the TIP ( w link 'more' to where the user can find more on this TIP)
- the percentage of votes that were casted
- how the community voted ( ="V passed!" or "X rejected" )

### E. Dev-module
T.B.D.

### F. TRBholder-module
= module for TRB-holder which shows, in its first iteration, the holder's TRB and ETH-balance and the holder's voting(/tx) history.

## To be discussed:

- What data is important for investors?
- What data is important for devs?
- What data is important for TRB-holders?
- Other target audiences...?

https://docs.google.com/document/d/1u_U804KioqLfcR8ERF1iJnRsBKaB9jcJClLLP9Rk0G8/edit#

## Other

- **BEN:** Check out code in detail to see what/how stuff can be be re-used?
- connection-stuff
- mining events?
- pricefeed?
- voting?

- **KRASI:** Dashboard to show some useful data - should be able to use thegraph or google big query for this.
https://explore.duneanalytics.com/public/dashboards/pVN6lRN8xxtfhjnEbcPbqreI8DNkPOng5P5fol0v
https://cloud.google.com/blog/products/data-analytics/ethereum-bigquery-public-dataset-smart-contract-analytics

- cfr. data.chain.link > make it flashy! Make it visually feel alive