Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tweak Smesher screen #912

Closed
4 tasks
brusherru opened this issue May 24, 2022 · 0 comments · Fixed by #925
Closed
4 tasks

Tweak Smesher screen #912

brusherru opened this issue May 24, 2022 · 0 comments · Fixed by #925
Assignees

Comments

@brusherru
Copy link
Member

brusherru commented May 24, 2022

Rationale

The smesher screen shows some information, but it is not enough for the user to understand what is the current status.

Here are the user questions we want to answer:

  1. I am Smeshing Correctly (eligible for reward)?
  2. Am I getting rewards?
  3. When is the next one?
  4. What & When was my last reward?

The idea is to add such additional rows:

  • Smeshing statistics
    Layer rewards: 127.56 SMH
    Fee rewards: 8.07 SMH
    Total rewards: 135.63 SMH
    Last earned: 09:52:20 AM + 0.0510 SMH [OPEN LOG]

  • Currently Mining: EPOCH 22
    Layer rewards: 13.5 SMH
    Fee rewards: 1 SMH
    Total rewards: 14.5 SMH
    Estimated rewards: 3.46 SMH

  • Coming up: EPOCH 23
    Status: WAITING FOR POET / ELIGIBLE / NOT ELIGIBLE
    Estimated Time: ~24.05.2022 11:44 AM (layer 4600)
    Estimated reward: 342.5 SMH

Since some API endpoints are missing we will not implement crossed-out rows.
Then we have everything on our hands to implement the rest.

Acceptance criteria

  • Time estimation is calculated based on values from node-config (layer-duration-sec, layers-per-epoch, genesis-time)
  • New fields are displayed
  • Button "OPEN LOG" just opens the transaction log without any filtration
  • Receiving the next reward should automatically rerender these rows

Out of scope

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant