helium / HIP

Helium Improvement Proposals
Apache License 2.0
580 stars 408 forks source link

HIP 118: Updates #1025

Closed zer0tweets closed 4 months ago

zer0tweets commented 4 months ago

Adding changes per most recent community discussion:

  1. Tooling requirements section added, specifying the need for updates to planner with location of subscribers + updates to helium mobile app with confirmation of the name for mapped hotspots.

  2. Updated Rewards Adjustments section, such that this HIP will initially only affect boosted locations.

  3. Added thoughts on having this HIP affect hotspot trust score in Unresolved Questions section, proposing to defer this to later to minimize implementation complexity.

nosmaster89 commented 4 months ago

As the success metrics are currently written can this hip even succeed ? can you map CBRS radios if not then the success of over 50% of all radios can currently not be met, the metric defines all radios , my understanding would this would be WIFI units ,and the radios connected to Freedomfi units. Also is this intended to be 50% of active units or just on boarded units

madninja commented 4 months ago

I believe CBRS radios can be mapped just as well.. it's all about getting CDR records for data which both wifi and CBRS will support. The hold back for CBRS is getting working SIMs..

On Wed, May 22, 2024 at 10:36 AM Liam Edwards @.***> wrote:

As the success metrics are currently written can this hip even succeed ? can you map CBRS radios if not then the success of over 50% of all radios can currently not be met, the metric defines all radios , my understanding would this would be WIFI units ,and the radios connected to Freedomfi units. Also is this intended to be 50% of active units or just on boarded units

— Reply to this email directly, view it on GitHub https://github.com/helium/HIP/pull/1025#issuecomment-2124967273, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAACZBU4YM3KSN5R7GCPORTZDSUPFAVCNFSM6AAAAABICPWKKOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRUHE3DOMRXGM . You are receiving this because you are subscribed to this thread.Message ID: @.***>