The Livepeer Protocol Explorer is like a block explorer, but for Livepeer's round based progression and roles rather than blockchain blocks.
This is not meant to be a prioritization, but rather is a braindump of some of the obvious things that could be included in the protocol explorer. Anyone should add comments, questions, discussion to this issue, but we probably should break out the actual tasks into separate issues.
Network Status
Current round number
Cycle in round
Start block number of round
End block number of round
Current transcoder turn
Next transcoder turn
Previous transcoder turn
Block number of next transcoder turn
Total Livepeer Token issued
Number of active transcoders
(@yondonfu may have some additional ideas here)
Address View
Token balance
Bonded token
Delegated towards (linkable to transcoder view)
Status of bonding (are they withdrawing for example)
Job history (linkable to job view)
Token reward history - how much token did they receive in each reward cycle? Perhaps linkable to a reward view which shows the split from fee and block reward.
Transcoder View
Active?
Current total bonded stake
Current pricing/fee share/block reward cut status
Pending pricing/fee share/block reward cut status
Cumulative job stats
Slashing history
Job View
Job status
Broadcaster (linkable)
Transcoder (linkable)
StreamIDs
Segments claimed
Segments challenged
Verification status
Reward View (Round View?)
TBD...can we identify a call to Reward() by any ID or round/cycle combo and then infer what happened in that round in terms of slashing and token distribution? Can we do this with publicly available blockchain data or do we have to build up the history as events/transactions are seen in blocks? If we can do the above, then can we actually generate a summary for the full round?
Transcoder election view
This is the "action oriented tool" for users to elect transcoders
Table view listing active and pending transcoders and their key stats
The Livepeer Protocol Explorer is like a block explorer, but for Livepeer's round based progression and roles rather than blockchain blocks.
This is not meant to be a prioritization, but rather is a braindump of some of the obvious things that could be included in the protocol explorer. Anyone should add comments, questions, discussion to this issue, but we probably should break out the actual tasks into separate issues.
Network Status
Address View
Transcoder View
Job View
Reward View (Round View?)
TBD...can we identify a call to
Reward()
by any ID or round/cycle combo and then infer what happened in that round in terms of slashing and token distribution? Can we do this with publicly available blockchain data or do we have to build up the history as events/transactions are seen in blocks? If we can do the above, then can we actually generate a summary for the full round?Transcoder election view
This is the "action oriented tool" for users to elect transcoders