Conversation
abhay
reviewed
May 21, 2020
| # Summary | ||
| [summary]: #summary | ||
|
|
||
| Data Packets are already transferring on the network. Once the price oracle is in place, users will be able too burn HNT and generate Data Credits, use DC to send packets on the network, and Hotspots routing those packets will earn a reward in the form of HNT. |
Contributor
There was a problem hiding this comment.
Suggested change
| Data Packets are already transferring on the network. Once the price oracle is in place, users will be able too burn HNT and generate Data Credits, use DC to send packets on the network, and Hotspots routing those packets will earn a reward in the form of HNT. | |
| Data Packets are already transferring on the network. Once the price oracle is in place, users will be able to burn HNT and generate Data Credits, use DC to send packets on the network, and Hotspots routing those packets will earn a reward in the form of HNT. |
Nit
|
|
||
| * How are we soliciting feedback on this HIP from these stakeholders? Note that | ||
| they may not be watching the HIPs repository or even aren't directly active in | ||
| the Rust Async Ecosystem working group. |
Contributor
There was a problem hiding this comment.
Suggested change
| the Rust Async Ecosystem working group. | |
| the Helium community. |
abhay
reviewed
May 21, 2020
| Data Packets are already transferring on the network. Once the price oracle is in place, users will be able too burn HNT and generate Data Credits, use DC to send packets on the network, and Hotspots routing those packets will earn a reward in the form of HNT. | ||
| This share is expected to be 30% of HNT per month, which is a large amount and can be easily gamed. | ||
|
|
||
| This proposal is to recommend a ramp up to 30% over a period of time to prevent undesirably gaming behaviour. |
Contributor
There was a problem hiding this comment.
What's the actual recommended ramp up and over what period of time? How does this conflict/work with the total ramp down of token distribution for PoC over the many year scale in the token distribution plan.
Contributor
|
Once Abhay's logistical changes have been incorporated, could we merge this PR so the actual HIP file is in the |
This was referenced Jun 4, 2020
Merged
Member
|
Closing for now. With the DC launch imminent, we are going to stick with the DC reward structure as originally implemented and can revisit in the future as needed. |
Contributor
|
Roger that. Do you think it's worth merging this HIP and labeling it
`rejected` for posterity?
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.