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

Add boosted_hex_device_type_v1 for HIP-109 #401

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

michaeldjeffrey
Copy link
Contributor

The first iteration of HIP-1091 adds the ability to boost by a device type. Pre-existing boosts will continue to boost all device types.

From the way the HIP reads, at some point, a hex may be boosted by the same provider for multiple device types. It was undecided wether that would be implemented as multiple device_types attached to a boosted hex, or multiple instances of a boosted hex.

src/hex_boosting.proto Outdated Show resolved Hide resolved
@michaeldjeffrey michaeldjeffrey force-pushed the mj/hip-109-boost-by-device-type branch from fc0da24 to 7e0c821 Compare August 30, 2024 19:33
The first iteration of HIP-109[1] adds the ability to boost by a device
type. Pre-existing boosts will continue to boost _all_ device types.

From the way the HIP reads, at some point, a hex may be boosted by the
same provider for multiple device types. It was undecided wether that
would be implemented as multiple device_types attached to a boosted hex,
or multiple instances of a boosted hex.

[1]: https://github.com/helium/HIP/blob/main/0109-hex-boosting-by-deployment.md
Familiarizes the reader with the context of what they're about to get into.
@michaeldjeffrey michaeldjeffrey force-pushed the mj/hip-109-boost-by-device-type branch from 4654fc8 to dcf951f Compare September 6, 2024 18:37
@michaeldjeffrey michaeldjeffrey marked this pull request as ready for review September 9, 2024 16:40
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