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

HIP 98: MOBILE SubDAO Quality of Service Requirements #794

Merged
merged 20 commits into from
Oct 25, 2023

Conversation

heatedlime
Copy link
Contributor

This HIP establishes Quality of Service Requirements for the MOBILE 5G Network.

heatedlime and others added 18 commits June 6, 2023 17:54
This Helium Improvement Proposal (HIP) proposes creating MOBILE Boosting Oracles to add multipliers to the MOBILE Proof of Coverage (PoC) modeled coverage points (MCP), by using external data sources (aka Oracles) for the purpose of identifying areas in which coverage is more likely to be used by Service Providers.
This proposal suggests the implementation of an onboarding fee for indoor output devices of $10 and outdoor output devices of $20 that join the MOBILE network after the passing of this HIP.
Did a bunch of silly changes.  Removed extra lines and added the dash in lines 2 through 7 as the Foundation keeps making the same correction to all of my HIPs.
This HIP suggests changing the IoT location assertion fee from $10 in Data Creditis (DC) to $5 in IoT.
Create 0000-change-iot-hotspot-assertion-fees.md
This Helium Improvement Proposal (HIP) sets quality of service (QOS) requirements that were previously implemented.
Deleting extra from branch.
Deleting extra from branch.
@hiptron hiptron changed the title Heatedlime mobile qos requirements HIP 98: MOBILE SubDAO Quality of Service Requirements Oct 25, 2023
@hiptron
Copy link
Collaborator

hiptron commented Oct 25, 2023

going to update the README / ToC in a separate PR as this one is from a stale branch.

@hiptron hiptron merged commit 41ce688 into helium:main Oct 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants