HIP 111: MOBILE Data Utility Benchmark - 10x Reward Boost #903
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
abhay
reviewed
Feb 13, 2024
Updated formatting, term changes, and clarity.
|
Updated based on feedback from @abhay, @waveform06, and @heatedlime |
capjbadger007
changed the title
capjbadger007
changed the title
…- Mobile Data Utility Benchmark 10x Boost.md Title changes
Exemption example added due to community feedback.
|
@abhay What are next steps? |
…o 0XXX - Mobile Data Utility Benchmark - 10x Boost.md Updates via Hashc0de
capjbadger007
changed the title
capjbadger007
changed the title
… to XXXX - Mobile Data Utility Benchmark - 10x Boost.md
hiptron
changed the title
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.
This Helium Improvement Proposal (HIP) introduces data transfer requirements for Mobile gateways (CBRS, wifi, and any other protocols that pass mobile data) to be eligible for Boosted Proof-of-Coverage (POC) rewards in a given epoch. Units meeting the specified data transfer benchmark (1MB) within the previous 7 epochs will receive 10x POC rewards for the current epoch