Official RChain Blockchain Explorer

Official RChain Blockchain Explorer

Target release

Mercury

Epic

 

Document status

DRAFT

Document owner

@Medha Parlikar (Unlicensed)

Designer

Developers

QA

Goals

  • Growth, Reduce Risk

Background and strategic fit

An official Blockchain explorer will be a requirement prior to listing on Bittrex.

Assumptions

  • At a minimum, features on https://etherscan.io/ will need to be supported.

  • Public namespace blockchains can be explored

  • Private names can only be explored, if the name is known @Michael Stay (Unlicensed) please confirm.

Requirements

Title

User Story

Importance

Notes

Title

User Story

Importance

Notes

1

Market Cap of Rev

Describe the total market cap of Rev, and exchange rate between BTC

Must Have

  • Need to determine where any exchange rate would be sourced

2

Explore a namespace

Provide a namespace to the explorer, see the blockchain stats for that namespace

Must Have

  • If I know the name of a RChain namespace, I can see the blockchain statistics for that namespace.

3

Last block mined

 Display the last block number mined & time it took

Must Have

  •  This would be the block for the namespace that is being explored.

4

Network Difficulty

Display the network difficulty 

TBD

  • Suspect that this is not relevant with a Proof of Stake Consensus protocol.  There may be another metric that could be used instead?

5

Transaction count

Display the transaction count

Must Have

  • Display the total transactions, transactions per block.

6

Display mined blocks

Display block number, Who mined the block, transactions in the block, time to mine the block, and the block reward.

Must Have

  • Basically need all the block details that are available.

7

Display transactions

Display transaction details.  Transaction id, from address, to address, block height, block confirmation count, timestamp, Contract address, description of transaction, Value, Phlogiston used, Phlogiston price, Actual Tx. cost, Input data, output data

Must Have

  • Need all the transaction details made available.

User interaction and design

Questions

Below is a list of questions to be addressed as a result of this requirements document:

Question

Outcome

Question

Outcome

Not Doing