[Feature] Node rewards chain explorer. Resolves [#413]

[apoorv-2204]

Description

It adds a Reward chain explorer to UI, which includes :node_rewards and :mint_rewards tx types in chronological order.

Fixes

• Add node rewards chain explorer #413

Type of change

Please delete options that are not relevant.

• Minor fix

  • Name change: get_gen_addr : genesis_address , wherever applicable.
  • Minor spec changes from number to non_negative_number for index.
  • Correct typos.

• New feature (non-breaking change which adds functionality)

  • New Reward explorer Ui.
  • New db method list_chain_addresses , takes genesis address and return a stream of address in old to recent order.

• This change requires a documentation update

  • Brief Reward chain desc was given under /explorer/chain/rewards UI.

• Review_changes

  • Transactions appear in page w.r.t previous page time reference.
  • Display pages according to nb of transactions.
  • ex: 40 transaction 4 page .
    

• Deterministic test

  • for faucet_controller_test.exs

• ####Future Improvements

  • ets table with DE - queue
  • Stream Transaction one by one from DB.

How Has This Been Tested?

• Unit Test cases were included wherever necessary
• Integration tests were included for live view
• DB tests.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[samuelmanzanera]

I got the previous button the first page

[samuelmanzanera]

This is not really accurate, actually the rewards are not sent during self-repair, but the fees burnt are collected during self-repair. The rewards transactions are sent at a specific interval later, once per cycle.

[samuelmanzanera]

There is an issue with the pagination:

Page1 is ended with 2022/09/16 14:34:30

Page2: is started with 2022/09/16 14:39:30

[samuelmanzanera]

Looks like good!
I just have one remark, when we reach 10 and 10 on 2 pages, I have a third empty page. Best would be to not showing it.
Maybe due to this one:

|> assign(:nb_pages, div(txn_count, @display_limit) + 1)

[samuelmanzanera]

If I wait on the first page, the transactions are accumulated but the pagination is not activated. If I refresh after I will the see the pagination.
Maybe we should detect when we reach the 10txs, to display only the last 10 on the screen while activating the pagination.

[samuelmanzanera]

Looks good

[apoorv-2204]

Closing Comment:
we must leverage ets, queue for cache. Or may be idea from google/guava.