Skip to content

HIP 122: Amend Service Provider Hex Boosting #998

@hiptron

Description

@hiptron

HIP 122: Amend Service Provider Hex Boosting

  • Author(s): @mrfizzy99 (Fizzy99 - Fiz-Tech.net)
  • Start Date: 2024-04-29
  • Category: Economic, Technical
  • Original HIP PR: #916
  • Tracking Issue: #998
  • Vote Requirements: veMOBILE Holders

Summary

HIP-84 Service Provider Hex Boosting as it is written, provides too much unilateral control over where rewards are distributed to any service provider at the expense of the network PoC distribution pool.

If a service provider decides to hex boost all of Miami, the rewards distributed on behalf of the network is disproportionate to the amount burned and disincentivizes the remaining nationwide deployments on the network for the sole purpose of that service provider, ultimately dictating areas where majority of rewards should go.
While this author understands that the first service provider on the network is key to the networks success for future service providers to join, it should not be at the detriment of the network's natural expansion nationwide into other cities, and internationally.

With this in mind, there are also a few other amendments in this HIP that will also benefit the Service Provider in regards to HIP-84. One of which is changing the minimum boost time to 3 months, and the other is staking the hotspot in order to receive the boosted rewards.

Rendered View

https://github.com/helium/HIP/blob/main/0122-amend-service-provider-hex-boosting.md

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions