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.

Sign up for GitHub

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 109: Hex Boosting by Deployment #884

Merged
merged 2 commits into from
Jan 27, 2024
Merged

HIP 109: Hex Boosting by Deployment #884

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5874e80
Create 0000-hex-boosting-by-deployment.md
heatedlime Jan 26, 2024
e33505b
Update frontmatter and number
hiptron Jan 27, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
48 changes: 48 additions & 0 deletions 0109-hex-boosting-by-deployment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,48 @@
# HIP 109: Hex Boosting by Deployment

- Author(s): [Andy Zyvoloski](https://github.com/heatedlime) & [Max Gold](https://github.com/maxgold91)
- Start Date: 2024-01-27
- Category: Economic, Technical
- Original HIP PR: [#886](https://github.com/helium/HIP/pull/886)
- Tracking Issue: [#888](https://github.com/helium/HIP/issues/888)
- Vote Requirements: veMOBILE Holders

## Summary:

This Helium Improvement Proposal (HIP) allows Service Providers to specify what types of deployments their hex boosting can be applied to (i.e. CBRS vs Wi-Fi).

## Prior Related HIPs

- [HIP-84](https://github.com/helium/HIP/blob/main/0084-service-provider-hex-boosting.md) created Service Provider Hex Boosting.

## Motivation:
In instances where Service Providers identify areas where they have high demand for data, they are able to burn MOBILE to provide a boost in those hexes, as defined in [HIP-84](https://github.com/helium/HIP/blob/main/0084-service-provider-hex-boosting.md). However, they aren’t able to specify which types of deployments they want to provide a boost to.


## Stakeholders:

The stakeholders of this proposal are:
- Service Providers will be able to fine tune what types of deployments they want and where
- Deployers may not receive hex boosting if the equipment they deploy isn’t what the Service Provider needs.

## Detailed Explanation:
Whenever a Service Provider burns MOBILE to boost hexes, they will be allowed to choose which types of deployments (i.e. indoor CBRS, outdoor CBRS, indoor Wi-Fi, Outdoor Wi-Fi) their boost will apply to. This selection may be one, or both deployment types. The selection needs to be made when the initial burn occurs, and cannot be changed after the initial selection.

For example, if a Service Provider burns MOBILE to boost a res12 hex and specifies the boost to only apply towards Wi-Fi, any CBRS deployments covering that Wi-Fi boosted hex will not receive the boost, but still will be rewarded for PoC.

In instances where the Service Provider wants to boost both CBRS and Wi-Fi in a hex, the cost will be $0.005 per res12 hex, per month, per deployment type (Wi-Fi vs CBRS). For example, if a Service Provider wanted to boost one res12 hex to 10X for one month for both CBRS and Wi-Fi, the Service Provider will be required to burn $0.05 in MOBILE for Wi-Fi boost and $0.05 MOBILE for the CBRS boost.

In instances where MOBILE already has been burned to boost hexes, those hexes will remain as boosted hexes for all deployment types (i.e. indoor CBRS, outdoor CBRS, indoor Wi-Fi, Outdoor Wi-Fi) for the duration of the boost.


## Drawbacks:
None

## Rationale
Since Service Providers are paying for boosts, they should be able to select what types of deployments they would like to see in those boosted areas.


## Success Metrics
The primary success metric will greater fine tuned coverage in boosted hexes.