Predict when the next reward will be farmed #206
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- This is a probabilistic function based on the amount of space pledged by farmer w.r.t the total space pledged. Also considered the last reward timestamp to give an idea as to when can a farmer expect the next reward.
- Boxed the large field `raw_config to reduce the total size of the enum. Suppressed `#[warn(clippy::large_enum_variant)]` warning. - Add the widget drawn using DrawingArea object considering its suitable appearance in both light & dark themes. - Implement that in Relm4 code style. - Integrated the widget into RunningView frontend page. - Also added a testing feature to try how it works by toggling the FarmDetails button.
- Commented the test button logic to see how the progress bar works. - Total space pledged function added to backend so as to calculate it fetching the TSP metrics.
1 task
nazar-pc
reviewed
Jun 4, 2024
- Rectified tests in test_format_eta function in src/frontend/utils - Receive chain constants into RunningView FE on each block import via sending separate event. - Receive space_pledged from backend rather than frontend.
nazar-pc
reviewed
Jun 11, 2024
Comment on lines
+535
to
+536
| let (current_solution_range, max_pieces_in_sector) = | ||
| consensus_node.total_space_pledged_chain_constants()?; |
There was a problem hiding this comment.
Neither current solution range nor max pieces in sector are actually constants. And even if they were, it would make much more sense to send all of this in initialization notification instead.
Okay. |
|
Replaced with #230 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
The issue titled "Predict when the next reward will be farmed" discusses the potential to provide users (farmers) with predictions on when they can expect to receive rewards based on on-chain data regarding space pledged and the last farming reward payment timestamp. This prediction could then be displayed to the user as having a high/low probability of receiving a reward with descriptions like "today", "in about an hour", or "any time now".
Description
This PR adds:
slot_probability(from frontend),current_solution_range,max_pieces_in_sector(from backend).calculate_expected_reward_duration_from_nowfunction to calculate the ETA for next reward payment.