HIP11: Usage based rewards proposal #33
Merged
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
added 2 commits
August 19, 2020 15:59
|
|
||
| ### Setting a per hotspot per epoch cap | ||
|
|
||
| By establishing a 100,000 DC per epoch per hotspot cap on data rewards, it disincentives ‘extreme’ gaming of the system and puts a cap on the time and energy of developers working to optimize mining devices. It also reduces to total mining going to the top few percentile of DC mining units and allows for the redistribution of that HNT, while still incentivizing significant data usage in the system. As the value of per DC rewards come down, so will the total max reward as the ratio remains. |
There was a problem hiding this comment.
Can you cut the cap down to say 10-15k an epoch? And maybe adjust up as the arb variance decreases? That would be a significant drop for these problem hotspots.
jamiew
changed the title
|
Merging in, please direct future discussion to the tracking issue: #34 |
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.
No description provided.