From fa874e5e0e1833301d91dfa8f7879d5d60945a7f Mon Sep 17 00:00:00 2001 From: Andy Zyvoloski <104723888+heatedlime@users.noreply.github.com> Date: Tue, 6 Jun 2023 17:54:35 -0500 Subject: [PATCH 01/56] Create 0000-MOBILE-Oracle-Hex-Boosting.md 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. --- 0000-MOBILE-Oracle-Hex-Boosting.md | 122 +++++++++++++++++++++++++++++ 1 file changed, 122 insertions(+) create mode 100644 0000-MOBILE-Oracle-Hex-Boosting.md diff --git a/0000-MOBILE-Oracle-Hex-Boosting.md b/0000-MOBILE-Oracle-Hex-Boosting.md new file mode 100644 index 000000000..c07667bde --- /dev/null +++ b/0000-MOBILE-Oracle-Hex-Boosting.md @@ -0,0 +1,122 @@ +Author: [Andy Zyvoloski](https://github.com/heatedlime) +Start Date: 6/6/2023 +Category: Technical & Economic +Original HIP PR: # +Tracking Issue: # +Voting Requirements: veMOBILE + + +## Summary: +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. + +Further, this HIP proposes adding the first Oracle, the Carrier Coverage Oracle, which incentives deployments in areas in which T-Mobile has pre-existing coverage. + + +## Motivation: +HIP 74 was passed to incorporate obstruction data and radio signal power into the PoC reward model; however, it weighs all hexes equally, even if there's a low probability of actual coverage being needed in that area. This proposal aims to improve the value of the network coverage by incentivizing users to deploy radios in areas where Oracles have determined Service Providers are more likely to need coverage. + +## Stakeholders: +The stakeholders of this proposal are Service Providers, radio deployers, and network users. Radio deployers can benefit from increased rewards for providing coverage in areas where coverage is needed. + +## Detailed Explanation: +MOBILE Boosting Oracles (refer herewith as “Oracles”) are data sources which are used to estimate how useful mobile coverage will be in a specific area. This HIP proposes allowing Oracles to be established to help guide deployments in areas that need more coverage. Oracles will be used to give applicable hexes boosts (increasing or decreasing) based on the area they are deployed in. Any Oracle multiplier within a single res12 hex will stack onto one another. Oracle boosting shall also stack with any other Mobile boosts, such as the Service Provider boosts defined in HIP 84 (assuming HIP 84 passes). + +The ranking system established in HIP 85 (assuming HIP 85 passes) will serve as a baseline multiplier. This means that once all boosts are aggregated, they will be multiplied against the MCP after the baseline multiplier defined in HIP 85 is applied. For example, if the MCP after HIP 85 calculations are 0, the total boosts that aggregate to 5X does not grant any additional MCP, and it will be 0, as 0 X 5 = 0. +Examples of how this works can be found below within the Carrier Coverage Oracle section. + +The data sources from Oracles are to be updated no less than once per year. The Oracle updates are to be reviewed by a MOBILE Governance Group (or MOBILE Working Group if no Governance Group exists) prior to implementation to ensure and confirm the Oracle data was updated correctly. + +### Changes to Oracle Boosts +As the MOBILE network matures, Oracle boosts may need to be fine tuned or changed. Therefore, the boosts and data type for each boost shall be implemented as chain variables. In order for these chain variables to be modified, or deleted, a MOBILE Governance Group (or MOBILE Working Group if no Governance Group exists) must create an Oracle Change Proposal. The proposal will then be presented and discussed by the Group, in which a general consensus must be reached (consensus defined by the Group). Once consensus is reached, the proposal will be put to a vote by the community, with the voting requirement being veMOBILE. + +The proposal must be announced within the Official Helium Community Discord Server under the “Governance-Announcement” channel (or similar channel if the “Governance-Announcement” channel is removed), at least five (5) calendar days prior to the start of voting. Voting shall remain open for seven (7) calendar days. A 66.67% vote in favor of the change(s) must be reached in order for the vote to pass. + +A new vote with the same or modified change(s) to that Oracle may be put to vote by the community again with Group consensus no earlier than 60 calendar days after the last voting has ended. + + +### Carrier Coverage Oracle +Coverage areas that are already covered by the top mobile carriers, such as T-Mobile, have already been identified as areas in which there’s a documented supply and demand for data. Therefore, this HIP proposes creating the first MOBILE Boosting Oracle, the Carrier Coverage Oracle that utilizes the existing T-Mobile coverage map (https://www.t-mobile.com/coverage/coverage-map) to add a boost to PoC Modeled Coverage Points defined in HIP 74 based on the type of coverage T-Mobile offers in that res12 hex. This HIP covers both indoor and outdoor CBRS radios. + +From reviewing the T-Mobile coverage map below of Minneapolis Minnesota and its surrounding suburbs, as well as other large cities within the US, it can be noted that T-Mobile coverage primarily consists of 5G Ultra Capacity and 5G Extended Range in populated cities. These are areas in which T-Mobile have deployed capital and infrastructure to increase and enhance coverage. Thus, one can assume data use in these areas are higher than data use in 4G LTE, 3G/2G areas. + +INSERT T MOBILE MAP PICTURE HERE + +The below boosts will be awarded to modeled coverage points for each radio and each res12 hex: + +| T-Mobile Coverage Type | Boost | +|------------------------|-------| +|5G Ultra Capacity | 1.25X | +|5G Extended Range | 1X | +|4G LTE | .5X | +|3G/2G/Partner | .25X | +|No Coverage | .1X | + + +See the examples below of boosts in a single res12 hex. Note, the Baseline Hex Coverage Limit Multiplier is from HIP 85, assuming HIP 85 passes) + +Carrier Coverage Oracle Boost: 1.25X +Made Up Oracle Boost: 3X +Service Provider Boost: 5X +Aggregate Boosts: 9.25X +Potential Signal Level: High +MCP assigned per HIP 74: 16 +Baseline Hex Coverage Limit Multiplier: 0X +MCP assigned per HIP 85: 0 +Total MCP per res12 hex: 0 + +Carrier Coverage Oracle Boost: 1.25X +Made Up Oracle Boost: 3X +Service Provider Boost: 5X +Aggregate Boosts: 9.25X +Potential Signal Level: High +MCP assigned per HIP 74: 16 +Baseline Hex Coverage Limit Multiplier: 1X +MCP assigned per HIP 85: 16 +Total MCP per res12 hex: 148 + +Carrier Coverage Oracle Boost: 1.25X +Made Up Oracle Boost: 3X +Service Provider Boost: None +Aggregate Boosts: 4.5X +Potential Signal Level: High +MCP assigned per HIP 74: 16 +Baseline Hex Coverage Limit Multiplier: .75X +MCP assigned per HIP 85: 12 +Total MCP per res12 hex: 54 + +Carrier Coverage Oracle Boost: 1X +Made Up Oracle Boost: 1X +Service Provider Boost: None +Aggregate Boosts: 2X +Potential Signal Level: High +MCP assigned per HIP 74: 16 +Baseline Hex Coverage Limit Multiplier: 1X +MCP assigned per HIP 85: 16 +Total MCP per res12 hex: 32 + +Carrier Coverage Oracle Boost: .5X +Made Up Oracle Boost: .5X +Service Provider Boost: None +Aggregate Boosts: 1X +Potential Signal Level: High +MCP assigned per HIP 74: 16 +Baseline Hex Coverage Limit Multiplier .75X +MCP assigned per HIP 85: 12 +Total MCP per res12 hex: 12 + +Drawbacks: +The implementation of this proposal could increase the complexity of the Helium Mobile network, and modeled coverage scores. There may be concerns about the accuracy of the population data provided, or the need to update the data regularly. + +Further, there may be areas in which T-Mobile does not provide coverage although there is a need for coverage. However, in these cases, Service Provider Boosts will be able to adjust the boosts as needed. + +Alternatives +An alternative would be allowing radios and hexes to keep earning the defined amount of modeled coverage points as described in HIP 74. However, this may prevent or stagnate the network's growth because HIP 74 does not incentivize deployment of Hotspots to specific areas or regions. + +Unresolved Question +1. Can bodies of water be extracted from the T-Mobile Map and provide a .1X multiplier for coverage over water? + +Deployment Impact +Radio deployers will now need to be cognizant of where they are placing their radios in order to maximize modeled coverage point. + +Success Metrics +The primary success metric will be greater coverage on the modeled coverage map in areas where top carriers have already identified as areas that need data. From 9e95944bc0e8c31cd332120888782a25127afe4b Mon Sep 17 00:00:00 2001 From: Andy Zyvoloski <104723888+heatedlime@users.noreply.github.com> Date: Tue, 6 Jun 2023 17:56:22 -0500 Subject: [PATCH 02/56] Update 0000-MOBILE-Oracle-Hex-Boosting.md minor formatting edits. --- 0000-MOBILE-Oracle-Hex-Boosting.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/0000-MOBILE-Oracle-Hex-Boosting.md b/0000-MOBILE-Oracle-Hex-Boosting.md index c07667bde..4facedafc 100644 --- a/0000-MOBILE-Oracle-Hex-Boosting.md +++ b/0000-MOBILE-Oracle-Hex-Boosting.md @@ -1,8 +1,13 @@ Author: [Andy Zyvoloski](https://github.com/heatedlime) + Start Date: 6/6/2023 + Category: Technical & Economic + Original HIP PR: # + Tracking Issue: # + Voting Requirements: veMOBILE From 47e625c8dd4079f2a02d2637200298a9938bf27f Mon Sep 17 00:00:00 2001 From: Andy Zyvoloski <104723888+heatedlime@users.noreply.github.com> Date: Tue, 6 Jun 2023 19:19:51 -0500 Subject: [PATCH 03/56] Update 0000-MOBILE-Oracle-Hex-Boosting.md Added image link --- 0000-MOBILE-Oracle-Hex-Boosting.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/0000-MOBILE-Oracle-Hex-Boosting.md b/0000-MOBILE-Oracle-Hex-Boosting.md index 4facedafc..4281cdef7 100644 --- a/0000-MOBILE-Oracle-Hex-Boosting.md +++ b/0000-MOBILE-Oracle-Hex-Boosting.md @@ -44,7 +44,8 @@ Coverage areas that are already covered by the top mobile carriers, such as T-Mo From reviewing the T-Mobile coverage map below of Minneapolis Minnesota and its surrounding suburbs, as well as other large cities within the US, it can be noted that T-Mobile coverage primarily consists of 5G Ultra Capacity and 5G Extended Range in populated cities. These are areas in which T-Mobile have deployed capital and infrastructure to increase and enhance coverage. Thus, one can assume data use in these areas are higher than data use in 4G LTE, 3G/2G areas. -INSERT T MOBILE MAP PICTURE HERE +https://github.com/helium/HIP/commit/9e95944bc0e8c31cd332120888782a25127afe4b#commitcomment-116813063 + The below boosts will be awarded to modeled coverage points for each radio and each res12 hex: @@ -99,15 +100,15 @@ Baseline Hex Coverage Limit Multiplier: 1X MCP assigned per HIP 85: 16 Total MCP per res12 hex: 32 -Carrier Coverage Oracle Boost: .5X +Carrier Coverage Oracle Boost: .25X Made Up Oracle Boost: .5X Service Provider Boost: None -Aggregate Boosts: 1X +Aggregate Boosts: .75X Potential Signal Level: High MCP assigned per HIP 74: 16 -Baseline Hex Coverage Limit Multiplier .75X -MCP assigned per HIP 85: 12 -Total MCP per res12 hex: 12 +Baseline Hex Coverage Limit Multiplier .25X +MCP assigned per HIP 85: 4 +Total MCP per res12 hex: 3 Drawbacks: The implementation of this proposal could increase the complexity of the Helium Mobile network, and modeled coverage scores. There may be concerns about the accuracy of the population data provided, or the need to update the data regularly. @@ -119,6 +120,7 @@ An alternative would be allowing radios and hexes to keep earning the defined am Unresolved Question 1. Can bodies of water be extracted from the T-Mobile Map and provide a .1X multiplier for coverage over water? +2. Are the current boosts prescribed in this HIP adequate? Deployment Impact Radio deployers will now need to be cognizant of where they are placing their radios in order to maximize modeled coverage point. From 63f604c1e5594821b6fa01c66a2d7e59112c8e65 Mon Sep 17 00:00:00 2001 From: Andy Zyvoloski <104723888+heatedlime@users.noreply.github.com> Date: Tue, 6 Jun 2023 19:29:34 -0500 Subject: [PATCH 04/56] Update 0000-MOBILE-Oracle-Hex-Boosting.md test --- 0000-MOBILE-Oracle-Hex-Boosting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-MOBILE-Oracle-Hex-Boosting.md b/0000-MOBILE-Oracle-Hex-Boosting.md index 4281cdef7..4dfc53b77 100644 --- a/0000-MOBILE-Oracle-Hex-Boosting.md +++ b/0000-MOBILE-Oracle-Hex-Boosting.md @@ -44,7 +44,7 @@ Coverage areas that are already covered by the top mobile carriers, such as T-Mo From reviewing the T-Mobile coverage map below of Minneapolis Minnesota and its surrounding suburbs, as well as other large cities within the US, it can be noted that T-Mobile coverage primarily consists of 5G Ultra Capacity and 5G Extended Range in populated cities. These are areas in which T-Mobile have deployed capital and infrastructure to increase and enhance coverage. Thus, one can assume data use in these areas are higher than data use in 4G LTE, 3G/2G areas. -https://github.com/helium/HIP/commit/9e95944bc0e8c31cd332120888782a25127afe4b#commitcomment-116813063 +![](https://github.com/helium/HIP/commit/9e95944bc0e8c31cd332120888782a25127afe4b#commitcomment-116813063) The below boosts will be awarded to modeled coverage points for each radio and each res12 hex: From 88263faf71d378545d6b7a799c1178acc0b5d873 Mon Sep 17 00:00:00 2001 From: Andy Zyvoloski <104723888+heatedlime@users.noreply.github.com> Date: Tue, 6 Jun 2023 19:34:55 -0500 Subject: [PATCH 05/56] Update 0000-MOBILE-Oracle-Hex-Boosting.md Testing image insert --- 0000-MOBILE-Oracle-Hex-Boosting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-MOBILE-Oracle-Hex-Boosting.md b/0000-MOBILE-Oracle-Hex-Boosting.md index 4dfc53b77..0b4f8d139 100644 --- a/0000-MOBILE-Oracle-Hex-Boosting.md +++ b/0000-MOBILE-Oracle-Hex-Boosting.md @@ -44,7 +44,7 @@ Coverage areas that are already covered by the top mobile carriers, such as T-Mo From reviewing the T-Mobile coverage map below of Minneapolis Minnesota and its surrounding suburbs, as well as other large cities within the US, it can be noted that T-Mobile coverage primarily consists of 5G Ultra Capacity and 5G Extended Range in populated cities. These are areas in which T-Mobile have deployed capital and infrastructure to increase and enhance coverage. Thus, one can assume data use in these areas are higher than data use in 4G LTE, 3G/2G areas. -![](https://github.com/helium/HIP/commit/9e95944bc0e8c31cd332120888782a25127afe4b#commitcomment-116813063) +![](https://user-images.githubusercontent.com/104723888/243865314-85ddc953-d767-4cdf-9556-1b7d5cf8b855.png) The below boosts will be awarded to modeled coverage points for each radio and each res12 hex: From 127c5a6082c9916cc3f42cd4ae8a94dd5e1a4ed2 Mon Sep 17 00:00:00 2001 From: Andy Zyvoloski <104723888+heatedlime@users.noreply.github.com> Date: Wed, 14 Jun 2023 09:21:42 -0500 Subject: [PATCH 06/56] Create 0000-MOBILE-Network-Onboarding-Fee 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. --- 0000-MOBILE-Network-Onboarding-Fee | 61 ++++++++++++++++++++++++++++++ 1 file changed, 61 insertions(+) create mode 100644 0000-MOBILE-Network-Onboarding-Fee diff --git a/0000-MOBILE-Network-Onboarding-Fee b/0000-MOBILE-Network-Onboarding-Fee new file mode 100644 index 000000000..26c62dffe --- /dev/null +++ b/0000-MOBILE-Network-Onboarding-Fee @@ -0,0 +1,61 @@ +# HIP XX: MOBILE Network Onboarding Fee + +Authors: [Andy Zyvoloski](https://github.com/heatedlime) & @KeithRettig +Start Date: 6/14/2023 +Category: Technical & Economic +Original HIP PR: # +Tracking Issue: # +Voting Requirements: veMOBILE + +##Summary: +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 the day after the passing of this HIP. Output devices are defined in the detailed summary section below. + + +##Motivation: +As implemented in HIP 51, a DAO Utility Score is used to determine the daily emissions of HNT to each SubDAO treasury. The equation for this calculation is noted below: + +$\text{DAO Utility Score} = V \times D \times A$ +Where +$V = \text{max}(1, veHNT_{DNP})$ +$D = \text{max}(1, \sqrt{\text{DNP DCs burned in USD}})$ +$A = \text{max}(1, \sqrt[4]{\text{DNP Active Device Count} \times \text{DNP Device Activation Fee}})$ + +At its current rate, the A score in the equation for MOBILE is zero (0), as there currently is not any prescribed onboarding fees for the MOBILE network. The implementation of this HIP would inscribe onboarding fees for output devices which would significantly boost the output of the A score, which in turn, would effectively provide a significant increase to the daily HNT emissions sent to the MOBILE SubDAO treasury. + +This HIP only applies to output devices onboarded the day after the passing of this HIP. Any output devices onboarded prior to the passing of this HIP are already onboarded, and as such, are not required to pay such fee. + +##Stakeholders: +Stakeholders are all current and future output device deployers on the MOBILE network. + +HNT holders will also benefit with the burning of HNT for each newly onboarded output device. + +##Detailed Explanation: + +At the passing of this HIP, all outdoor and indoor output devices onboarded to the MOBILE network will be required to pay an onboarding fee, which is paid via data credits. With this HIP, a way to track, manage and burn HNT/data credits for newly onboarded output devices needs to be created by the Helium Foundation. Thus, a way to pay onboarding fees needs to be established before they can be paid. Therefore, any output devices onboarded the day after the passing of this HIP will be required to pay their onboard fee no later than October 31st, 2023. This allows time for the Helium Foundation to create a way to track and manage this process. If any output devices onboarded to the MOBILE network the day after the passing of this HIP do not pay their onboarding fees by October 31st, 2023, their output device will become inactive, and not earn any PoC or data transfer rewards until the fee is paid in full. + +###Definitions +Output Device - A device that outputs a cellular or wifi signal for End Users to connect to. For example, this would include a CBRS Radio or a Carrier offload Wifi (CoWifi) unit. +End User - A device that connects to a cellular or wifi signal, such as a cell phone or mapping device. + + + +##Alternatives: + +One alternative is to do nothing, and keep onboarding fees as zero (0). However, this would hinder the daily HNT emissions to the MOBILE SubDAO treasury since the A score would remain zero (0). + +Another alternative is to change the way the A score is calculated to benefit the HNT emissions of the MOBILE Network; however, this would require a vote with veHNT instead of veMOBILE. + + +##Unresolved Question: +None + + +##Deployment Impact: +Output deployers will now need to pay onboarding fees for any newly onboarded output devices after the implementation of this HIP. + +The Helium Foundation will need to create a way to track and manage output device onboards and ensure fees paid for output devices prior to the October 31, 2023 deadline. Further, the foundation will need to ensure that the day after the passing of this HIP that the A score for the MOBILE SubDAO is correctly updated to reflect the total amount of indoor and outdoor output devices, as well as their associated fees for the MOBILE SubDAO. + + +##Success Metrics: +The primary success metric will be greater daily HNT emissions to the MOBILE SubDAO treasury. + From 823fe6a058d68880c94e66a835ef410ad2fe9e66 Mon Sep 17 00:00:00 2001 From: Andy Zyvoloski <104723888+heatedlime@users.noreply.github.com> Date: Wed, 14 Jun 2023 13:29:42 -0500 Subject: [PATCH 07/56] Create HeatedLime 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. --- HeatedLime | 59 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 59 insertions(+) create mode 100644 HeatedLime diff --git a/HeatedLime b/HeatedLime new file mode 100644 index 000000000..0f7017b35 --- /dev/null +++ b/HeatedLime @@ -0,0 +1,59 @@ +# HIP XX: MOBILE Network Onboarding Fee + +Authors: [Andy Zyvoloski](https://github.com/heatedlime) & @KeithRettig +Start Date: 6/14/2023 +Category: Technical & Economic +Original HIP PR: # +Tracking Issue: # +Voting Requirements: veMOBILE + +##Summary: +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 the day after the passing of this HIP. Output devices are defined in the detailed summary section below. + + +##Motivation: +As implemented in HIP 51, a DAO Utility Score is used to determine the daily emissions of HNT to each SubDAO treasury. The equation for this calculation is noted below: + +$\text{DAO Utility Score} = V \times D \times A$ +Where +$V = \text{max}(1, veHNT_{DNP})$ +$D = \text{max}(1, \sqrt{\text{DNP DCs burned in USD}})$ +$A = \text{max}(1, \sqrt[4]{\text{DNP Active Device Count} \times \text{DNP Device Activation Fee}})$ + +At its current rate, the A score in the equation for MOBILE is zero (0), as there currently is not any prescribed onboarding fees for the MOBILE network. The implementation of this HIP would inscribe onboarding fees for output devices which would significantly boost the output of the A score, which in turn, would effectively provide a significant increase to the daily HNT emissions sent to the MOBILE SubDAO treasury. + +This HIP only applies to output devices onboarded the day after the passing of this HIP. Any output devices onboarded prior to the passing of this HIP are already onboarded, and as such, are not required to pay such fee. + +##Stakeholders: +Stakeholders are all current and future output device deployers on the MOBILE network. + +HNT holders will also benefit with the burning of HNT for each newly onboarded output device. + +##Detailed Explanation: + +At the passing of this HIP, all outdoor and indoor output devices onboarded to the MOBILE network will be required to pay an onboarding fee, which is paid via data credits. With this HIP, a way to track, manage and burn HNT/data credits for newly onboarded output devices needs to be created by the Helium Foundation. Thus, a way to pay onboarding fees needs to be established before they can be paid. Therefore, any output devices onboarded the day after the passing of this HIP will be required to pay their onboard fee no later than October 31st, 2023. This allows time for the Helium Foundation to create a way to track and manage this process. If any output devices onboarded to the MOBILE network the day after the passing of this HIP do not pay their onboarding fees by October 31st, 2023, their output device will become inactive, and not earn any PoC or data transfer rewards until the fee is paid in full. + +###Definitions +Output Device - A device that outputs a cellular or wifi signal for End Users to connect to. For example, this would include a CBRS Radio or a Carrier offload Wifi (CoWifi) unit. +End User - A device that connects to a cellular or wifi signal, such as a cell phone or mapping device. + + + +##Alternatives: +One alternative is to do nothing, and keep onboarding fees as zero (0). However, this would hinder the daily HNT emissions to the MOBILE SubDAO treasury since the A score would remain zero (0). + +Another alternative is to change the way the A score is calculated to benefit the HNT emissions of the MOBILE Network; however, this would require a vote with veHNT instead of veMOBILE. + + +##Unresolved Question: +None + + +##Deployment Impact: +Output deployers will now need to pay onboarding fees for any newly onboarded output devices after the implementation of this HIP. + +The Helium Foundation will need to create a way to track and manage output device onboards and ensure fees paid for output devices prior to the October 31, 2023 deadline. Further, the foundation will need to ensure that the day after the passing of this HIP that the A score for the MOBILE SubDAO is correctly updated to reflect the total amount of indoor and outdoor output devices, as well as their associated fees for the MOBILE SubDAO. + + +##Success Metrics: +The primary success metric will be greater daily HNT emissions to the MOBILE SubDAO treasury. From 2e6b47507e5b8536682b20da13a58b6a63d62896 Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Wed, 14 Jun 2023 17:41:04 -0700 Subject: [PATCH 08/56] Update 0000-MOBILE-Network-Onboarding-Fee Made basically the same set of changes but to the correct file. --- 0000-MOBILE-Network-Onboarding-Fee | 22 +++++++--------------- 1 file changed, 7 insertions(+), 15 deletions(-) diff --git a/0000-MOBILE-Network-Onboarding-Fee b/0000-MOBILE-Network-Onboarding-Fee index 26c62dffe..16daf5a54 100644 --- a/0000-MOBILE-Network-Onboarding-Fee +++ b/0000-MOBILE-Network-Onboarding-Fee @@ -1,16 +1,14 @@ # HIP XX: MOBILE Network Onboarding Fee - -Authors: [Andy Zyvoloski](https://github.com/heatedlime) & @KeithRettig -Start Date: 6/14/2023 -Category: Technical & Economic -Original HIP PR: # -Tracking Issue: # -Voting Requirements: veMOBILE +- Authors: [Andy Zyvoloski](https://github.com/heatedlime) & @KeithRettig +- Start Date: 6/14/2023 +- Category: Technical & Economic +- Original HIP PR: # +- Tracking Issue: # +- Voting Requirements: veMOBILE ##Summary: 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 the day after the passing of this HIP. Output devices are defined in the detailed summary section below. - ##Motivation: As implemented in HIP 51, a DAO Utility Score is used to determine the daily emissions of HNT to each SubDAO treasury. The equation for this calculation is noted below: @@ -34,28 +32,22 @@ HNT holders will also benefit with the burning of HNT for each newly onboarded o At the passing of this HIP, all outdoor and indoor output devices onboarded to the MOBILE network will be required to pay an onboarding fee, which is paid via data credits. With this HIP, a way to track, manage and burn HNT/data credits for newly onboarded output devices needs to be created by the Helium Foundation. Thus, a way to pay onboarding fees needs to be established before they can be paid. Therefore, any output devices onboarded the day after the passing of this HIP will be required to pay their onboard fee no later than October 31st, 2023. This allows time for the Helium Foundation to create a way to track and manage this process. If any output devices onboarded to the MOBILE network the day after the passing of this HIP do not pay their onboarding fees by October 31st, 2023, their output device will become inactive, and not earn any PoC or data transfer rewards until the fee is paid in full. ###Definitions -Output Device - A device that outputs a cellular or wifi signal for End Users to connect to. For example, this would include a CBRS Radio or a Carrier offload Wifi (CoWifi) unit. +Output Device - A device that outputs a cellular or wifi signal to which End Users connect. For example, this would include a CBRS Radio or a carrier-offloading Wifi (coWifi) unit. End User - A device that connects to a cellular or wifi signal, such as a cell phone or mapping device. - - ##Alternatives: One alternative is to do nothing, and keep onboarding fees as zero (0). However, this would hinder the daily HNT emissions to the MOBILE SubDAO treasury since the A score would remain zero (0). Another alternative is to change the way the A score is calculated to benefit the HNT emissions of the MOBILE Network; however, this would require a vote with veHNT instead of veMOBILE. - ##Unresolved Question: None - ##Deployment Impact: Output deployers will now need to pay onboarding fees for any newly onboarded output devices after the implementation of this HIP. The Helium Foundation will need to create a way to track and manage output device onboards and ensure fees paid for output devices prior to the October 31, 2023 deadline. Further, the foundation will need to ensure that the day after the passing of this HIP that the A score for the MOBILE SubDAO is correctly updated to reflect the total amount of indoor and outdoor output devices, as well as their associated fees for the MOBILE SubDAO. - ##Success Metrics: The primary success metric will be greater daily HNT emissions to the MOBILE SubDAO treasury. - From cf035e9a3a2bf1e777acb7d80a5ab5f1f96e63f9 Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Wed, 14 Jun 2023 17:44:05 -0700 Subject: [PATCH 09/56] Update 0000-MOBILE-Network-Onboarding-Fee edited my name in author line --- 0000-MOBILE-Network-Onboarding-Fee | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-MOBILE-Network-Onboarding-Fee b/0000-MOBILE-Network-Onboarding-Fee index 16daf5a54..24dc951b6 100644 --- a/0000-MOBILE-Network-Onboarding-Fee +++ b/0000-MOBILE-Network-Onboarding-Fee @@ -1,5 +1,5 @@ # HIP XX: MOBILE Network Onboarding Fee -- Authors: [Andy Zyvoloski](https://github.com/heatedlime) & @KeithRettig +- Authors: [Andy Zyvoloski](https://github.com/heatedlime), [Keith Rettig](https://github.com/keithrettig) - Start Date: 6/14/2023 - Category: Technical & Economic - Original HIP PR: # From 879e469bf3b1f17374c67681ac84c09fb7bbea8c Mon Sep 17 00:00:00 2001 From: Andy Zyvoloski <104723888+heatedlime@users.noreply.github.com> Date: Wed, 14 Jun 2023 21:28:54 -0500 Subject: [PATCH 10/56] Update 0000-MOBILE-Network-Onboarding-Fee small gramatical changes. --- 0000-MOBILE-Network-Onboarding-Fee | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/0000-MOBILE-Network-Onboarding-Fee b/0000-MOBILE-Network-Onboarding-Fee index 24dc951b6..3ab65988b 100644 --- a/0000-MOBILE-Network-Onboarding-Fee +++ b/0000-MOBILE-Network-Onboarding-Fee @@ -25,19 +25,21 @@ This HIP only applies to output devices onboarded the day after the passing of t ##Stakeholders: Stakeholders are all current and future output device deployers on the MOBILE network. -HNT holders will also benefit with the burning of HNT for each newly onboarded output device. +HNT holders will also benefit from the burning of HNT for each newly onboarded output device. ##Detailed Explanation: -At the passing of this HIP, all outdoor and indoor output devices onboarded to the MOBILE network will be required to pay an onboarding fee, which is paid via data credits. With this HIP, a way to track, manage and burn HNT/data credits for newly onboarded output devices needs to be created by the Helium Foundation. Thus, a way to pay onboarding fees needs to be established before they can be paid. Therefore, any output devices onboarded the day after the passing of this HIP will be required to pay their onboard fee no later than October 31st, 2023. This allows time for the Helium Foundation to create a way to track and manage this process. If any output devices onboarded to the MOBILE network the day after the passing of this HIP do not pay their onboarding fees by October 31st, 2023, their output device will become inactive, and not earn any PoC or data transfer rewards until the fee is paid in full. +At the passing of this HIP, all outdoor and indoor output devices onboarded to the MOBILE network will be required to pay an onboarding fee, which is paid via data credits. + +With this HIP, a way to track, manage and burn HNT/data credits for newly onboarded output devices will need to be created by the Helium Foundation. Therefore, any output devices onboarded the day after the passing of this HIP will be required to pay their onboard fee no later than October 31st, 2023. This allows time for the Helium Foundation to create a way to track and manage this process. If any output devices onboarded to the MOBILE network the day after the passing of this HIP do not pay their onboarding fees by October 31st, 2023, their output device will become inactive, and not earn any PoC or data transfer rewards until the fee is paid in full. ###Definitions -Output Device - A device that outputs a cellular or wifi signal to which End Users connect. For example, this would include a CBRS Radio or a carrier-offloading Wifi (coWifi) unit. +Output Device (AKA Gateway) - A device that outputs a cellular or wifi signal to which End Users connect. For example, this would include a CBRS Radio or a carrier-offloading Wifi (coWifi) unit. End User - A device that connects to a cellular or wifi signal, such as a cell phone or mapping device. ##Alternatives: -One alternative is to do nothing, and keep onboarding fees as zero (0). However, this would hinder the daily HNT emissions to the MOBILE SubDAO treasury since the A score would remain zero (0). +One alternative is to do nothing, and keep onboarding fees as zero (0). However, this would impede the daily HNT emissions to the MOBILE SubDAO treasury since the A score would remain zero (0). Another alternative is to change the way the A score is calculated to benefit the HNT emissions of the MOBILE Network; however, this would require a vote with veHNT instead of veMOBILE. From 810a50255344eaea944148ec034f83ed078ea130 Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Thu, 15 Jun 2023 06:19:45 -0700 Subject: [PATCH 11/56] Update and rename 0000-MOBILE-Network-Onboarding-Fee to 0000-designate-mobile-network-onboarding-fees-and-device-definition.md Rewrote but left your draft at the end to make it easier for you to review. Delete your original once you merge the two. --- 0000-MOBILE-Network-Onboarding-Fee | 55 --------- ...k-onboarding-fees-and-device-definition.md | 109 ++++++++++++++++++ 2 files changed, 109 insertions(+), 55 deletions(-) delete mode 100644 0000-MOBILE-Network-Onboarding-Fee create mode 100644 0000-designate-mobile-network-onboarding-fees-and-device-definition.md diff --git a/0000-MOBILE-Network-Onboarding-Fee b/0000-MOBILE-Network-Onboarding-Fee deleted file mode 100644 index 3ab65988b..000000000 --- a/0000-MOBILE-Network-Onboarding-Fee +++ /dev/null @@ -1,55 +0,0 @@ -# HIP XX: MOBILE Network Onboarding Fee -- Authors: [Andy Zyvoloski](https://github.com/heatedlime), [Keith Rettig](https://github.com/keithrettig) -- Start Date: 6/14/2023 -- Category: Technical & Economic -- Original HIP PR: # -- Tracking Issue: # -- Voting Requirements: veMOBILE - -##Summary: -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 the day after the passing of this HIP. Output devices are defined in the detailed summary section below. - -##Motivation: -As implemented in HIP 51, a DAO Utility Score is used to determine the daily emissions of HNT to each SubDAO treasury. The equation for this calculation is noted below: - -$\text{DAO Utility Score} = V \times D \times A$ -Where -$V = \text{max}(1, veHNT_{DNP})$ -$D = \text{max}(1, \sqrt{\text{DNP DCs burned in USD}})$ -$A = \text{max}(1, \sqrt[4]{\text{DNP Active Device Count} \times \text{DNP Device Activation Fee}})$ - -At its current rate, the A score in the equation for MOBILE is zero (0), as there currently is not any prescribed onboarding fees for the MOBILE network. The implementation of this HIP would inscribe onboarding fees for output devices which would significantly boost the output of the A score, which in turn, would effectively provide a significant increase to the daily HNT emissions sent to the MOBILE SubDAO treasury. - -This HIP only applies to output devices onboarded the day after the passing of this HIP. Any output devices onboarded prior to the passing of this HIP are already onboarded, and as such, are not required to pay such fee. - -##Stakeholders: -Stakeholders are all current and future output device deployers on the MOBILE network. - -HNT holders will also benefit from the burning of HNT for each newly onboarded output device. - -##Detailed Explanation: - -At the passing of this HIP, all outdoor and indoor output devices onboarded to the MOBILE network will be required to pay an onboarding fee, which is paid via data credits. - -With this HIP, a way to track, manage and burn HNT/data credits for newly onboarded output devices will need to be created by the Helium Foundation. Therefore, any output devices onboarded the day after the passing of this HIP will be required to pay their onboard fee no later than October 31st, 2023. This allows time for the Helium Foundation to create a way to track and manage this process. If any output devices onboarded to the MOBILE network the day after the passing of this HIP do not pay their onboarding fees by October 31st, 2023, their output device will become inactive, and not earn any PoC or data transfer rewards until the fee is paid in full. - -###Definitions -Output Device (AKA Gateway) - A device that outputs a cellular or wifi signal to which End Users connect. For example, this would include a CBRS Radio or a carrier-offloading Wifi (coWifi) unit. -End User - A device that connects to a cellular or wifi signal, such as a cell phone or mapping device. - -##Alternatives: - -One alternative is to do nothing, and keep onboarding fees as zero (0). However, this would impede the daily HNT emissions to the MOBILE SubDAO treasury since the A score would remain zero (0). - -Another alternative is to change the way the A score is calculated to benefit the HNT emissions of the MOBILE Network; however, this would require a vote with veHNT instead of veMOBILE. - -##Unresolved Question: -None - -##Deployment Impact: -Output deployers will now need to pay onboarding fees for any newly onboarded output devices after the implementation of this HIP. - -The Helium Foundation will need to create a way to track and manage output device onboards and ensure fees paid for output devices prior to the October 31, 2023 deadline. Further, the foundation will need to ensure that the day after the passing of this HIP that the A score for the MOBILE SubDAO is correctly updated to reflect the total amount of indoor and outdoor output devices, as well as their associated fees for the MOBILE SubDAO. - -##Success Metrics: -The primary success metric will be greater daily HNT emissions to the MOBILE SubDAO treasury. diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md new file mode 100644 index 000000000..f459638fc --- /dev/null +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -0,0 +1,109 @@ +# HIP XX: Designate MOBILE Network Onboarding Fees and Device Definition +- Authors: [Andy Zyvoloski](https://github.com/heatedlime), [Keith Rettig](https://github.com/keithrettig) +- Start Date: 6/14/2023 +- Category: Technical & Economic +- Original HIP PR: # +- Tracking Issue: # +- Voting Requirements: veMOBILE + +##Summary +This proposal designates the Onboarding Fees for the onboarding of MOBILE subDAO devices. Also provides a definition of a Device within the MOBILE subDAO for the purposes of calculating the $A$ factor of the DAO Utility Score. An Onboarding Fee of $40 will set immedaitely upon passing; and, then once the necessary coding is complete, an Onboarding Fee of $10 will be set for Indoor Radio devices and $20 for Outdoor Radio devices. Indoor Devices and Outdoor Devices are defined in the detailed explanation section. + +##Motivation +As implemented in HIP51, a DAO Utility Score is used to determine the daily emissions of HNT to each SubDAO treasury. The equation for this calculation is noted below: + +$\text{DAO Utility Score} = V \times D \times A$ +Where +$V = \text{max}(1, veHNT_{DNP})$ +$D = \text{max}(1, \sqrt{\text{DNP DCs burned in USD}})$ +$A = \text{max}(1, \sqrt[4]{\text{DNP Active Device Count} \times \text{DNP Device Activation Fee}})$ + +At its current rate, the $A$ score in the equation for MOBILE is $0$ (zero) as, currently, there is not any prescribed onboarding fees for the MOBILE network. The implementation of this HIP would inscribe onboarding fees for output devices as prescribed by HIP51 which would allow a more appropriate calculation of the DAO Utility Score. + +This HIP only applies to Devices onboarded after the passing of this HIP. Any Device onboarded prior to the passing of this HIP are to be considered already onboarded. + +##Stakeholders +Stakeholders are all current and future Device deployers within the MOBILE subDAO. HNT holders will also be impacted from the burning of HNT by each Device paying its Onboarding Fees. + +##Detailed Explanation +At the passing of this HIP, all Devices onboarded to the MOBILE Network will be required to pay an onboarding fee; which is paid via $USD equivalent in Data Credits (DC). + +With this HIP, a way to track, manage, and burn Data Credits used to pay the Onboarding Fees for any newly onboarded Devices will need to be created by the Helium Foundation. Therefore, any output devices onboarded the day after the passing of this HIP will be required to pay their onboarding fees no later than October 31st, 2023. This allows time for the Helium Foundation to create a way to track and manage this process. If any Device onboarded to the MOBILE Network after the passing of this HIP do not pay their onboarding fees by October 31st, 2023, their output device will become inactive and not earn any Proof-of-Coverage or Data Transfer rewards until the fee is paid in full. Such Devices will be consider as if not onboarded. + +###Definitions +Indoor Device (AKA indoor radio) - A device that outputs a cellular or wifi signal to which End Users connect that is designed to be installed indoors. +Outdoor Device (AKA outdoor radio) - A device that outputs a cellular or wifi signal to which End Users connect that is designed to be installed oudoors. + At the time of this HIP's writing, both Indoor and Outdoor Devices would include CBRS Radioa and carrier-offloading Wifi (coWifi) devices. +End User - A device that connects to a cellular or wifi signal, such as a cell phone, tablet, laptop, etc. + +##Unresolved Questions +Confirmation that the Helium Foundation can certainly complete the needed work by the stated deadline of October 31, 2023. Conversations have been had various members of the FOundation and it has been conveyed that approximately 90 days would be needed to complete the work. + +##Deployment Impact +Operators of Devices will now need to pay Onboarding Fees for any newly onboarded output devices after the implementation of this HIP. + +The Helium Foundation will need to create a way to track and manage output device onboards and ensure fees paid for output devices prior to the October 31, 2023 deadline. Further, the foundation will need to ensure that after the passing of this HIP that the $A$ score of the DAO Utility Score for the MOBILE SubDAO is correctly updated to reflect the total amount of indoor and outdoor output devices, as well as their associated fees for the MOBILE SubDAO. + +##Success Metrics +The success metric will be the implementation of Onboarding Fees for all new Devices. + + + + +********************************************************************************************************************************************** + +# HIP XX: MOBILE Network Onboarding Fee +- Authors: [Andy Zyvoloski](https://github.com/heatedlime), [Keith Rettig](https://github.com/keithrettig) +- Start Date: 6/14/2023 +- Category: Technical & Economic +- Original HIP PR: # +- Tracking Issue: # +- Voting Requirements: veMOBILE + +##Summary: +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 the day after the passing of this HIP. Output devices are defined in the detailed summary section below. + +##Motivation: +As implemented in HIP 51, a DAO Utility Score is used to determine the daily emissions of HNT to each SubDAO treasury. The equation for this calculation is noted below: + +$\text{DAO Utility Score} = V \times D \times A$ +Where +$V = \text{max}(1, veHNT_{DNP})$ +$D = \text{max}(1, \sqrt{\text{DNP DCs burned in USD}})$ +$A = \text{max}(1, \sqrt[4]{\text{DNP Active Device Count} \times \text{DNP Device Activation Fee}})$ + +At its current rate, the A score in the equation for MOBILE is zero (0), as there currently is not any prescribed onboarding fees for the MOBILE network. The implementation of this HIP would inscribe onboarding fees for output devices which would significantly boost the output of the A score, which in turn, would effectively provide a significant increase to the daily HNT emissions sent to the MOBILE SubDAO treasury. + +This HIP only applies to output devices onboarded the day after the passing of this HIP. Any output devices onboarded prior to the passing of this HIP are already onboarded, and as such, are not required to pay such fee. + +##Stakeholders: +Stakeholders are all current and future output device deployers on the MOBILE network. + +HNT holders will also benefit from the burning of HNT for each newly onboarded output device. + +##Detailed Explanation: + +At the passing of this HIP, all outdoor and indoor output devices onboarded to the MOBILE network will be required to pay an onboarding fee, which is paid via data credits. + +With this HIP, a way to track, manage and burn HNT/data credits for newly onboarded output devices will need to be created by the Helium Foundation. Therefore, any output devices onboarded the day after the passing of this HIP will be required to pay their onboard fee no later than October 31st, 2023. This allows time for the Helium Foundation to create a way to track and manage this process. If any output devices onboarded to the MOBILE network the day after the passing of this HIP do not pay their onboarding fees by October 31st, 2023, their output device will become inactive, and not earn any PoC or data transfer rewards until the fee is paid in full. + +###Definitions +Output Device (AKA Gateway) - A device that outputs a cellular or wifi signal to which End Users connect. For example, this would include a CBRS Radio or a carrier-offloading Wifi (coWifi) unit. +End User - A device that connects to a cellular or wifi signal, such as a cell phone or mapping device. + +##Alternatives: + +One alternative is to do nothing, and keep onboarding fees as zero (0). However, this would impede the daily HNT emissions to the MOBILE SubDAO treasury since the A score would remain zero (0). + +Another alternative is to change the way the A score is calculated to benefit the HNT emissions of the MOBILE Network; however, this would require a vote with veHNT instead of veMOBILE. + +##Unresolved Question: +None + +##Deployment Impact: +Output deployers will now need to pay onboarding fees for any newly onboarded output devices after the implementation of this HIP. + +The Helium Foundation will need to create a way to track and manage output device onboards and ensure fees paid for output devices prior to the October 31, 2023 deadline. Further, the foundation will need to ensure that the day after the passing of this HIP that the A score for the MOBILE SubDAO is correctly updated to reflect the total amount of indoor and outdoor output devices, as well as their associated fees for the MOBILE SubDAO. + +##Success Metrics: +The primary success metric will be greater daily HNT emissions to the MOBILE SubDAO treasury. From 938cb8a4035e4ecb2dc60786caec83a42bb1c6ae Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Thu, 15 Jun 2023 06:21:23 -0700 Subject: [PATCH 12/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...work-onboarding-fees-and-device-definition.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index f459638fc..e0cfef3c1 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -6,10 +6,10 @@ - Tracking Issue: # - Voting Requirements: veMOBILE -##Summary +## Summary This proposal designates the Onboarding Fees for the onboarding of MOBILE subDAO devices. Also provides a definition of a Device within the MOBILE subDAO for the purposes of calculating the $A$ factor of the DAO Utility Score. An Onboarding Fee of $40 will set immedaitely upon passing; and, then once the necessary coding is complete, an Onboarding Fee of $10 will be set for Indoor Radio devices and $20 for Outdoor Radio devices. Indoor Devices and Outdoor Devices are defined in the detailed explanation section. -##Motivation +## Motivation As implemented in HIP51, a DAO Utility Score is used to determine the daily emissions of HNT to each SubDAO treasury. The equation for this calculation is noted below: $\text{DAO Utility Score} = V \times D \times A$ @@ -22,29 +22,29 @@ At its current rate, the $A$ score in the equation for MOBILE is $0$ (zero) as, This HIP only applies to Devices onboarded after the passing of this HIP. Any Device onboarded prior to the passing of this HIP are to be considered already onboarded. -##Stakeholders +## Stakeholders Stakeholders are all current and future Device deployers within the MOBILE subDAO. HNT holders will also be impacted from the burning of HNT by each Device paying its Onboarding Fees. -##Detailed Explanation +## Detailed Explanation At the passing of this HIP, all Devices onboarded to the MOBILE Network will be required to pay an onboarding fee; which is paid via $USD equivalent in Data Credits (DC). With this HIP, a way to track, manage, and burn Data Credits used to pay the Onboarding Fees for any newly onboarded Devices will need to be created by the Helium Foundation. Therefore, any output devices onboarded the day after the passing of this HIP will be required to pay their onboarding fees no later than October 31st, 2023. This allows time for the Helium Foundation to create a way to track and manage this process. If any Device onboarded to the MOBILE Network after the passing of this HIP do not pay their onboarding fees by October 31st, 2023, their output device will become inactive and not earn any Proof-of-Coverage or Data Transfer rewards until the fee is paid in full. Such Devices will be consider as if not onboarded. -###Definitions +### Definitions Indoor Device (AKA indoor radio) - A device that outputs a cellular or wifi signal to which End Users connect that is designed to be installed indoors. Outdoor Device (AKA outdoor radio) - A device that outputs a cellular or wifi signal to which End Users connect that is designed to be installed oudoors. At the time of this HIP's writing, both Indoor and Outdoor Devices would include CBRS Radioa and carrier-offloading Wifi (coWifi) devices. End User - A device that connects to a cellular or wifi signal, such as a cell phone, tablet, laptop, etc. -##Unresolved Questions +## Unresolved Questions Confirmation that the Helium Foundation can certainly complete the needed work by the stated deadline of October 31, 2023. Conversations have been had various members of the FOundation and it has been conveyed that approximately 90 days would be needed to complete the work. -##Deployment Impact +## Deployment Impact Operators of Devices will now need to pay Onboarding Fees for any newly onboarded output devices after the implementation of this HIP. The Helium Foundation will need to create a way to track and manage output device onboards and ensure fees paid for output devices prior to the October 31, 2023 deadline. Further, the foundation will need to ensure that after the passing of this HIP that the $A$ score of the DAO Utility Score for the MOBILE SubDAO is correctly updated to reflect the total amount of indoor and outdoor output devices, as well as their associated fees for the MOBILE SubDAO. -##Success Metrics +## Success Metrics The success metric will be the implementation of Onboarding Fees for all new Devices. From e5b4f2b7836ad0a48d0fe8b2f98ec955b517c10f Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Thu, 15 Jun 2023 06:22:14 -0700 Subject: [PATCH 13/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...ate-mobile-network-onboarding-fees-and-device-definition.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index e0cfef3c1..639af1389 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -32,8 +32,11 @@ With this HIP, a way to track, manage, and burn Data Credits used to pay the Onb ### Definitions Indoor Device (AKA indoor radio) - A device that outputs a cellular or wifi signal to which End Users connect that is designed to be installed indoors. + Outdoor Device (AKA outdoor radio) - A device that outputs a cellular or wifi signal to which End Users connect that is designed to be installed oudoors. + At the time of this HIP's writing, both Indoor and Outdoor Devices would include CBRS Radioa and carrier-offloading Wifi (coWifi) devices. + End User - A device that connects to a cellular or wifi signal, such as a cell phone, tablet, laptop, etc. ## Unresolved Questions From ef814e19bc9358dba41a5c83e0b1d910cf51c8b2 Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Thu, 15 Jun 2023 06:23:10 -0700 Subject: [PATCH 14/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...e-mobile-network-onboarding-fees-and-device-definition.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index 639af1389..29016811a 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -31,11 +31,10 @@ At the passing of this HIP, all Devices onboarded to the MOBILE Network will be With this HIP, a way to track, manage, and burn Data Credits used to pay the Onboarding Fees for any newly onboarded Devices will need to be created by the Helium Foundation. Therefore, any output devices onboarded the day after the passing of this HIP will be required to pay their onboarding fees no later than October 31st, 2023. This allows time for the Helium Foundation to create a way to track and manage this process. If any Device onboarded to the MOBILE Network after the passing of this HIP do not pay their onboarding fees by October 31st, 2023, their output device will become inactive and not earn any Proof-of-Coverage or Data Transfer rewards until the fee is paid in full. Such Devices will be consider as if not onboarded. ### Definitions -Indoor Device (AKA indoor radio) - A device that outputs a cellular or wifi signal to which End Users connect that is designed to be installed indoors. +Indoor Device (AKA indoor radio) - A device that outputs a cellular or wifi signal to which End Users connect that is designed to be installed indoors. At the time of this HIP's writing, this would include CBRS Radios and carrier-offloading Wifi (coWifi) devices. -Outdoor Device (AKA outdoor radio) - A device that outputs a cellular or wifi signal to which End Users connect that is designed to be installed oudoors. +Outdoor Device (AKA outdoor radio) - A device that outputs a cellular or wifi signal to which End Users connect that is designed to be installed oudoors. At the time of this HIP's writing, this would include CBRS Radios and carrier-offloading Wifi (coWifi) devices. - At the time of this HIP's writing, both Indoor and Outdoor Devices would include CBRS Radioa and carrier-offloading Wifi (coWifi) devices. End User - A device that connects to a cellular or wifi signal, such as a cell phone, tablet, laptop, etc. From fd0104a7a9af03edc4f62f1b407915e2117e6281 Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Thu, 15 Jun 2023 06:24:24 -0700 Subject: [PATCH 15/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...nate-mobile-network-onboarding-fees-and-device-definition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index 29016811a..2f5fc1d48 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -39,7 +39,7 @@ Outdoor Device (AKA outdoor radio) - A device that outputs a cellular or wifi si End User - A device that connects to a cellular or wifi signal, such as a cell phone, tablet, laptop, etc. ## Unresolved Questions -Confirmation that the Helium Foundation can certainly complete the needed work by the stated deadline of October 31, 2023. Conversations have been had various members of the FOundation and it has been conveyed that approximately 90 days would be needed to complete the work. +Confirmation that the Helium Foundation can certainly complete the needed work by the stated deadline of October 31, 2023. Impromptu conversations have been had with various members of the Foundation and it is believed that approximately 90 days would be needed to complete the work. ## Deployment Impact Operators of Devices will now need to pay Onboarding Fees for any newly onboarded output devices after the implementation of this HIP. From 3dc12794d517b3cb851e6a3b18dc13a7f55247eb Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Thu, 15 Jun 2023 06:24:56 -0700 Subject: [PATCH 16/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...te-mobile-network-onboarding-fees-and-device-definition.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index 2f5fc1d48..898e3e60b 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -13,9 +13,13 @@ This proposal designates the Onboarding Fees for the onboarding of MOBILE subDAO As implemented in HIP51, a DAO Utility Score is used to determine the daily emissions of HNT to each SubDAO treasury. The equation for this calculation is noted below: $\text{DAO Utility Score} = V \times D \times A$ + Where + $V = \text{max}(1, veHNT_{DNP})$ + $D = \text{max}(1, \sqrt{\text{DNP DCs burned in USD}})$ + $A = \text{max}(1, \sqrt[4]{\text{DNP Active Device Count} \times \text{DNP Device Activation Fee}})$ At its current rate, the $A$ score in the equation for MOBILE is $0$ (zero) as, currently, there is not any prescribed onboarding fees for the MOBILE network. The implementation of this HIP would inscribe onboarding fees for output devices as prescribed by HIP51 which would allow a more appropriate calculation of the DAO Utility Score. From be0083c81af86e43deb6c9dff76ba114c9e8cfc4 Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Thu, 15 Jun 2023 06:30:17 -0700 Subject: [PATCH 17/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...te-mobile-network-onboarding-fees-and-device-definition.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index 898e3e60b..a0c707393 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -7,7 +7,7 @@ - Voting Requirements: veMOBILE ## Summary -This proposal designates the Onboarding Fees for the onboarding of MOBILE subDAO devices. Also provides a definition of a Device within the MOBILE subDAO for the purposes of calculating the $A$ factor of the DAO Utility Score. An Onboarding Fee of $40 will set immedaitely upon passing; and, then once the necessary coding is complete, an Onboarding Fee of $10 will be set for Indoor Radio devices and $20 for Outdoor Radio devices. Indoor Devices and Outdoor Devices are defined in the detailed explanation section. +This proposal designates the Onboarding Fees for the onboarding of MOBILE subDAO devices. Also provides a definition of a Device within the MOBILE subDAO for the purposes of calculating the $A$ factor of the DAO Utility Score. An Onboarding Fee of $40 will set immediately upon passing and apply to HIP51-inherited Defined Devices; and, then once the necessary coding is complete, an Onboarding Fee of $10 will be set for Indoor Devices and $20 for Outdoor Devices. Indoor Devices and Outdoor Devices are defined in the detailed explanation section. ## Motivation As implemented in HIP51, a DAO Utility Score is used to determine the daily emissions of HNT to each SubDAO treasury. The equation for this calculation is noted below: @@ -35,6 +35,8 @@ At the passing of this HIP, all Devices onboarded to the MOBILE Network will be With this HIP, a way to track, manage, and burn Data Credits used to pay the Onboarding Fees for any newly onboarded Devices will need to be created by the Helium Foundation. Therefore, any output devices onboarded the day after the passing of this HIP will be required to pay their onboarding fees no later than October 31st, 2023. This allows time for the Helium Foundation to create a way to track and manage this process. If any Device onboarded to the MOBILE Network after the passing of this HIP do not pay their onboarding fees by October 31st, 2023, their output device will become inactive and not earn any Proof-of-Coverage or Data Transfer rewards until the fee is paid in full. Such Devices will be consider as if not onboarded. ### Definitions +HIP51-inherited Defined Devices (AKA gateway) - A gateway device that allows mobile network radios to be attached to which End USers connect. + Indoor Device (AKA indoor radio) - A device that outputs a cellular or wifi signal to which End Users connect that is designed to be installed indoors. At the time of this HIP's writing, this would include CBRS Radios and carrier-offloading Wifi (coWifi) devices. Outdoor Device (AKA outdoor radio) - A device that outputs a cellular or wifi signal to which End Users connect that is designed to be installed oudoors. At the time of this HIP's writing, this would include CBRS Radios and carrier-offloading Wifi (coWifi) devices. From 6e0da486aa385892d80de238d94c0659f2b99804 Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Thu, 15 Jun 2023 06:33:09 -0700 Subject: [PATCH 18/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...nate-mobile-network-onboarding-fees-and-device-definition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index a0c707393..e8b161e95 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -35,7 +35,7 @@ At the passing of this HIP, all Devices onboarded to the MOBILE Network will be With this HIP, a way to track, manage, and burn Data Credits used to pay the Onboarding Fees for any newly onboarded Devices will need to be created by the Helium Foundation. Therefore, any output devices onboarded the day after the passing of this HIP will be required to pay their onboarding fees no later than October 31st, 2023. This allows time for the Helium Foundation to create a way to track and manage this process. If any Device onboarded to the MOBILE Network after the passing of this HIP do not pay their onboarding fees by October 31st, 2023, their output device will become inactive and not earn any Proof-of-Coverage or Data Transfer rewards until the fee is paid in full. Such Devices will be consider as if not onboarded. ### Definitions -HIP51-inherited Defined Devices (AKA gateway) - A gateway device that allows mobile network radios to be attached to which End USers connect. +HIP51-inherited Defined Devices (AKA gateway) - A gateway device that allows mobile network radios to be attached to which End Users connect. Indoor Device (AKA indoor radio) - A device that outputs a cellular or wifi signal to which End Users connect that is designed to be installed indoors. At the time of this HIP's writing, this would include CBRS Radios and carrier-offloading Wifi (coWifi) devices. From 05e9db5faceb2500604f9e320df966dd4deb1d42 Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Thu, 15 Jun 2023 06:36:31 -0700 Subject: [PATCH 19/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...nate-mobile-network-onboarding-fees-and-device-definition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index e8b161e95..c7652895f 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -32,7 +32,7 @@ Stakeholders are all current and future Device deployers within the MOBILE subDA ## Detailed Explanation At the passing of this HIP, all Devices onboarded to the MOBILE Network will be required to pay an onboarding fee; which is paid via $USD equivalent in Data Credits (DC). -With this HIP, a way to track, manage, and burn Data Credits used to pay the Onboarding Fees for any newly onboarded Devices will need to be created by the Helium Foundation. Therefore, any output devices onboarded the day after the passing of this HIP will be required to pay their onboarding fees no later than October 31st, 2023. This allows time for the Helium Foundation to create a way to track and manage this process. If any Device onboarded to the MOBILE Network after the passing of this HIP do not pay their onboarding fees by October 31st, 2023, their output device will become inactive and not earn any Proof-of-Coverage or Data Transfer rewards until the fee is paid in full. Such Devices will be consider as if not onboarded. +With this HIP, a way to track, manage, and burn Data Credits used to pay the Onboarding Fees for any newly onboarded Devices will need to be created by the Helium Foundation. Therefore, any output devices onboarded after the passing of this HIP will be required to pay their onboarding fees no later than October 31st, 2023. This allows time for the Helium Foundation to create a way to track and manage this process. If any Device onboarded to the MOBILE Network after the passing of this HIP do not pay their onboarding fees by October 31st, 2023, their output device will become inactive and not earn any Proof-of-Coverage or Data Transfer rewards until the fee is paid in full. Such Devices will be consider as if not onboarded. ### Definitions HIP51-inherited Defined Devices (AKA gateway) - A gateway device that allows mobile network radios to be attached to which End Users connect. From f56149de8b996a10a6449a9d113a2b0bf7f1924a Mon Sep 17 00:00:00 2001 From: Andy Zyvoloski <104723888+heatedlime@users.noreply.github.com> Date: Thu, 15 Jun 2023 10:07:41 -0500 Subject: [PATCH 20/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md Merged two drafts together and made small edits. --- ...k-onboarding-fees-and-device-definition.md | 79 ++++--------------- 1 file changed, 15 insertions(+), 64 deletions(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index c7652895f..51a998bb8 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -7,7 +7,7 @@ - Voting Requirements: veMOBILE ## Summary -This proposal designates the Onboarding Fees for the onboarding of MOBILE subDAO devices. Also provides a definition of a Device within the MOBILE subDAO for the purposes of calculating the $A$ factor of the DAO Utility Score. An Onboarding Fee of $40 will set immediately upon passing and apply to HIP51-inherited Defined Devices; and, then once the necessary coding is complete, an Onboarding Fee of $10 will be set for Indoor Devices and $20 for Outdoor Devices. Indoor Devices and Outdoor Devices are defined in the detailed explanation section. +This proposal designates the Onboarding Fees for the onboarding of MOBILE subDAO devices. It also provides a definition of a Device within the MOBILE subDAO for the purposes of calculating the $A$ factor of the DAO Utility Score. An Onboarding Fee of $40 will set immediately upon passing and apply to HIP51-inherited Defined Devices; and, then once the necessary coding is complete, an Onboarding Fee of $10 will be set for Indoor Devices and $20 for Outdoor Devices. Indoor Devices and Outdoor Devices are defined in the detailed explanation section. ## Motivation As implemented in HIP51, a DAO Utility Score is used to determine the daily emissions of HNT to each SubDAO treasury. The equation for this calculation is noted below: @@ -35,15 +35,24 @@ At the passing of this HIP, all Devices onboarded to the MOBILE Network will be With this HIP, a way to track, manage, and burn Data Credits used to pay the Onboarding Fees for any newly onboarded Devices will need to be created by the Helium Foundation. Therefore, any output devices onboarded after the passing of this HIP will be required to pay their onboarding fees no later than October 31st, 2023. This allows time for the Helium Foundation to create a way to track and manage this process. If any Device onboarded to the MOBILE Network after the passing of this HIP do not pay their onboarding fees by October 31st, 2023, their output device will become inactive and not earn any Proof-of-Coverage or Data Transfer rewards until the fee is paid in full. Such Devices will be consider as if not onboarded. ### Definitions -HIP51-inherited Defined Devices (AKA gateway) - A gateway device that allows mobile network radios to be attached to which End Users connect. -Indoor Device (AKA indoor radio) - A device that outputs a cellular or wifi signal to which End Users connect that is designed to be installed indoors. At the time of this HIP's writing, this would include CBRS Radios and carrier-offloading Wifi (coWifi) devices. +Device - A device includes but is not limited to a any hotspot/radio/router/modem or other output device that is onboarded to the MOBILE network that is creating a cellular or Wi-Fi Helium 5G signal in which End Users can connect to access the internet. At the writing of this HIP, the two types of devices can include Indoor Devices and Outdoor Devices, which are defined below. -Outdoor Device (AKA outdoor radio) - A device that outputs a cellular or wifi signal to which End Users connect that is designed to be installed oudoors. At the time of this HIP's writing, this would include CBRS Radios and carrier-offloading Wifi (coWifi) devices. +Active Device - An active device is defined as a device that is creating valid coverage for that epoch. + +Indoor Device (AKA indoor radio or wi-Fi unit) - A device that outputs a cellular or wifi signal to which End Users connect that is designed to be installed indoors. At the time of this HIP's writing, this would include CBRS Radios and carrier-offloading Wifi (coWifi) devices. + +Outdoor Device (AKA outdoor radio or wi-Fi unit) - A device that outputs a cellular or wifi signal to which End Users connect that is designed to be installed oudoors. At the time of this HIP's writing, this would include CBRS Radios and carrier-offloading Wifi (coWifi) devices. - End User - A device that connects to a cellular or wifi signal, such as a cell phone, tablet, laptop, etc. +### Relocation/Reassertion Fees +Relocation and or re-asserting a device location shall not occur any fee. + +##Alternatives: + +One alternative is to do nothing, and keep onboarding fees as zero (0). However, this would impede the daily HNT emissions to the MOBILE SubDAO treasury since the A score would remain zero (0). + ## Unresolved Questions Confirmation that the Helium Foundation can certainly complete the needed work by the stated deadline of October 31, 2023. Impromptu conversations have been had with various members of the Foundation and it is believed that approximately 90 days would be needed to complete the work. @@ -53,65 +62,7 @@ Operators of Devices will now need to pay Onboarding Fees for any newly onboarde The Helium Foundation will need to create a way to track and manage output device onboards and ensure fees paid for output devices prior to the October 31, 2023 deadline. Further, the foundation will need to ensure that after the passing of this HIP that the $A$ score of the DAO Utility Score for the MOBILE SubDAO is correctly updated to reflect the total amount of indoor and outdoor output devices, as well as their associated fees for the MOBILE SubDAO. ## Success Metrics -The success metric will be the implementation of Onboarding Fees for all new Devices. - - - - -********************************************************************************************************************************************** - -# HIP XX: MOBILE Network Onboarding Fee -- Authors: [Andy Zyvoloski](https://github.com/heatedlime), [Keith Rettig](https://github.com/keithrettig) -- Start Date: 6/14/2023 -- Category: Technical & Economic -- Original HIP PR: # -- Tracking Issue: # -- Voting Requirements: veMOBILE - -##Summary: -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 the day after the passing of this HIP. Output devices are defined in the detailed summary section below. - -##Motivation: -As implemented in HIP 51, a DAO Utility Score is used to determine the daily emissions of HNT to each SubDAO treasury. The equation for this calculation is noted below: - -$\text{DAO Utility Score} = V \times D \times A$ -Where -$V = \text{max}(1, veHNT_{DNP})$ -$D = \text{max}(1, \sqrt{\text{DNP DCs burned in USD}})$ -$A = \text{max}(1, \sqrt[4]{\text{DNP Active Device Count} \times \text{DNP Device Activation Fee}})$ - -At its current rate, the A score in the equation for MOBILE is zero (0), as there currently is not any prescribed onboarding fees for the MOBILE network. The implementation of this HIP would inscribe onboarding fees for output devices which would significantly boost the output of the A score, which in turn, would effectively provide a significant increase to the daily HNT emissions sent to the MOBILE SubDAO treasury. - -This HIP only applies to output devices onboarded the day after the passing of this HIP. Any output devices onboarded prior to the passing of this HIP are already onboarded, and as such, are not required to pay such fee. - -##Stakeholders: -Stakeholders are all current and future output device deployers on the MOBILE network. - -HNT holders will also benefit from the burning of HNT for each newly onboarded output device. - -##Detailed Explanation: - -At the passing of this HIP, all outdoor and indoor output devices onboarded to the MOBILE network will be required to pay an onboarding fee, which is paid via data credits. - -With this HIP, a way to track, manage and burn HNT/data credits for newly onboarded output devices will need to be created by the Helium Foundation. Therefore, any output devices onboarded the day after the passing of this HIP will be required to pay their onboard fee no later than October 31st, 2023. This allows time for the Helium Foundation to create a way to track and manage this process. If any output devices onboarded to the MOBILE network the day after the passing of this HIP do not pay their onboarding fees by October 31st, 2023, their output device will become inactive, and not earn any PoC or data transfer rewards until the fee is paid in full. - -###Definitions -Output Device (AKA Gateway) - A device that outputs a cellular or wifi signal to which End Users connect. For example, this would include a CBRS Radio or a carrier-offloading Wifi (coWifi) unit. -End User - A device that connects to a cellular or wifi signal, such as a cell phone or mapping device. - -##Alternatives: - -One alternative is to do nothing, and keep onboarding fees as zero (0). However, this would impede the daily HNT emissions to the MOBILE SubDAO treasury since the A score would remain zero (0). - -Another alternative is to change the way the A score is calculated to benefit the HNT emissions of the MOBILE Network; however, this would require a vote with veHNT instead of veMOBILE. - -##Unresolved Question: -None +The success metric will be the implementation of Onboarding Fees for all new Devices, which will lead to higher daily HNT emissions to the MOBILE SubDAO treasury. -##Deployment Impact: -Output deployers will now need to pay onboarding fees for any newly onboarded output devices after the implementation of this HIP. -The Helium Foundation will need to create a way to track and manage output device onboards and ensure fees paid for output devices prior to the October 31, 2023 deadline. Further, the foundation will need to ensure that the day after the passing of this HIP that the A score for the MOBILE SubDAO is correctly updated to reflect the total amount of indoor and outdoor output devices, as well as their associated fees for the MOBILE SubDAO. -##Success Metrics: -The primary success metric will be greater daily HNT emissions to the MOBILE SubDAO treasury. From fba969a0fd9a29a916cd4f03911e41b8b78ebeb0 Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Thu, 15 Jun 2023 08:52:03 -0700 Subject: [PATCH 21/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...nate-mobile-network-onboarding-fees-and-device-definition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index 51a998bb8..c4553d723 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -36,7 +36,7 @@ With this HIP, a way to track, manage, and burn Data Credits used to pay the Onb ### Definitions -Device - A device includes but is not limited to a any hotspot/radio/router/modem or other output device that is onboarded to the MOBILE network that is creating a cellular or Wi-Fi Helium 5G signal in which End Users can connect to access the internet. At the writing of this HIP, the two types of devices can include Indoor Devices and Outdoor Devices, which are defined below. +Device - A device includes, but is not limited to, any hotspot/radio/router/modem or other output device that is onboarded to the MOBILE network that is creating a cellular or Wi-Fi Helium 5G signal in which End Users can connect to access the internet. At the writing of this HIP, the two types of devices can include Indoor Devices and Outdoor Devices, which are defined below. Active Device - An active device is defined as a device that is creating valid coverage for that epoch. From 787f2ada331af627a188742cd556035ef524d832 Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Thu, 15 Jun 2023 08:52:50 -0700 Subject: [PATCH 22/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...obile-network-onboarding-fees-and-device-definition.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index c4553d723..f68386340 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -49,9 +49,8 @@ End User - A device that connects to a cellular or wifi signal, such as a cell p ### Relocation/Reassertion Fees Relocation and or re-asserting a device location shall not occur any fee. -##Alternatives: - -One alternative is to do nothing, and keep onboarding fees as zero (0). However, this would impede the daily HNT emissions to the MOBILE SubDAO treasury since the A score would remain zero (0). +## Alternatives +One alternative is to do nothing and keep onboarding fees as zero (0). However, this would impede the daily HNT emissions to the MOBILE SubDAO treasury since the A score would remain zero (0). ## Unresolved Questions Confirmation that the Helium Foundation can certainly complete the needed work by the stated deadline of October 31, 2023. Impromptu conversations have been had with various members of the Foundation and it is believed that approximately 90 days would be needed to complete the work. @@ -63,6 +62,3 @@ The Helium Foundation will need to create a way to track and manage output devic ## Success Metrics The success metric will be the implementation of Onboarding Fees for all new Devices, which will lead to higher daily HNT emissions to the MOBILE SubDAO treasury. - - - From 05ded4733149c4eb8955e8a10f38b504a43395ee Mon Sep 17 00:00:00 2001 From: Andy Zyvoloski <104723888+heatedlime@users.noreply.github.com> Date: Sun, 18 Jun 2023 11:14:07 -0500 Subject: [PATCH 23/56] Delete 0000-MOBILE-Oracle-Hex-Boosting.md Added to new branch. --- 0000-MOBILE-Oracle-Hex-Boosting.md | 129 ----------------------------- 1 file changed, 129 deletions(-) delete mode 100644 0000-MOBILE-Oracle-Hex-Boosting.md diff --git a/0000-MOBILE-Oracle-Hex-Boosting.md b/0000-MOBILE-Oracle-Hex-Boosting.md deleted file mode 100644 index 0b4f8d139..000000000 --- a/0000-MOBILE-Oracle-Hex-Boosting.md +++ /dev/null @@ -1,129 +0,0 @@ -Author: [Andy Zyvoloski](https://github.com/heatedlime) - -Start Date: 6/6/2023 - -Category: Technical & Economic - -Original HIP PR: # - -Tracking Issue: # - -Voting Requirements: veMOBILE - - -## Summary: -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. - -Further, this HIP proposes adding the first Oracle, the Carrier Coverage Oracle, which incentives deployments in areas in which T-Mobile has pre-existing coverage. - - -## Motivation: -HIP 74 was passed to incorporate obstruction data and radio signal power into the PoC reward model; however, it weighs all hexes equally, even if there's a low probability of actual coverage being needed in that area. This proposal aims to improve the value of the network coverage by incentivizing users to deploy radios in areas where Oracles have determined Service Providers are more likely to need coverage. - -## Stakeholders: -The stakeholders of this proposal are Service Providers, radio deployers, and network users. Radio deployers can benefit from increased rewards for providing coverage in areas where coverage is needed. - -## Detailed Explanation: -MOBILE Boosting Oracles (refer herewith as “Oracles”) are data sources which are used to estimate how useful mobile coverage will be in a specific area. This HIP proposes allowing Oracles to be established to help guide deployments in areas that need more coverage. Oracles will be used to give applicable hexes boosts (increasing or decreasing) based on the area they are deployed in. Any Oracle multiplier within a single res12 hex will stack onto one another. Oracle boosting shall also stack with any other Mobile boosts, such as the Service Provider boosts defined in HIP 84 (assuming HIP 84 passes). - -The ranking system established in HIP 85 (assuming HIP 85 passes) will serve as a baseline multiplier. This means that once all boosts are aggregated, they will be multiplied against the MCP after the baseline multiplier defined in HIP 85 is applied. For example, if the MCP after HIP 85 calculations are 0, the total boosts that aggregate to 5X does not grant any additional MCP, and it will be 0, as 0 X 5 = 0. -Examples of how this works can be found below within the Carrier Coverage Oracle section. - -The data sources from Oracles are to be updated no less than once per year. The Oracle updates are to be reviewed by a MOBILE Governance Group (or MOBILE Working Group if no Governance Group exists) prior to implementation to ensure and confirm the Oracle data was updated correctly. - -### Changes to Oracle Boosts -As the MOBILE network matures, Oracle boosts may need to be fine tuned or changed. Therefore, the boosts and data type for each boost shall be implemented as chain variables. In order for these chain variables to be modified, or deleted, a MOBILE Governance Group (or MOBILE Working Group if no Governance Group exists) must create an Oracle Change Proposal. The proposal will then be presented and discussed by the Group, in which a general consensus must be reached (consensus defined by the Group). Once consensus is reached, the proposal will be put to a vote by the community, with the voting requirement being veMOBILE. - -The proposal must be announced within the Official Helium Community Discord Server under the “Governance-Announcement” channel (or similar channel if the “Governance-Announcement” channel is removed), at least five (5) calendar days prior to the start of voting. Voting shall remain open for seven (7) calendar days. A 66.67% vote in favor of the change(s) must be reached in order for the vote to pass. - -A new vote with the same or modified change(s) to that Oracle may be put to vote by the community again with Group consensus no earlier than 60 calendar days after the last voting has ended. - - -### Carrier Coverage Oracle -Coverage areas that are already covered by the top mobile carriers, such as T-Mobile, have already been identified as areas in which there’s a documented supply and demand for data. Therefore, this HIP proposes creating the first MOBILE Boosting Oracle, the Carrier Coverage Oracle that utilizes the existing T-Mobile coverage map (https://www.t-mobile.com/coverage/coverage-map) to add a boost to PoC Modeled Coverage Points defined in HIP 74 based on the type of coverage T-Mobile offers in that res12 hex. This HIP covers both indoor and outdoor CBRS radios. - -From reviewing the T-Mobile coverage map below of Minneapolis Minnesota and its surrounding suburbs, as well as other large cities within the US, it can be noted that T-Mobile coverage primarily consists of 5G Ultra Capacity and 5G Extended Range in populated cities. These are areas in which T-Mobile have deployed capital and infrastructure to increase and enhance coverage. Thus, one can assume data use in these areas are higher than data use in 4G LTE, 3G/2G areas. - -![](https://user-images.githubusercontent.com/104723888/243865314-85ddc953-d767-4cdf-9556-1b7d5cf8b855.png) - - -The below boosts will be awarded to modeled coverage points for each radio and each res12 hex: - -| T-Mobile Coverage Type | Boost | -|------------------------|-------| -|5G Ultra Capacity | 1.25X | -|5G Extended Range | 1X | -|4G LTE | .5X | -|3G/2G/Partner | .25X | -|No Coverage | .1X | - - -See the examples below of boosts in a single res12 hex. Note, the Baseline Hex Coverage Limit Multiplier is from HIP 85, assuming HIP 85 passes) - -Carrier Coverage Oracle Boost: 1.25X -Made Up Oracle Boost: 3X -Service Provider Boost: 5X -Aggregate Boosts: 9.25X -Potential Signal Level: High -MCP assigned per HIP 74: 16 -Baseline Hex Coverage Limit Multiplier: 0X -MCP assigned per HIP 85: 0 -Total MCP per res12 hex: 0 - -Carrier Coverage Oracle Boost: 1.25X -Made Up Oracle Boost: 3X -Service Provider Boost: 5X -Aggregate Boosts: 9.25X -Potential Signal Level: High -MCP assigned per HIP 74: 16 -Baseline Hex Coverage Limit Multiplier: 1X -MCP assigned per HIP 85: 16 -Total MCP per res12 hex: 148 - -Carrier Coverage Oracle Boost: 1.25X -Made Up Oracle Boost: 3X -Service Provider Boost: None -Aggregate Boosts: 4.5X -Potential Signal Level: High -MCP assigned per HIP 74: 16 -Baseline Hex Coverage Limit Multiplier: .75X -MCP assigned per HIP 85: 12 -Total MCP per res12 hex: 54 - -Carrier Coverage Oracle Boost: 1X -Made Up Oracle Boost: 1X -Service Provider Boost: None -Aggregate Boosts: 2X -Potential Signal Level: High -MCP assigned per HIP 74: 16 -Baseline Hex Coverage Limit Multiplier: 1X -MCP assigned per HIP 85: 16 -Total MCP per res12 hex: 32 - -Carrier Coverage Oracle Boost: .25X -Made Up Oracle Boost: .5X -Service Provider Boost: None -Aggregate Boosts: .75X -Potential Signal Level: High -MCP assigned per HIP 74: 16 -Baseline Hex Coverage Limit Multiplier .25X -MCP assigned per HIP 85: 4 -Total MCP per res12 hex: 3 - -Drawbacks: -The implementation of this proposal could increase the complexity of the Helium Mobile network, and modeled coverage scores. There may be concerns about the accuracy of the population data provided, or the need to update the data regularly. - -Further, there may be areas in which T-Mobile does not provide coverage although there is a need for coverage. However, in these cases, Service Provider Boosts will be able to adjust the boosts as needed. - -Alternatives -An alternative would be allowing radios and hexes to keep earning the defined amount of modeled coverage points as described in HIP 74. However, this may prevent or stagnate the network's growth because HIP 74 does not incentivize deployment of Hotspots to specific areas or regions. - -Unresolved Question -1. Can bodies of water be extracted from the T-Mobile Map and provide a .1X multiplier for coverage over water? -2. Are the current boosts prescribed in this HIP adequate? - -Deployment Impact -Radio deployers will now need to be cognizant of where they are placing their radios in order to maximize modeled coverage point. - -Success Metrics -The primary success metric will be greater coverage on the modeled coverage map in areas where top carriers have already identified as areas that need data. From dcee32226bd14ee2040aab8a2c444bceafe85751 Mon Sep 17 00:00:00 2001 From: Andy Zyvoloski <104723888+heatedlime@users.noreply.github.com> Date: Sun, 18 Jun 2023 16:50:18 -0500 Subject: [PATCH 24/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md Revamped to make the fee per hotspot. --- ...k-onboarding-fees-and-device-definition.md | 50 ++++++------------- 1 file changed, 15 insertions(+), 35 deletions(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index f68386340..5dc549bf4 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -1,4 +1,4 @@ -# HIP XX: Designate MOBILE Network Onboarding Fees and Device Definition +# HIP XX: MOBILE Network Onboarding Fees - Authors: [Andy Zyvoloski](https://github.com/heatedlime), [Keith Rettig](https://github.com/keithrettig) - Start Date: 6/14/2023 - Category: Technical & Economic @@ -7,58 +7,38 @@ - Voting Requirements: veMOBILE ## Summary -This proposal designates the Onboarding Fees for the onboarding of MOBILE subDAO devices. It also provides a definition of a Device within the MOBILE subDAO for the purposes of calculating the $A$ factor of the DAO Utility Score. An Onboarding Fee of $40 will set immediately upon passing and apply to HIP51-inherited Defined Devices; and, then once the necessary coding is complete, an Onboarding Fee of $10 will be set for Indoor Devices and $20 for Outdoor Devices. Indoor Devices and Outdoor Devices are defined in the detailed explanation section. +This HIP proposes implementing a $40 onboard fee paid in Data Credits (DC) for each Hotspot onboarded to the Mobile Network. ## Motivation -As implemented in HIP51, a DAO Utility Score is used to determine the daily emissions of HNT to each SubDAO treasury. The equation for this calculation is noted below: +[HIP-51](https://github.com/helium/HIP/blob/main/0051-helium-dao.md#omni-protocol-poc-incentive-model) specifies the DAO Utility Score, which determines the distribution of HNT between all Helium subDAOs. The Hotspots of each subDAO count towards its Utility Score based on the onboarding fee set by that subDAO. -$\text{DAO Utility Score} = V \times D \times A$ - -Where - -$V = \text{max}(1, veHNT_{DNP})$ - -$D = \text{max}(1, \sqrt{\text{DNP DCs burned in USD}})$ +However, current MOBILE Hotspots, such as Freedomfi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. While HIP-53 specifies that MOBILE Hotspots should burn a $40 onboarding fee, just like IOT Hotspots, the existing implementation only onboarded the IoT network component. All active MOBILE Hotspots have been onboarded to the IOT network, but no separate onboarding process for the MOBILE network was ever implemented. As a result, no onboarding fees have yet been burned towards the MOBILE subDAO, which negatively affects the A Score for the MOBILE SubDAO. The current A Score within the DAO Utility Score is as followed: $A = \text{max}(1, \sqrt[4]{\text{DNP Active Device Count} \times \text{DNP Device Activation Fee}})$ -At its current rate, the $A$ score in the equation for MOBILE is $0$ (zero) as, currently, there is not any prescribed onboarding fees for the MOBILE network. The implementation of this HIP would inscribe onboarding fees for output devices as prescribed by HIP51 which would allow a more appropriate calculation of the DAO Utility Score. - -This HIP only applies to Devices onboarded after the passing of this HIP. Any Device onboarded prior to the passing of this HIP are to be considered already onboarded. ## Stakeholders -Stakeholders are all current and future Device deployers within the MOBILE subDAO. HNT holders will also be impacted from the burning of HNT by each Device paying its Onboarding Fees. -## Detailed Explanation -At the passing of this HIP, all Devices onboarded to the MOBILE Network will be required to pay an onboarding fee; which is paid via $USD equivalent in Data Credits (DC). +Future MOBILE Hotspot owners - Future MOBILE Hotspot owners may have to pay a higher fee to purchase a MOBILE Hotspot, as manufactures may pass the fee onto the consumer. -With this HIP, a way to track, manage, and burn Data Credits used to pay the Onboarding Fees for any newly onboarded Devices will need to be created by the Helium Foundation. Therefore, any output devices onboarded after the passing of this HIP will be required to pay their onboarding fees no later than October 31st, 2023. This allows time for the Helium Foundation to create a way to track and manage this process. If any Device onboarded to the MOBILE Network after the passing of this HIP do not pay their onboarding fees by October 31st, 2023, their output device will become inactive and not earn any Proof-of-Coverage or Data Transfer rewards until the fee is paid in full. Such Devices will be consider as if not onboarded. +MOBILE Hotspot manufacturers - MOBILE Hotspot manufactures will now be required to pay the onboarding fees for each MOBILE Hotspot, as well as retroactively pay onboarding fees for Hotspots already onboarded. -### Definitions - -Device - A device includes, but is not limited to, any hotspot/radio/router/modem or other output device that is onboarded to the MOBILE network that is creating a cellular or Wi-Fi Helium 5G signal in which End Users can connect to access the internet. At the writing of this HIP, the two types of devices can include Indoor Devices and Outdoor Devices, which are defined below. - -Active Device - An active device is defined as a device that is creating valid coverage for that epoch. +## Detailed Explanation +The current A Score factor within the DAO Utility Score noted in the Motivation section above currently accounts for the active devices on that SubDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed $40 MOBILE onboard fee will instantly raise the A Score factor for the MOBILE SubDAO. This will inture increase the daily emssions of HNT into the MOBILE SubDAO treasury. -Indoor Device (AKA indoor radio or wi-Fi unit) - A device that outputs a cellular or wifi signal to which End Users connect that is designed to be installed indoors. At the time of this HIP's writing, this would include CBRS Radios and carrier-offloading Wifi (coWifi) devices. +To show good faith to other SubDAOs, this HIP also requires that manufactures of MOBILE Hotspots that were previously onboarded to the IoT network are required to retroactively pay a $40 onboard fee to the MOBILE SubDAO. -Outdoor Device (AKA outdoor radio or wi-Fi unit) - A device that outputs a cellular or wifi signal to which End Users connect that is designed to be installed oudoors. At the time of this HIP's writing, this would include CBRS Radios and carrier-offloading Wifi (coWifi) devices. +## Drawbacks -End User - A device that connects to a cellular or wifi signal, such as a cell phone, tablet, laptop, etc. +This proposal may require Hotspot Manufactures to increase the costs of MOBILE Gateways. -### Relocation/Reassertion Fees -Relocation and or re-asserting a device location shall not occur any fee. +An additional drawback is that this HIP does not include the number of active radios, which may be a better metric of active devices. However, under guidance of the Helium Foundation, using Hotspots as the active device is easier to implement. ## Alternatives -One alternative is to do nothing and keep onboarding fees as zero (0). However, this would impede the daily HNT emissions to the MOBILE SubDAO treasury since the A score would remain zero (0). +One alternative is to do nothing, and keep onboarding fees as zero (0). However, this would hinder the daily HNT emissions to the MOBILE SubDAO treasury since the A score would remain zero (0). -## Unresolved Questions -Confirmation that the Helium Foundation can certainly complete the needed work by the stated deadline of October 31, 2023. Impromptu conversations have been had with various members of the Foundation and it is believed that approximately 90 days would be needed to complete the work. +Another alternative is to change the way the A score is calculated to benefit the HNT emissions of the MOBILE Network; however, this would require a vote with veHNT instead of veMOBILE. ## Deployment Impact -Operators of Devices will now need to pay Onboarding Fees for any newly onboarded output devices after the implementation of this HIP. - -The Helium Foundation will need to create a way to track and manage output device onboards and ensure fees paid for output devices prior to the October 31, 2023 deadline. Further, the foundation will need to ensure that after the passing of this HIP that the $A$ score of the DAO Utility Score for the MOBILE SubDAO is correctly updated to reflect the total amount of indoor and outdoor output devices, as well as their associated fees for the MOBILE SubDAO. -## Success Metrics -The success metric will be the implementation of Onboarding Fees for all new Devices, which will lead to higher daily HNT emissions to the MOBILE SubDAO treasury. +The primary success metric will be greater daily HNT emissions to the MOBILE SubDAO treasury. From 779117418922aa3c19c5f8e83e48d6638989e696 Mon Sep 17 00:00:00 2001 From: Andy Zyvoloski <104723888+heatedlime@users.noreply.github.com> Date: Sun, 18 Jun 2023 16:51:19 -0500 Subject: [PATCH 25/56] Delete HeatedLime Deleting old verbiage. --- HeatedLime | 59 ------------------------------------------------------ 1 file changed, 59 deletions(-) delete mode 100644 HeatedLime diff --git a/HeatedLime b/HeatedLime deleted file mode 100644 index 0f7017b35..000000000 --- a/HeatedLime +++ /dev/null @@ -1,59 +0,0 @@ -# HIP XX: MOBILE Network Onboarding Fee - -Authors: [Andy Zyvoloski](https://github.com/heatedlime) & @KeithRettig -Start Date: 6/14/2023 -Category: Technical & Economic -Original HIP PR: # -Tracking Issue: # -Voting Requirements: veMOBILE - -##Summary: -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 the day after the passing of this HIP. Output devices are defined in the detailed summary section below. - - -##Motivation: -As implemented in HIP 51, a DAO Utility Score is used to determine the daily emissions of HNT to each SubDAO treasury. The equation for this calculation is noted below: - -$\text{DAO Utility Score} = V \times D \times A$ -Where -$V = \text{max}(1, veHNT_{DNP})$ -$D = \text{max}(1, \sqrt{\text{DNP DCs burned in USD}})$ -$A = \text{max}(1, \sqrt[4]{\text{DNP Active Device Count} \times \text{DNP Device Activation Fee}})$ - -At its current rate, the A score in the equation for MOBILE is zero (0), as there currently is not any prescribed onboarding fees for the MOBILE network. The implementation of this HIP would inscribe onboarding fees for output devices which would significantly boost the output of the A score, which in turn, would effectively provide a significant increase to the daily HNT emissions sent to the MOBILE SubDAO treasury. - -This HIP only applies to output devices onboarded the day after the passing of this HIP. Any output devices onboarded prior to the passing of this HIP are already onboarded, and as such, are not required to pay such fee. - -##Stakeholders: -Stakeholders are all current and future output device deployers on the MOBILE network. - -HNT holders will also benefit with the burning of HNT for each newly onboarded output device. - -##Detailed Explanation: - -At the passing of this HIP, all outdoor and indoor output devices onboarded to the MOBILE network will be required to pay an onboarding fee, which is paid via data credits. With this HIP, a way to track, manage and burn HNT/data credits for newly onboarded output devices needs to be created by the Helium Foundation. Thus, a way to pay onboarding fees needs to be established before they can be paid. Therefore, any output devices onboarded the day after the passing of this HIP will be required to pay their onboard fee no later than October 31st, 2023. This allows time for the Helium Foundation to create a way to track and manage this process. If any output devices onboarded to the MOBILE network the day after the passing of this HIP do not pay their onboarding fees by October 31st, 2023, their output device will become inactive, and not earn any PoC or data transfer rewards until the fee is paid in full. - -###Definitions -Output Device - A device that outputs a cellular or wifi signal for End Users to connect to. For example, this would include a CBRS Radio or a Carrier offload Wifi (CoWifi) unit. -End User - A device that connects to a cellular or wifi signal, such as a cell phone or mapping device. - - - -##Alternatives: -One alternative is to do nothing, and keep onboarding fees as zero (0). However, this would hinder the daily HNT emissions to the MOBILE SubDAO treasury since the A score would remain zero (0). - -Another alternative is to change the way the A score is calculated to benefit the HNT emissions of the MOBILE Network; however, this would require a vote with veHNT instead of veMOBILE. - - -##Unresolved Question: -None - - -##Deployment Impact: -Output deployers will now need to pay onboarding fees for any newly onboarded output devices after the implementation of this HIP. - -The Helium Foundation will need to create a way to track and manage output device onboards and ensure fees paid for output devices prior to the October 31, 2023 deadline. Further, the foundation will need to ensure that the day after the passing of this HIP that the A score for the MOBILE SubDAO is correctly updated to reflect the total amount of indoor and outdoor output devices, as well as their associated fees for the MOBILE SubDAO. - - -##Success Metrics: -The primary success metric will be greater daily HNT emissions to the MOBILE SubDAO treasury. From 2095be187d15015c08a7cec8b91a0ca73ce07fe1 Mon Sep 17 00:00:00 2001 From: Andy Zyvoloski <104723888+heatedlime@users.noreply.github.com> Date: Sun, 18 Jun 2023 16:57:58 -0500 Subject: [PATCH 26/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md fixed typos --- ...e-mobile-network-onboarding-fees-and-device-definition.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index 5dc549bf4..f4c9c38fc 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -24,7 +24,7 @@ Future MOBILE Hotspot owners - Future MOBILE Hotspot owners may have to pay a hi MOBILE Hotspot manufacturers - MOBILE Hotspot manufactures will now be required to pay the onboarding fees for each MOBILE Hotspot, as well as retroactively pay onboarding fees for Hotspots already onboarded. ## Detailed Explanation -The current A Score factor within the DAO Utility Score noted in the Motivation section above currently accounts for the active devices on that SubDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed $40 MOBILE onboard fee will instantly raise the A Score factor for the MOBILE SubDAO. This will inture increase the daily emssions of HNT into the MOBILE SubDAO treasury. +The current A Score factor within the DAO Utility Score noted in the Motivation section above currently accounts for the active devices on that SubDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed $40 MOBILE onboard fee will instantly raise the A Score factor for the MOBILE SubDAO. This will instantly increase the daily emssions of HNT into the MOBILE SubDAO treasury. To show good faith to other SubDAOs, this HIP also requires that manufactures of MOBILE Hotspots that were previously onboarded to the IoT network are required to retroactively pay a $40 onboard fee to the MOBILE SubDAO. @@ -41,4 +41,7 @@ Another alternative is to change the way the A score is calculated to benefit th ## Deployment Impact +After the passing of this HIP, the Helium Foundation will need to modify the A Score code withint the DAO utility Score for the MOBILE Network to reflect the new onboard fee. + +## Success Metrics The primary success metric will be greater daily HNT emissions to the MOBILE SubDAO treasury. From 1d9480cdffd04593710289892244459ce5795d6c Mon Sep 17 00:00:00 2001 From: Andy Zyvoloski <104723888+heatedlime@users.noreply.github.com> Date: Sun, 18 Jun 2023 17:00:55 -0500 Subject: [PATCH 27/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...nate-mobile-network-onboarding-fees-and-device-definition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index f4c9c38fc..31df4f9b2 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -24,7 +24,7 @@ Future MOBILE Hotspot owners - Future MOBILE Hotspot owners may have to pay a hi MOBILE Hotspot manufacturers - MOBILE Hotspot manufactures will now be required to pay the onboarding fees for each MOBILE Hotspot, as well as retroactively pay onboarding fees for Hotspots already onboarded. ## Detailed Explanation -The current A Score factor within the DAO Utility Score noted in the Motivation section above currently accounts for the active devices on that SubDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed $40 MOBILE onboard fee will instantly raise the A Score factor for the MOBILE SubDAO. This will instantly increase the daily emssions of HNT into the MOBILE SubDAO treasury. +The current A Score factor within the DAO Utility Score noted in the Motivation section above currently accounts for the active devices on that SubDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed $40 MOBILE onboard fee will instantly raise the A Score factor for the MOBILE SubDAO. This will instantly increase the daily emissions of HNT into the MOBILE SubDAO treasury. To show good faith to other SubDAOs, this HIP also requires that manufactures of MOBILE Hotspots that were previously onboarded to the IoT network are required to retroactively pay a $40 onboard fee to the MOBILE SubDAO. From 419380cc70ccf54f99e141fe951c9eb983cce6e8 Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Sun, 18 Jun 2023 17:26:16 -0700 Subject: [PATCH 28/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...network-onboarding-fees-and-device-definition.md | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index 31df4f9b2..a6b4b5f3f 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -7,18 +7,17 @@ - Voting Requirements: veMOBILE ## Summary -This HIP proposes implementing a $40 onboard fee paid in Data Credits (DC) for each Hotspot onboarded to the Mobile Network. +This HIP proposes implementing a $40 onboard fee paid in Data Credits (DC) for each Hotspot onboarded to the MOBILE Network. ## Motivation [HIP-51](https://github.com/helium/HIP/blob/main/0051-helium-dao.md#omni-protocol-poc-incentive-model) specifies the DAO Utility Score, which determines the distribution of HNT between all Helium subDAOs. The Hotspots of each subDAO count towards its Utility Score based on the onboarding fee set by that subDAO. -However, current MOBILE Hotspots, such as Freedomfi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. While HIP-53 specifies that MOBILE Hotspots should burn a $40 onboarding fee, just like IOT Hotspots, the existing implementation only onboarded the IoT network component. All active MOBILE Hotspots have been onboarded to the IOT network, but no separate onboarding process for the MOBILE network was ever implemented. As a result, no onboarding fees have yet been burned towards the MOBILE subDAO, which negatively affects the A Score for the MOBILE SubDAO. The current A Score within the DAO Utility Score is as followed: +However, current MOBILE Hotspots, such as Freedomfi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. While HIP-53 specifies that MOBILE Hotspots should burn a $40 onboarding fee, just like IOT Hotspots, the existing implementation only onboarded the IOT network component. All active MOBILE Hotspots have been onboarded to the IOT network, but no separate onboarding process for the MOBILE network was ever implemented. As a result, no onboarding fees have yet been burned towards the MOBILE subDAO, which negatively affects the A Score for the MOBILE SubDAO. The current A Score within the DAO Utility Score is as followed: $A = \text{max}(1, \sqrt[4]{\text{DNP Active Device Count} \times \text{DNP Device Activation Fee}})$ ## Stakeholders - Future MOBILE Hotspot owners - Future MOBILE Hotspot owners may have to pay a higher fee to purchase a MOBILE Hotspot, as manufactures may pass the fee onto the consumer. MOBILE Hotspot manufacturers - MOBILE Hotspot manufactures will now be required to pay the onboarding fees for each MOBILE Hotspot, as well as retroactively pay onboarding fees for Hotspots already onboarded. @@ -26,22 +25,20 @@ MOBILE Hotspot manufacturers - MOBILE Hotspot manufactures will now be required ## Detailed Explanation The current A Score factor within the DAO Utility Score noted in the Motivation section above currently accounts for the active devices on that SubDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed $40 MOBILE onboard fee will instantly raise the A Score factor for the MOBILE SubDAO. This will instantly increase the daily emissions of HNT into the MOBILE SubDAO treasury. -To show good faith to other SubDAOs, this HIP also requires that manufactures of MOBILE Hotspots that were previously onboarded to the IoT network are required to retroactively pay a $40 onboard fee to the MOBILE SubDAO. +To show good faith to other SubDAOs, this HIP also requires that manufactures of MOBILE Hotspots that were previously onboarded to the IOT network are required to retroactively pay a $40 onboard fee to the MOBILE SubDAO. ## Drawbacks - This proposal may require Hotspot Manufactures to increase the costs of MOBILE Gateways. An additional drawback is that this HIP does not include the number of active radios, which may be a better metric of active devices. However, under guidance of the Helium Foundation, using Hotspots as the active device is easier to implement. ## Alternatives -One alternative is to do nothing, and keep onboarding fees as zero (0). However, this would hinder the daily HNT emissions to the MOBILE SubDAO treasury since the A score would remain zero (0). +One alternative is to do nothing, and keep Onboarding Fees as zero (0). However, this would hinder the daily HNT emissions to the MOBILE SubDAO treasury since the A score would remain zero (0). Another alternative is to change the way the A score is calculated to benefit the HNT emissions of the MOBILE Network; however, this would require a vote with veHNT instead of veMOBILE. ## Deployment Impact - -After the passing of this HIP, the Helium Foundation will need to modify the A Score code withint the DAO utility Score for the MOBILE Network to reflect the new onboard fee. +After the passing of this HIP, the Helium Foundation will need to modify the A Score code within the DAO Utility Score for the MOBILE Network to reflect the new onboard fee. ## Success Metrics The primary success metric will be greater daily HNT emissions to the MOBILE SubDAO treasury. From 610c2a22c6ab00038d6690dc396ea4314cbc439c Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Sun, 18 Jun 2023 17:33:55 -0700 Subject: [PATCH 29/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...le-network-onboarding-fees-and-device-definition.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index a6b4b5f3f..2d14e4ab7 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -12,7 +12,7 @@ This HIP proposes implementing a $40 onboard fee paid in Data Credits (DC) for e ## Motivation [HIP-51](https://github.com/helium/HIP/blob/main/0051-helium-dao.md#omni-protocol-poc-incentive-model) specifies the DAO Utility Score, which determines the distribution of HNT between all Helium subDAOs. The Hotspots of each subDAO count towards its Utility Score based on the onboarding fee set by that subDAO. -However, current MOBILE Hotspots, such as Freedomfi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. While HIP-53 specifies that MOBILE Hotspots should burn a $40 onboarding fee, just like IOT Hotspots, the existing implementation only onboarded the IOT network component. All active MOBILE Hotspots have been onboarded to the IOT network, but no separate onboarding process for the MOBILE network was ever implemented. As a result, no onboarding fees have yet been burned towards the MOBILE subDAO, which negatively affects the A Score for the MOBILE SubDAO. The current A Score within the DAO Utility Score is as followed: +However, current MOBILE Hotspots, such as Freedomfi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. While HIP-53 specifies that MOBILE Hotspots should burn a $40 onboarding fee, just like IOT Hotspots, the existing implementation only onboarded the IOT network component. All active MOBILE Hotspots have been onboarded to the IOT network, but no separate onboarding process for the MOBILE network was ever implemented. As a result, no onboarding fees have yet been burned towards the MOBILE subDAO, which negatively affects the A Score for the MOBILE subDAO. The current A Score within the DAO Utility Score is as followed: $A = \text{max}(1, \sqrt[4]{\text{DNP Active Device Count} \times \text{DNP Device Activation Fee}})$ @@ -23,9 +23,9 @@ Future MOBILE Hotspot owners - Future MOBILE Hotspot owners may have to pay a hi MOBILE Hotspot manufacturers - MOBILE Hotspot manufactures will now be required to pay the onboarding fees for each MOBILE Hotspot, as well as retroactively pay onboarding fees for Hotspots already onboarded. ## Detailed Explanation -The current A Score factor within the DAO Utility Score noted in the Motivation section above currently accounts for the active devices on that SubDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed $40 MOBILE onboard fee will instantly raise the A Score factor for the MOBILE SubDAO. This will instantly increase the daily emissions of HNT into the MOBILE SubDAO treasury. +The current A Score factor within the DAO Utility Score noted in the Motivation section above currently accounts for the active devices on that subDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed $40 MOBILE onboard fee will instantly raise the A Score factor for the MOBILE subDAO. This will instantly increase the daily emissions of HNT into the MOBILE subDAO treasury. -To show good faith to other SubDAOs, this HIP also requires that manufactures of MOBILE Hotspots that were previously onboarded to the IOT network are required to retroactively pay a $40 onboard fee to the MOBILE SubDAO. +To show good faith to other subDAOs, this HIP also requires that manufactures of MOBILE Hotspots that were previously onboarded to the IOT network are required to retroactively pay a $40 onboard fee to the MOBILE subDAO. ## Drawbacks This proposal may require Hotspot Manufactures to increase the costs of MOBILE Gateways. @@ -33,7 +33,7 @@ This proposal may require Hotspot Manufactures to increase the costs of MOBILE G An additional drawback is that this HIP does not include the number of active radios, which may be a better metric of active devices. However, under guidance of the Helium Foundation, using Hotspots as the active device is easier to implement. ## Alternatives -One alternative is to do nothing, and keep Onboarding Fees as zero (0). However, this would hinder the daily HNT emissions to the MOBILE SubDAO treasury since the A score would remain zero (0). +One alternative is to do nothing, and keep Onboarding Fees as zero (0). However, this would hinder the daily HNT emissions to the MOBILE subDAO treasury since the A score would remain one (1). Another alternative is to change the way the A score is calculated to benefit the HNT emissions of the MOBILE Network; however, this would require a vote with veHNT instead of veMOBILE. @@ -41,4 +41,4 @@ Another alternative is to change the way the A score is calculated to benefit th After the passing of this HIP, the Helium Foundation will need to modify the A Score code within the DAO Utility Score for the MOBILE Network to reflect the new onboard fee. ## Success Metrics -The primary success metric will be greater daily HNT emissions to the MOBILE SubDAO treasury. +The primary success metric will be greater daily HNT emissions to the MOBILE subDAO treasury. From 3ce92ff850a7966335aee24c4fd6d7f2e8c22e66 Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Sun, 18 Jun 2023 20:07:26 -0700 Subject: [PATCH 30/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...e-mobile-network-onboarding-fees-and-device-definition.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index 2d14e4ab7..72b85625e 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -16,7 +16,6 @@ However, current MOBILE Hotspots, such as Freedomfi and Bobcat 500, contain both $A = \text{max}(1, \sqrt[4]{\text{DNP Active Device Count} \times \text{DNP Device Activation Fee}})$ - ## Stakeholders Future MOBILE Hotspot owners - Future MOBILE Hotspot owners may have to pay a higher fee to purchase a MOBILE Hotspot, as manufactures may pass the fee onto the consumer. @@ -33,12 +32,12 @@ This proposal may require Hotspot Manufactures to increase the costs of MOBILE G An additional drawback is that this HIP does not include the number of active radios, which may be a better metric of active devices. However, under guidance of the Helium Foundation, using Hotspots as the active device is easier to implement. ## Alternatives -One alternative is to do nothing, and keep Onboarding Fees as zero (0). However, this would hinder the daily HNT emissions to the MOBILE subDAO treasury since the A score would remain one (1). +One alternative is to do nothing, and keep Onboarding Fees as zero (0). However, this would impair the daily HNT emissions to the MOBILE subDAO treasury since the A score would remain one (1). Another alternative is to change the way the A score is calculated to benefit the HNT emissions of the MOBILE Network; however, this would require a vote with veHNT instead of veMOBILE. ## Deployment Impact -After the passing of this HIP, the Helium Foundation will need to modify the A Score code within the DAO Utility Score for the MOBILE Network to reflect the new onboard fee. +After the passing of this HIP, the Helium Foundation will need to modify the chain variable that defines the onboarding fee for the MOBILE subDAO. ## Success Metrics The primary success metric will be greater daily HNT emissions to the MOBILE subDAO treasury. From fdca8e92c9f421a6bead83a7713bab991b872910 Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Sun, 18 Jun 2023 20:09:23 -0700 Subject: [PATCH 31/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...nate-mobile-network-onboarding-fees-and-device-definition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index 72b85625e..db33fa2dc 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -27,7 +27,7 @@ The current A Score factor within the DAO Utility Score noted in the Motivation To show good faith to other subDAOs, this HIP also requires that manufactures of MOBILE Hotspots that were previously onboarded to the IOT network are required to retroactively pay a $40 onboard fee to the MOBILE subDAO. ## Drawbacks -This proposal may require Hotspot Manufactures to increase the costs of MOBILE Gateways. +This proposal may require Hotspot Manufactures to increase the costs of MOBILE Network Gateways. An additional drawback is that this HIP does not include the number of active radios, which may be a better metric of active devices. However, under guidance of the Helium Foundation, using Hotspots as the active device is easier to implement. From 9713629fe3a130f2d338deb8152f27f77c4d678d Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Mon, 19 Jun 2023 02:15:16 -0700 Subject: [PATCH 32/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...nate-mobile-network-onboarding-fees-and-device-definition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index db33fa2dc..44c609c2b 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -24,7 +24,7 @@ MOBILE Hotspot manufacturers - MOBILE Hotspot manufactures will now be required ## Detailed Explanation The current A Score factor within the DAO Utility Score noted in the Motivation section above currently accounts for the active devices on that subDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed $40 MOBILE onboard fee will instantly raise the A Score factor for the MOBILE subDAO. This will instantly increase the daily emissions of HNT into the MOBILE subDAO treasury. -To show good faith to other subDAOs, this HIP also requires that manufactures of MOBILE Hotspots that were previously onboarded to the IOT network are required to retroactively pay a $40 onboard fee to the MOBILE subDAO. +To show good faith to other subDAOs, this HIP also requires that manufacturers of MOBILE Hotspots that were previously onboarded to the IOT network are required to retroactively pay a $40 onboard fee to the MOBILE subDAO. ## Drawbacks This proposal may require Hotspot Manufactures to increase the costs of MOBILE Network Gateways. From 7f1050674d116efe95568af1a5f1fc6479273e3a Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Mon, 19 Jun 2023 02:16:07 -0700 Subject: [PATCH 33/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...nate-mobile-network-onboarding-fees-and-device-definition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index 44c609c2b..3c8916eb9 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -27,7 +27,7 @@ The current A Score factor within the DAO Utility Score noted in the Motivation To show good faith to other subDAOs, this HIP also requires that manufacturers of MOBILE Hotspots that were previously onboarded to the IOT network are required to retroactively pay a $40 onboard fee to the MOBILE subDAO. ## Drawbacks -This proposal may require Hotspot Manufactures to increase the costs of MOBILE Network Gateways. +This proposal may require Hotspot Manufacturers to increase the costs of MOBILE Network Gateways. An additional drawback is that this HIP does not include the number of active radios, which may be a better metric of active devices. However, under guidance of the Helium Foundation, using Hotspots as the active device is easier to implement. From 02f48ab1ff4e9810955609916f5e9f5e5dcc924e Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Mon, 19 Jun 2023 02:17:27 -0700 Subject: [PATCH 34/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...nate-mobile-network-onboarding-fees-and-device-definition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index 3c8916eb9..f53b1e80f 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -24,7 +24,7 @@ MOBILE Hotspot manufacturers - MOBILE Hotspot manufactures will now be required ## Detailed Explanation The current A Score factor within the DAO Utility Score noted in the Motivation section above currently accounts for the active devices on that subDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed $40 MOBILE onboard fee will instantly raise the A Score factor for the MOBILE subDAO. This will instantly increase the daily emissions of HNT into the MOBILE subDAO treasury. -To show good faith to other subDAOs, this HIP also requires that manufacturers of MOBILE Hotspots that were previously onboarded to the IOT network are required to retroactively pay a $40 onboard fee to the MOBILE subDAO. +To show good faith to other subDAOs, this HIP also requires that MOBILE Hotspots that were previously onboarded to the MOBILE network are required to retroactively pay a $40 onboard fee to the MOBILE subDAO. ## Drawbacks This proposal may require Hotspot Manufacturers to increase the costs of MOBILE Network Gateways. From ed9ccbf70937e7dce6988671edf1e56a35b7d94d Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Mon, 19 Jun 2023 03:31:56 -0700 Subject: [PATCH 35/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md Some additional spelling errors. Some changes due to new understanding that all gateways were indeed onboarded to the MOBILE network but were done at a $0 rate. --- ...k-onboarding-fees-and-device-definition.md | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index f53b1e80f..c1d1c612c 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -10,31 +10,31 @@ This HIP proposes implementing a $40 onboard fee paid in Data Credits (DC) for each Hotspot onboarded to the MOBILE Network. ## Motivation -[HIP-51](https://github.com/helium/HIP/blob/main/0051-helium-dao.md#omni-protocol-poc-incentive-model) specifies the DAO Utility Score, which determines the distribution of HNT between all Helium subDAOs. The Hotspots of each subDAO count towards its Utility Score based on the onboarding fee set by that subDAO. +[HIP-51](https://github.com/helium/HIP/blob/main/0051-helium-dao.md#omni-protocol-poc-incentive-model) specifies the DAO Utility Score, which determines the distribution of HNT between all Helium subDAOs. The Hotspots of each subDAO count towards its Utility Score based on the Onboarding Fee set by that subDAO. -However, current MOBILE Hotspots, such as Freedomfi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. While HIP-53 specifies that MOBILE Hotspots should burn a $40 onboarding fee, just like IOT Hotspots, the existing implementation only onboarded the IOT network component. All active MOBILE Hotspots have been onboarded to the IOT network, but no separate onboarding process for the MOBILE network was ever implemented. As a result, no onboarding fees have yet been burned towards the MOBILE subDAO, which negatively affects the A Score for the MOBILE subDAO. The current A Score within the DAO Utility Score is as followed: +Current MOBILE Hotspots, such as FreedomFi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. As such, HIP-53 specifies that MOBILE Hotspots should burn a $40 Onboarding Fee to be onboarded to the network. All onboarded MOBILE Hotspots were onboarded to the IOT network with the correct Onboarding Fee of $40 USD, but were onboarded to the MOBILE network with an Onboarding Fee of $0 USD. As a result, $0 USD in Onboarding Fees have been burned towards the MOBILE subDAO's $A$ Factor, which negatively affects the $A$ Score for the MOBILE subDAO. The current $A$ Score within the DAO Utility Score is as followed: $A = \text{max}(1, \sqrt[4]{\text{DNP Active Device Count} \times \text{DNP Device Activation Fee}})$ ## Stakeholders -Future MOBILE Hotspot owners - Future MOBILE Hotspot owners may have to pay a higher fee to purchase a MOBILE Hotspot, as manufactures may pass the fee onto the consumer. +Future MOBILE Hotspot owners - Future MOBILE Hotspot owners may have to pay a higher fee to purchase a MOBILE Hotspot, as manufacturers may pass the fee onto the consumer. -MOBILE Hotspot manufacturers - MOBILE Hotspot manufactures will now be required to pay the onboarding fees for each MOBILE Hotspot, as well as retroactively pay onboarding fees for Hotspots already onboarded. +MOBILE Hotspot manufacturers - MOBILE Hotspot manufacturers will now be required to pay the onboarding fees for each MOBILE Hotspot, as well as retroactively pay onboarding fees for Hotspots already onboarded. ## Detailed Explanation -The current A Score factor within the DAO Utility Score noted in the Motivation section above currently accounts for the active devices on that subDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed $40 MOBILE onboard fee will instantly raise the A Score factor for the MOBILE subDAO. This will instantly increase the daily emissions of HNT into the MOBILE subDAO treasury. +The current $A$ Score factor within the DAO Utility Score noted in the Motivation section above currently accounts for the active devices on that subDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed $40 MOBILE Onboarding Fee will raise the $A$ Score factor for the MOBILE subDAO. This will increase the daily emissions of HNT into the MOBILE subDAO treasury. -To show good faith to other subDAOs, this HIP also requires that MOBILE Hotspots that were previously onboarded to the MOBILE network are required to retroactively pay a $40 onboard fee to the MOBILE subDAO. +This HIP also requires that for MOBILE Hotspots that were previously onboarded at $0 USD, there is to be $40 USD worth of DCs burned to the MOBILE subDAO. This HIP does not require any specific payer for the DCs; it is the responsibility of the MOBILE subDAO to find the payer(s) and to ensure the payment is settled. ## Drawbacks -This proposal may require Hotspot Manufacturers to increase the costs of MOBILE Network Gateways. +This proposal may cause Hotspot Manufacturers to increase the costs of MOBILE Network Gateways. This is not expected to be the case. -An additional drawback is that this HIP does not include the number of active radios, which may be a better metric of active devices. However, under guidance of the Helium Foundation, using Hotspots as the active device is easier to implement. +An additional drawback is that the Onboarding Fees are not based the number of active radios, which may be a better metric of active devices. However, under guidance of the Helium Foundation, using Hotspots as the active device is easier to implement. ## Alternatives -One alternative is to do nothing, and keep Onboarding Fees as zero (0). However, this would impair the daily HNT emissions to the MOBILE subDAO treasury since the A score would remain one (1). +One alternative is to do nothing, and keep Onboarding Fees as zero (0). However, this would impair the daily HNT emissions to the MOBILE subDAO treasury since the $A$ score would remain one (1). -Another alternative is to change the way the A score is calculated to benefit the HNT emissions of the MOBILE Network; however, this would require a vote with veHNT instead of veMOBILE. +Another alternative is to change the way the $A$ score is calculated to benefit the HNT emissions of the MOBILE Network; however, this would require a vote with veHNT instead of veMOBILE. ## Deployment Impact After the passing of this HIP, the Helium Foundation will need to modify the chain variable that defines the onboarding fee for the MOBILE subDAO. From 5ffa9bde39172a00f97090e27939efc8517a1dad Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Mon, 19 Jun 2023 03:32:39 -0700 Subject: [PATCH 36/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...nate-mobile-network-onboarding-fees-and-device-definition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index c1d1c612c..fdb56623c 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -12,7 +12,7 @@ This HIP proposes implementing a $40 onboard fee paid in Data Credits (DC) for e ## Motivation [HIP-51](https://github.com/helium/HIP/blob/main/0051-helium-dao.md#omni-protocol-poc-incentive-model) specifies the DAO Utility Score, which determines the distribution of HNT between all Helium subDAOs. The Hotspots of each subDAO count towards its Utility Score based on the Onboarding Fee set by that subDAO. -Current MOBILE Hotspots, such as FreedomFi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. As such, HIP-53 specifies that MOBILE Hotspots should burn a $40 Onboarding Fee to be onboarded to the network. All onboarded MOBILE Hotspots were onboarded to the IOT network with the correct Onboarding Fee of $40 USD, but were onboarded to the MOBILE network with an Onboarding Fee of $0 USD. As a result, $0 USD in Onboarding Fees have been burned towards the MOBILE subDAO's $A$ Factor, which negatively affects the $A$ Score for the MOBILE subDAO. The current $A$ Score within the DAO Utility Score is as followed: +Current MOBILE Hotspots, such as FreedomFi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. As such, HIP-53 specifies that MOBILE Hotspots should burn a USD $40 Onboarding Fee to be onboarded to the network. All onboarded MOBILE Hotspots were onboarded to the IOT network with the correct Onboarding Fee of $40 USD, but were onboarded to the MOBILE network with an Onboarding Fee of $0 USD. As a result, $0 USD in Onboarding Fees have been burned towards the MOBILE subDAO's $A$ Factor, which negatively affects the $A$ Score for the MOBILE subDAO. The current $A$ Score within the DAO Utility Score is as followed: $A = \text{max}(1, \sqrt[4]{\text{DNP Active Device Count} \times \text{DNP Device Activation Fee}})$ From 9e0ab9cd73750a57bba7fe8dee9a1a4692d3e56f Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Mon, 19 Jun 2023 03:33:37 -0700 Subject: [PATCH 37/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...nate-mobile-network-onboarding-fees-and-device-definition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index fdb56623c..86e685c47 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -12,7 +12,7 @@ This HIP proposes implementing a $40 onboard fee paid in Data Credits (DC) for e ## Motivation [HIP-51](https://github.com/helium/HIP/blob/main/0051-helium-dao.md#omni-protocol-poc-incentive-model) specifies the DAO Utility Score, which determines the distribution of HNT between all Helium subDAOs. The Hotspots of each subDAO count towards its Utility Score based on the Onboarding Fee set by that subDAO. -Current MOBILE Hotspots, such as FreedomFi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. As such, HIP-53 specifies that MOBILE Hotspots should burn a USD $40 Onboarding Fee to be onboarded to the network. All onboarded MOBILE Hotspots were onboarded to the IOT network with the correct Onboarding Fee of $40 USD, but were onboarded to the MOBILE network with an Onboarding Fee of $0 USD. As a result, $0 USD in Onboarding Fees have been burned towards the MOBILE subDAO's $A$ Factor, which negatively affects the $A$ Score for the MOBILE subDAO. The current $A$ Score within the DAO Utility Score is as followed: +Current MOBILE Hotspots, such as FreedomFi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. As such, HIP-53 specifies that MOBILE Hotspots should burn a \$40 USD Onboarding Fee to be onboarded to the network. All onboarded MOBILE Hotspots were onboarded to the IOT network with the correct Onboarding Fee of /$40 USD, but were onboarded to the MOBILE network with an Onboarding Fee of \$0 USD. As a result, \$0 USD in Onboarding Fees have been burned towards the MOBILE subDAO's $A$ Factor, which negatively affects the $A$ Score for the MOBILE subDAO. The current $A$ Score within the DAO Utility Score is as followed: $A = \text{max}(1, \sqrt[4]{\text{DNP Active Device Count} \times \text{DNP Device Activation Fee}})$ From 75db2c3e605b4b87beaf3016a13f9e7263b82329 Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Mon, 19 Jun 2023 03:35:15 -0700 Subject: [PATCH 38/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...nate-mobile-network-onboarding-fees-and-device-definition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index 86e685c47..0cadf6bb3 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -12,7 +12,7 @@ This HIP proposes implementing a $40 onboard fee paid in Data Credits (DC) for e ## Motivation [HIP-51](https://github.com/helium/HIP/blob/main/0051-helium-dao.md#omni-protocol-poc-incentive-model) specifies the DAO Utility Score, which determines the distribution of HNT between all Helium subDAOs. The Hotspots of each subDAO count towards its Utility Score based on the Onboarding Fee set by that subDAO. -Current MOBILE Hotspots, such as FreedomFi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. As such, HIP-53 specifies that MOBILE Hotspots should burn a \$40 USD Onboarding Fee to be onboarded to the network. All onboarded MOBILE Hotspots were onboarded to the IOT network with the correct Onboarding Fee of /$40 USD, but were onboarded to the MOBILE network with an Onboarding Fee of \$0 USD. As a result, \$0 USD in Onboarding Fees have been burned towards the MOBILE subDAO's $A$ Factor, which negatively affects the $A$ Score for the MOBILE subDAO. The current $A$ Score within the DAO Utility Score is as followed: +Current MOBILE Hotspots, such as FreedomFi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. As such, HIP-53 specifies that MOBILE Hotspots should burn a ($)40 USD Onboarding Fee to be onboarded to the network. All onboarded MOBILE Hotspots were onboarded to the IOT network with the correct Onboarding Fee of ($)40 USD, but were onboarded to the MOBILE network with an Onboarding Fee of ($)0 USD. As a result, ($)0 USD in Onboarding Fees have been burned towards the MOBILE subDAO's $A$ Factor, which negatively affects the $A$ Score for the MOBILE subDAO. The current $A$ Score within the DAO Utility Score is as followed: $A = \text{max}(1, \sqrt[4]{\text{DNP Active Device Count} \times \text{DNP Device Activation Fee}})$ From 1a4d125d4f40b43d74c6b07c37bf103239c93970 Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Mon, 19 Jun 2023 03:36:33 -0700 Subject: [PATCH 39/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...nate-mobile-network-onboarding-fees-and-device-definition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index 0cadf6bb3..fed881932 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -12,7 +12,7 @@ This HIP proposes implementing a $40 onboard fee paid in Data Credits (DC) for e ## Motivation [HIP-51](https://github.com/helium/HIP/blob/main/0051-helium-dao.md#omni-protocol-poc-incentive-model) specifies the DAO Utility Score, which determines the distribution of HNT between all Helium subDAOs. The Hotspots of each subDAO count towards its Utility Score based on the Onboarding Fee set by that subDAO. -Current MOBILE Hotspots, such as FreedomFi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. As such, HIP-53 specifies that MOBILE Hotspots should burn a ($)40 USD Onboarding Fee to be onboarded to the network. All onboarded MOBILE Hotspots were onboarded to the IOT network with the correct Onboarding Fee of ($)40 USD, but were onboarded to the MOBILE network with an Onboarding Fee of ($)0 USD. As a result, ($)0 USD in Onboarding Fees have been burned towards the MOBILE subDAO's $A$ Factor, which negatively affects the $A$ Score for the MOBILE subDAO. The current $A$ Score within the DAO Utility Score is as followed: +Current MOBILE Hotspots, such as FreedomFi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. As such, HIP-53 specifies that MOBILE Hotspots should burn a \\$40 USD Onboarding Fee to be onboarded to the network. All onboarded MOBILE Hotspots were onboarded to the IOT network with the correct Onboarding Fee of \\$40 USD, but were onboarded to the MOBILE network with an Onboarding Fee of \\$0 USD. As a result, \\$0 USD in Onboarding Fees have been burned towards the MOBILE subDAO's $A$ Factor, which negatively affects the $A$ Score for the MOBILE subDAO. The current $A$ Score within the DAO Utility Score is as followed: $A = \text{max}(1, \sqrt[4]{\text{DNP Active Device Count} \times \text{DNP Device Activation Fee}})$ From ad0bca6b856ed16ace601154bca1d67c703ee4f2 Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Mon, 19 Jun 2023 03:36:46 -0700 Subject: [PATCH 40/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...nate-mobile-network-onboarding-fees-and-device-definition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index fed881932..6a5759867 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -12,7 +12,7 @@ This HIP proposes implementing a $40 onboard fee paid in Data Credits (DC) for e ## Motivation [HIP-51](https://github.com/helium/HIP/blob/main/0051-helium-dao.md#omni-protocol-poc-incentive-model) specifies the DAO Utility Score, which determines the distribution of HNT between all Helium subDAOs. The Hotspots of each subDAO count towards its Utility Score based on the Onboarding Fee set by that subDAO. -Current MOBILE Hotspots, such as FreedomFi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. As such, HIP-53 specifies that MOBILE Hotspots should burn a \\$40 USD Onboarding Fee to be onboarded to the network. All onboarded MOBILE Hotspots were onboarded to the IOT network with the correct Onboarding Fee of \\$40 USD, but were onboarded to the MOBILE network with an Onboarding Fee of \\$0 USD. As a result, \\$0 USD in Onboarding Fees have been burned towards the MOBILE subDAO's $A$ Factor, which negatively affects the $A$ Score for the MOBILE subDAO. The current $A$ Score within the DAO Utility Score is as followed: +Current MOBILE Hotspots, such as FreedomFi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. As such, HIP-53 specifies that MOBILE Hotspots should burn a \$40 USD Onboarding Fee to be onboarded to the network. All onboarded MOBILE Hotspots were onboarded to the IOT network with the correct Onboarding Fee of \$40 USD, but were onboarded to the MOBILE network with an Onboarding Fee of \$0 USD. As a result, \$0 USD in Onboarding Fees have been burned towards the MOBILE subDAO's $A$ Factor, which negatively affects the $A$ Score for the MOBILE subDAO. The current $A$ Score within the DAO Utility Score is as followed: $A = \text{max}(1, \sqrt[4]{\text{DNP Active Device Count} \times \text{DNP Device Activation Fee}})$ From 4f3d53d50217c1755ad753ea11ee7e6228f4b97e Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Mon, 19 Jun 2023 03:37:21 -0700 Subject: [PATCH 41/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...nate-mobile-network-onboarding-fees-and-device-definition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index 6a5759867..0b244c645 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -12,7 +12,7 @@ This HIP proposes implementing a $40 onboard fee paid in Data Credits (DC) for e ## Motivation [HIP-51](https://github.com/helium/HIP/blob/main/0051-helium-dao.md#omni-protocol-poc-incentive-model) specifies the DAO Utility Score, which determines the distribution of HNT between all Helium subDAOs. The Hotspots of each subDAO count towards its Utility Score based on the Onboarding Fee set by that subDAO. -Current MOBILE Hotspots, such as FreedomFi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. As such, HIP-53 specifies that MOBILE Hotspots should burn a \$40 USD Onboarding Fee to be onboarded to the network. All onboarded MOBILE Hotspots were onboarded to the IOT network with the correct Onboarding Fee of \$40 USD, but were onboarded to the MOBILE network with an Onboarding Fee of \$0 USD. As a result, \$0 USD in Onboarding Fees have been burned towards the MOBILE subDAO's $A$ Factor, which negatively affects the $A$ Score for the MOBILE subDAO. The current $A$ Score within the DAO Utility Score is as followed: +Current MOBILE Hotspots, such as FreedomFi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. As such, HIP-53 specifies that MOBILE Hotspots should burn a $\$40$ USD Onboarding Fee to be onboarded to the network. All onboarded MOBILE Hotspots were onboarded to the IOT network with the correct Onboarding Fee of $\$40$ USD, but were onboarded to the MOBILE network with an Onboarding Fee of $\$0$ USD. As a result, $\$0$ USD in Onboarding Fees have been burned towards the MOBILE subDAO's $A$ Factor, which negatively affects the $A$ Score for the MOBILE subDAO. The current $A$ Score within the DAO Utility Score is as followed: $A = \text{max}(1, \sqrt[4]{\text{DNP Active Device Count} \times \text{DNP Device Activation Fee}})$ From 85729bc3271a8a99ca19a4efe66d88917ab46072 Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Mon, 19 Jun 2023 03:37:53 -0700 Subject: [PATCH 42/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...nate-mobile-network-onboarding-fees-and-device-definition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index 0b244c645..59662cd2a 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -12,7 +12,7 @@ This HIP proposes implementing a $40 onboard fee paid in Data Credits (DC) for e ## Motivation [HIP-51](https://github.com/helium/HIP/blob/main/0051-helium-dao.md#omni-protocol-poc-incentive-model) specifies the DAO Utility Score, which determines the distribution of HNT between all Helium subDAOs. The Hotspots of each subDAO count towards its Utility Score based on the Onboarding Fee set by that subDAO. -Current MOBILE Hotspots, such as FreedomFi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. As such, HIP-53 specifies that MOBILE Hotspots should burn a $\$40$ USD Onboarding Fee to be onboarded to the network. All onboarded MOBILE Hotspots were onboarded to the IOT network with the correct Onboarding Fee of $\$40$ USD, but were onboarded to the MOBILE network with an Onboarding Fee of $\$0$ USD. As a result, $\$0$ USD in Onboarding Fees have been burned towards the MOBILE subDAO's $A$ Factor, which negatively affects the $A$ Score for the MOBILE subDAO. The current $A$ Score within the DAO Utility Score is as followed: +Current MOBILE Hotspots, such as FreedomFi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. As such, HIP-53 specifies that MOBILE Hotspots should burn a \$40$ USD Onboarding Fee to be onboarded to the network. All onboarded MOBILE Hotspots were onboarded to the IOT network with the correct Onboarding Fee of \$40$ USD, but were onboarded to the MOBILE network with an Onboarding Fee of $\0$ USD. As a result, $\$0 USD in Onboarding Fees have been burned towards the MOBILE subDAO's $A$ Factor, which negatively affects the $A$ Score for the MOBILE subDAO. The current $A$ Score within the DAO Utility Score is as followed: $A = \text{max}(1, \sqrt[4]{\text{DNP Active Device Count} \times \text{DNP Device Activation Fee}})$ From 78db815a41d7f892b684871f3e6e6c85782f5dde Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Mon, 19 Jun 2023 03:38:34 -0700 Subject: [PATCH 43/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...te-mobile-network-onboarding-fees-and-device-definition.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index 59662cd2a..e8bed093b 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -12,7 +12,7 @@ This HIP proposes implementing a $40 onboard fee paid in Data Credits (DC) for e ## Motivation [HIP-51](https://github.com/helium/HIP/blob/main/0051-helium-dao.md#omni-protocol-poc-incentive-model) specifies the DAO Utility Score, which determines the distribution of HNT between all Helium subDAOs. The Hotspots of each subDAO count towards its Utility Score based on the Onboarding Fee set by that subDAO. -Current MOBILE Hotspots, such as FreedomFi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. As such, HIP-53 specifies that MOBILE Hotspots should burn a \$40$ USD Onboarding Fee to be onboarded to the network. All onboarded MOBILE Hotspots were onboarded to the IOT network with the correct Onboarding Fee of \$40$ USD, but were onboarded to the MOBILE network with an Onboarding Fee of $\0$ USD. As a result, $\$0 USD in Onboarding Fees have been burned towards the MOBILE subDAO's $A$ Factor, which negatively affects the $A$ Score for the MOBILE subDAO. The current $A$ Score within the DAO Utility Score is as followed: +Current MOBILE Hotspots, such as FreedomFi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. As such, HIP-53 specifies that MOBILE Hotspots should burn a 40 USD Onboarding Fee to be onboarded to the network. All onboarded MOBILE Hotspots were onboarded to the IOT network with the correct Onboarding Fee of 40 USD, but were onboarded to the MOBILE network with an Onboarding Fee of 0 USD. As a result, 0 USD in Onboarding Fees have been burned towards the MOBILE subDAO's $A$ Factor, which negatively affects the $A$ Score for the MOBILE subDAO. The current $A$ Score within the DAO Utility Score is as followed: $A = \text{max}(1, \sqrt[4]{\text{DNP Active Device Count} \times \text{DNP Device Activation Fee}})$ @@ -24,7 +24,7 @@ MOBILE Hotspot manufacturers - MOBILE Hotspot manufacturers will now be required ## Detailed Explanation The current $A$ Score factor within the DAO Utility Score noted in the Motivation section above currently accounts for the active devices on that subDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed $40 MOBILE Onboarding Fee will raise the $A$ Score factor for the MOBILE subDAO. This will increase the daily emissions of HNT into the MOBILE subDAO treasury. -This HIP also requires that for MOBILE Hotspots that were previously onboarded at $0 USD, there is to be $40 USD worth of DCs burned to the MOBILE subDAO. This HIP does not require any specific payer for the DCs; it is the responsibility of the MOBILE subDAO to find the payer(s) and to ensure the payment is settled. +This HIP also requires that for MOBILE Hotspots that were previously onboarded at 0 USD, there is to be 40 USD worth of DCs burned to the MOBILE subDAO. This HIP does not require any specific payer for the DCs; it is the responsibility of the MOBILE subDAO to find the payer(s) and to ensure the payment is settled. ## Drawbacks This proposal may cause Hotspot Manufacturers to increase the costs of MOBILE Network Gateways. This is not expected to be the case. From 5750a0cf16334f626e716d93065a306d7a6bf59f Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Mon, 19 Jun 2023 03:40:03 -0700 Subject: [PATCH 44/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...nate-mobile-network-onboarding-fees-and-device-definition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index e8bed093b..c0e8d624d 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -32,7 +32,7 @@ This proposal may cause Hotspot Manufacturers to increase the costs of MOBILE Ne An additional drawback is that the Onboarding Fees are not based the number of active radios, which may be a better metric of active devices. However, under guidance of the Helium Foundation, using Hotspots as the active device is easier to implement. ## Alternatives -One alternative is to do nothing, and keep Onboarding Fees as zero (0). However, this would impair the daily HNT emissions to the MOBILE subDAO treasury since the $A$ score would remain one (1). +One alternative is to do nothing, and keep Onboarding Fees as zero (0). However, this would impair the daily HNT emissions to the MOBILE subDAO treasury since the $A$ score would remain 1 (one). Another alternative is to change the way the $A$ score is calculated to benefit the HNT emissions of the MOBILE Network; however, this would require a vote with veHNT instead of veMOBILE. From ffa2942e8ca890329444058fd3fe388335853b0a Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Mon, 19 Jun 2023 03:41:06 -0700 Subject: [PATCH 45/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...te-mobile-network-onboarding-fees-and-device-definition.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index c0e8d624d..792ebb4db 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -22,7 +22,7 @@ Future MOBILE Hotspot owners - Future MOBILE Hotspot owners may have to pay a hi MOBILE Hotspot manufacturers - MOBILE Hotspot manufacturers will now be required to pay the onboarding fees for each MOBILE Hotspot, as well as retroactively pay onboarding fees for Hotspots already onboarded. ## Detailed Explanation -The current $A$ Score factor within the DAO Utility Score noted in the Motivation section above currently accounts for the active devices on that subDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed $40 MOBILE Onboarding Fee will raise the $A$ Score factor for the MOBILE subDAO. This will increase the daily emissions of HNT into the MOBILE subDAO treasury. +The current $A$ Score factor within the DAO Utility Score noted in the Motivation section above currently accounts for the active devices on that subDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed 40 USD MOBILE Onboarding Fee will raise the $A$ Score factor for the MOBILE subDAO. This will increase the daily emissions of HNT into the MOBILE subDAO treasury. This HIP also requires that for MOBILE Hotspots that were previously onboarded at 0 USD, there is to be 40 USD worth of DCs burned to the MOBILE subDAO. This HIP does not require any specific payer for the DCs; it is the responsibility of the MOBILE subDAO to find the payer(s) and to ensure the payment is settled. @@ -32,7 +32,7 @@ This proposal may cause Hotspot Manufacturers to increase the costs of MOBILE Ne An additional drawback is that the Onboarding Fees are not based the number of active radios, which may be a better metric of active devices. However, under guidance of the Helium Foundation, using Hotspots as the active device is easier to implement. ## Alternatives -One alternative is to do nothing, and keep Onboarding Fees as zero (0). However, this would impair the daily HNT emissions to the MOBILE subDAO treasury since the $A$ score would remain 1 (one). +One alternative is to do nothing, and keep Onboarding Fees as zero (0). However, this would impair the daily HNT emissions to the MOBILE subDAO treasury since the $A$ score would remain $1$ (one). Another alternative is to change the way the $A$ score is calculated to benefit the HNT emissions of the MOBILE Network; however, this would require a vote with veHNT instead of veMOBILE. From e530297ce32a659480f050c61d855bf2bdb192ae Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Mon, 19 Jun 2023 03:41:37 -0700 Subject: [PATCH 46/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...nate-mobile-network-onboarding-fees-and-device-definition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index 792ebb4db..f2434fb05 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -32,7 +32,7 @@ This proposal may cause Hotspot Manufacturers to increase the costs of MOBILE Ne An additional drawback is that the Onboarding Fees are not based the number of active radios, which may be a better metric of active devices. However, under guidance of the Helium Foundation, using Hotspots as the active device is easier to implement. ## Alternatives -One alternative is to do nothing, and keep Onboarding Fees as zero (0). However, this would impair the daily HNT emissions to the MOBILE subDAO treasury since the $A$ score would remain $1$ (one). +One alternative is to do nothing, and keep Onboarding Fees as $0$ (zero). However, this would impair the daily HNT emissions to the MOBILE subDAO treasury since the $A$ score would remain $1$ (one). Another alternative is to change the way the $A$ score is calculated to benefit the HNT emissions of the MOBILE Network; however, this would require a vote with veHNT instead of veMOBILE. From 5ccca011d4cc477165a373db91f83f8a7a08810e Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Mon, 19 Jun 2023 03:43:12 -0700 Subject: [PATCH 47/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...nate-mobile-network-onboarding-fees-and-device-definition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index f2434fb05..7aee1f5fe 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -24,7 +24,7 @@ MOBILE Hotspot manufacturers - MOBILE Hotspot manufacturers will now be required ## Detailed Explanation The current $A$ Score factor within the DAO Utility Score noted in the Motivation section above currently accounts for the active devices on that subDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed 40 USD MOBILE Onboarding Fee will raise the $A$ Score factor for the MOBILE subDAO. This will increase the daily emissions of HNT into the MOBILE subDAO treasury. -This HIP also requires that for MOBILE Hotspots that were previously onboarded at 0 USD, there is to be 40 USD worth of DCs burned to the MOBILE subDAO. This HIP does not require any specific payer for the DCs; it is the responsibility of the MOBILE subDAO to find the payer(s) and to ensure the payment is settled. +This HIP also requires that for each MOBILE Hotspot that was previously onboarded at 0 USD, there is to be 40 USD worth of DCs burned to the MOBILE subDAO. This HIP does not require any specific payer for the DCs; it is the responsibility of the MOBILE subDAO to find the payer(s) and to ensure the payment is settled. ## Drawbacks This proposal may cause Hotspot Manufacturers to increase the costs of MOBILE Network Gateways. This is not expected to be the case. From c3ed49a93a0b03dab9d1ea0d0eaab6db0dbfb8d9 Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Mon, 19 Jun 2023 04:09:19 -0700 Subject: [PATCH 48/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...nate-mobile-network-onboarding-fees-and-device-definition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index 7aee1f5fe..dbd19f029 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -12,7 +12,7 @@ This HIP proposes implementing a $40 onboard fee paid in Data Credits (DC) for e ## Motivation [HIP-51](https://github.com/helium/HIP/blob/main/0051-helium-dao.md#omni-protocol-poc-incentive-model) specifies the DAO Utility Score, which determines the distribution of HNT between all Helium subDAOs. The Hotspots of each subDAO count towards its Utility Score based on the Onboarding Fee set by that subDAO. -Current MOBILE Hotspots, such as FreedomFi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. As such, HIP-53 specifies that MOBILE Hotspots should burn a 40 USD Onboarding Fee to be onboarded to the network. All onboarded MOBILE Hotspots were onboarded to the IOT network with the correct Onboarding Fee of 40 USD, but were onboarded to the MOBILE network with an Onboarding Fee of 0 USD. As a result, 0 USD in Onboarding Fees have been burned towards the MOBILE subDAO's $A$ Factor, which negatively affects the $A$ Score for the MOBILE subDAO. The current $A$ Score within the DAO Utility Score is as followed: +Current MOBILE Hotspots, such as FreedomFi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. As such, HIP-53 specifies that MOBILE Hotspots should burn a 40 USD Onboarding Fee to be onboarded to the network. All onboarded MOBILE Hotspots were onboarded to the IOT network with the correct Onboarding Fee of 40 USD, but were onboarded to the MOBILE network with an Onboarding Fee of 0 USD. As a result, 0 USD in Onboarding Fees have been burned towards the MOBILE subDAO's $A$ Factor, which negatively affects the $A$ Score for the MOBILE subDAO. The current $A$ Score within the DAO Utility Score is as follows: $A = \text{max}(1, \sqrt[4]{\text{DNP Active Device Count} \times \text{DNP Device Activation Fee}})$ From ebdc153e1adb7f49706ef617f9667bdce4924283 Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Mon, 19 Jun 2023 04:10:13 -0700 Subject: [PATCH 49/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...te-mobile-network-onboarding-fees-and-device-definition.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index dbd19f029..5a0603f04 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -22,9 +22,9 @@ Future MOBILE Hotspot owners - Future MOBILE Hotspot owners may have to pay a hi MOBILE Hotspot manufacturers - MOBILE Hotspot manufacturers will now be required to pay the onboarding fees for each MOBILE Hotspot, as well as retroactively pay onboarding fees for Hotspots already onboarded. ## Detailed Explanation -The current $A$ Score factor within the DAO Utility Score noted in the Motivation section above currently accounts for the active devices on that subDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed 40 USD MOBILE Onboarding Fee will raise the $A$ Score factor for the MOBILE subDAO. This will increase the daily emissions of HNT into the MOBILE subDAO treasury. +The current $A$ Score factor within the DAO Utility Score noted in the Motivation section above currently accounts for the active devices on that subDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed $<\span>40 USD MOBILE Onboarding Fee will raise the $A$ Score factor for the MOBILE subDAO. This will increase the daily emissions of HNT into the MOBILE subDAO treasury. -This HIP also requires that for each MOBILE Hotspot that was previously onboarded at 0 USD, there is to be 40 USD worth of DCs burned to the MOBILE subDAO. This HIP does not require any specific payer for the DCs; it is the responsibility of the MOBILE subDAO to find the payer(s) and to ensure the payment is settled. +This HIP also requires that for each MOBILE Hotspot that was previously onboarded at $<\span>0 USD, there is to be $<\span>40 USD worth of DCs burned to the MOBILE subDAO. This HIP does not require any specific payer for the DCs; it is the responsibility of the MOBILE subDAO to find the payer(s) and to ensure the payment is settled. ## Drawbacks This proposal may cause Hotspot Manufacturers to increase the costs of MOBILE Network Gateways. This is not expected to be the case. From 20b039131a13ecb7a09ec24c4915577546cdcb5b Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Mon, 19 Jun 2023 04:11:13 -0700 Subject: [PATCH 50/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...te-mobile-network-onboarding-fees-and-device-definition.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index 5a0603f04..dbd19f029 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -22,9 +22,9 @@ Future MOBILE Hotspot owners - Future MOBILE Hotspot owners may have to pay a hi MOBILE Hotspot manufacturers - MOBILE Hotspot manufacturers will now be required to pay the onboarding fees for each MOBILE Hotspot, as well as retroactively pay onboarding fees for Hotspots already onboarded. ## Detailed Explanation -The current $A$ Score factor within the DAO Utility Score noted in the Motivation section above currently accounts for the active devices on that subDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed $<\span>40 USD MOBILE Onboarding Fee will raise the $A$ Score factor for the MOBILE subDAO. This will increase the daily emissions of HNT into the MOBILE subDAO treasury. +The current $A$ Score factor within the DAO Utility Score noted in the Motivation section above currently accounts for the active devices on that subDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed 40 USD MOBILE Onboarding Fee will raise the $A$ Score factor for the MOBILE subDAO. This will increase the daily emissions of HNT into the MOBILE subDAO treasury. -This HIP also requires that for each MOBILE Hotspot that was previously onboarded at $<\span>0 USD, there is to be $<\span>40 USD worth of DCs burned to the MOBILE subDAO. This HIP does not require any specific payer for the DCs; it is the responsibility of the MOBILE subDAO to find the payer(s) and to ensure the payment is settled. +This HIP also requires that for each MOBILE Hotspot that was previously onboarded at 0 USD, there is to be 40 USD worth of DCs burned to the MOBILE subDAO. This HIP does not require any specific payer for the DCs; it is the responsibility of the MOBILE subDAO to find the payer(s) and to ensure the payment is settled. ## Drawbacks This proposal may cause Hotspot Manufacturers to increase the costs of MOBILE Network Gateways. This is not expected to be the case. From 5e513e6afa73bf79d17a1c8495198fb180ed440e Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Mon, 19 Jun 2023 12:13:38 -0700 Subject: [PATCH 51/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...ork-onboarding-fees-and-device-definition.md | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index dbd19f029..9408b57d5 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -22,11 +22,11 @@ Future MOBILE Hotspot owners - Future MOBILE Hotspot owners may have to pay a hi MOBILE Hotspot manufacturers - MOBILE Hotspot manufacturers will now be required to pay the onboarding fees for each MOBILE Hotspot, as well as retroactively pay onboarding fees for Hotspots already onboarded. ## Detailed Explanation -The current $A$ Score factor within the DAO Utility Score noted in the Motivation section above currently accounts for the active devices on that subDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed 40 USD MOBILE Onboarding Fee will raise the $A$ Score factor for the MOBILE subDAO. This will increase the daily emissions of HNT into the MOBILE subDAO treasury. - -This HIP also requires that for each MOBILE Hotspot that was previously onboarded at 0 USD, there is to be 40 USD worth of DCs burned to the MOBILE subDAO. This HIP does not require any specific payer for the DCs; it is the responsibility of the MOBILE subDAO to find the payer(s) and to ensure the payment is settled. +HIP-53 specified an Onboarding Fee and MOBILE Hotspots would like to pay the Onboarding Fee. The Onboarding Fee for MOBILE Hotspots is currently set to 0 USD. It is the purview of subDAOs to set the fees that apply to their network. The MOBILE subDAO, via this HIP, is setting the Onboarding Fee to 40 USD. While we are leaving the coding of this work to the Foundation, it is understood to be a rather simple task (estimated at less than an hour of work). The chain variable is to be changed from 0 USD to 40 USD. ## Drawbacks +The current $A$ Score factor within the DAO Utility Score currently accounts for the active devices on that subDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed 40 USD MOBILE Onboarding Fee will raise the $A$ Score factor for the MOBILE subDAO. This will increase the daily emissions of HNT into the MOBILE subDAO treasury until the current limitation of the implementation is corrected. + This proposal may cause Hotspot Manufacturers to increase the costs of MOBILE Network Gateways. This is not expected to be the case. An additional drawback is that the Onboarding Fees are not based the number of active radios, which may be a better metric of active devices. However, under guidance of the Helium Foundation, using Hotspots as the active device is easier to implement. @@ -36,8 +36,17 @@ One alternative is to do nothing, and keep Onboarding Fees as $0$ (zero). Howeve Another alternative is to change the way the $A$ score is calculated to benefit the HNT emissions of the MOBILE Network; however, this would require a vote with veHNT instead of veMOBILE. +A complementary HIP to require that for each MOBILE Hotspot that was previously onboarded at 0 USD, there is to be 40 USD worth of DCs burned to the MOBILE subDAO. SUch a HIP should not require any specific payer for the DCs; it would be the responsibility of the MOBILE subDAO to find the payer(s) and to ensure the payment is settled. Given there is no mechanism currently for this be done, such a feature can not be included in this HIP. + ## Deployment Impact After the passing of this HIP, the Helium Foundation will need to modify the chain variable that defines the onboarding fee for the MOBILE subDAO. ## Success Metrics -The primary success metric will be greater daily HNT emissions to the MOBILE subDAO treasury. +The success metric will be that any MOBILE Hotspot that is added to the MOBILE network will have paid its Onboarding Fee. + + +was: + +## Detailed Explanation +The current $A$ Score factor within the DAO Utility Score noted in the Motivation section above currently accounts for the active devices on that subDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed 40 USD MOBILE Onboarding Fee will raise the $A$ Score factor for the MOBILE subDAO. This will increase the daily emissions of HNT into the MOBILE subDAO treasury. + From 252100a7908950626e7aee78355434b6f099ee5e Mon Sep 17 00:00:00 2001 From: KeithRettig <134342852+KeithRettig@users.noreply.github.com> Date: Mon, 19 Jun 2023 12:18:05 -0700 Subject: [PATCH 52/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md --- ...nate-mobile-network-onboarding-fees-and-device-definition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index 9408b57d5..f7ef40845 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -36,7 +36,7 @@ One alternative is to do nothing, and keep Onboarding Fees as $0$ (zero). Howeve Another alternative is to change the way the $A$ score is calculated to benefit the HNT emissions of the MOBILE Network; however, this would require a vote with veHNT instead of veMOBILE. -A complementary HIP to require that for each MOBILE Hotspot that was previously onboarded at 0 USD, there is to be 40 USD worth of DCs burned to the MOBILE subDAO. SUch a HIP should not require any specific payer for the DCs; it would be the responsibility of the MOBILE subDAO to find the payer(s) and to ensure the payment is settled. Given there is no mechanism currently for this be done, such a feature can not be included in this HIP. +A complementary HIP to require that for each MOBILE Hotspot that was previously onboarded at 0 USD, there is to be 40 USD worth of DCs burned to the MOBILE subDAO. Such a HIP should not require any specific payer for the DCs; it would be the responsibility of the MOBILE subDAO to find the payer(s) and to ensure the payment is settled. Given there is no mechanism currently for this be done, such a feature can not be included in this HIP. ## Deployment Impact After the passing of this HIP, the Helium Foundation will need to modify the chain variable that defines the onboarding fee for the MOBILE subDAO. From 53f563b1a82c01b322e959341e4d0e9e99336cb7 Mon Sep 17 00:00:00 2001 From: Andy Zyvoloski <104723888+heatedlime@users.noreply.github.com> Date: Mon, 19 Jun 2023 14:28:43 -0500 Subject: [PATCH 53/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md changes to motivation section and detailed explanation --- ...etwork-onboarding-fees-and-device-definition.md | 14 +++----------- 1 file changed, 3 insertions(+), 11 deletions(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index f7ef40845..282141dc1 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -10,9 +10,7 @@ This HIP proposes implementing a $40 onboard fee paid in Data Credits (DC) for each Hotspot onboarded to the MOBILE Network. ## Motivation -[HIP-51](https://github.com/helium/HIP/blob/main/0051-helium-dao.md#omni-protocol-poc-incentive-model) specifies the DAO Utility Score, which determines the distribution of HNT between all Helium subDAOs. The Hotspots of each subDAO count towards its Utility Score based on the Onboarding Fee set by that subDAO. - -Current MOBILE Hotspots, such as FreedomFi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. As such, HIP-53 specifies that MOBILE Hotspots should burn a 40 USD Onboarding Fee to be onboarded to the network. All onboarded MOBILE Hotspots were onboarded to the IOT network with the correct Onboarding Fee of 40 USD, but were onboarded to the MOBILE network with an Onboarding Fee of 0 USD. As a result, 0 USD in Onboarding Fees have been burned towards the MOBILE subDAO's $A$ Factor, which negatively affects the $A$ Score for the MOBILE subDAO. The current $A$ Score within the DAO Utility Score is as follows: +Current MOBILE Hotspots, such as FreedomFi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. As such, HIP-53 specifies that MOBILE Hotspots should burn a 40 USD Onboarding Fee to be onboarded to the network. All onboarded MOBILE Hotspots were onboarded to the IOT network with the correct Onboarding Fee of 40 USD, but were onboarded to the MOBILE network with an Onboarding Fee of 0 USD. As a result, 0 USD in Onboarding Fees have been burned towards the MOBILE subDAO's $A$ Factor, which negatively affects the $A$ Score established in HIP 51 for the MOBILE subDAO. The current $A$ Score within the DAO Utility Score is as follows: $A = \text{max}(1, \sqrt[4]{\text{DNP Active Device Count} \times \text{DNP Device Activation Fee}})$ @@ -22,7 +20,7 @@ Future MOBILE Hotspot owners - Future MOBILE Hotspot owners may have to pay a hi MOBILE Hotspot manufacturers - MOBILE Hotspot manufacturers will now be required to pay the onboarding fees for each MOBILE Hotspot, as well as retroactively pay onboarding fees for Hotspots already onboarded. ## Detailed Explanation -HIP-53 specified an Onboarding Fee and MOBILE Hotspots would like to pay the Onboarding Fee. The Onboarding Fee for MOBILE Hotspots is currently set to 0 USD. It is the purview of subDAOs to set the fees that apply to their network. The MOBILE subDAO, via this HIP, is setting the Onboarding Fee to 40 USD. While we are leaving the coding of this work to the Foundation, it is understood to be a rather simple task (estimated at less than an hour of work). The chain variable is to be changed from 0 USD to 40 USD. +As the framework for the MOBILE subDAO was established after the passing of HIP 53, a way to pay onboarding fees for MOBILE Hotspots was never created, and therefore, the Onboarding Fee for MOBILE Hotspots is currently set to 0 USD. It is the purview of subDAOs to set the fees that apply to their network. The MOBILE subDAO, via this HIP, is setting the Onboarding Fee to 40 USD. While we are leaving the coding of this work to the Foundation, it is understood to be a rather simple task (estimated at less than an hour of work). The chain variable is to be changed from 0 USD to 40 USD. ## Drawbacks The current $A$ Score factor within the DAO Utility Score currently accounts for the active devices on that subDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed 40 USD MOBILE Onboarding Fee will raise the $A$ Score factor for the MOBILE subDAO. This will increase the daily emissions of HNT into the MOBILE subDAO treasury until the current limitation of the implementation is corrected. @@ -36,7 +34,7 @@ One alternative is to do nothing, and keep Onboarding Fees as $0$ (zero). Howeve Another alternative is to change the way the $A$ score is calculated to benefit the HNT emissions of the MOBILE Network; however, this would require a vote with veHNT instead of veMOBILE. -A complementary HIP to require that for each MOBILE Hotspot that was previously onboarded at 0 USD, there is to be 40 USD worth of DCs burned to the MOBILE subDAO. Such a HIP should not require any specific payer for the DCs; it would be the responsibility of the MOBILE subDAO to find the payer(s) and to ensure the payment is settled. Given there is no mechanism currently for this be done, such a feature can not be included in this HIP. +A complementary HIP is to require that for each MOBILE Hotspot that was previously onboarded at 0 USD, there is to be 40 USD worth of DCs burned to the MOBILE subDAO. Such a HIP should not require any specific payer for the DCs; it would be the responsibility of the MOBILE subDAO to find the payer(s) and to ensure the payment is settled. Given there is no mechanism currently for this be done, such a feature can not be included in this HIP. ## Deployment Impact After the passing of this HIP, the Helium Foundation will need to modify the chain variable that defines the onboarding fee for the MOBILE subDAO. @@ -44,9 +42,3 @@ After the passing of this HIP, the Helium Foundation will need to modify the cha ## Success Metrics The success metric will be that any MOBILE Hotspot that is added to the MOBILE network will have paid its Onboarding Fee. - -was: - -## Detailed Explanation -The current $A$ Score factor within the DAO Utility Score noted in the Motivation section above currently accounts for the active devices on that subDAO multiplied by the current onboard fee set for each device. Therefore, the passing of this HIP and the establishment of a prescribed 40 USD MOBILE Onboarding Fee will raise the $A$ Score factor for the MOBILE subDAO. This will increase the daily emissions of HNT into the MOBILE subDAO treasury. - From 4f679017e7801c68442960379d559dcfa7c3c279 Mon Sep 17 00:00:00 2001 From: Andy Zyvoloski <104723888+heatedlime@users.noreply.github.com> Date: Mon, 19 Jun 2023 16:42:35 -0500 Subject: [PATCH 54/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md Co-authored-by: Abhay Kumar <75+abhay@users.noreply.github.com> --- ...nate-mobile-network-onboarding-fees-and-device-definition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index 282141dc1..bf3ebf243 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -10,7 +10,7 @@ This HIP proposes implementing a $40 onboard fee paid in Data Credits (DC) for each Hotspot onboarded to the MOBILE Network. ## Motivation -Current MOBILE Hotspots, such as FreedomFi and Bobcat 500, contain both an IOT Hotspot and a MOBILE Hotspot. As such, HIP-53 specifies that MOBILE Hotspots should burn a 40 USD Onboarding Fee to be onboarded to the network. All onboarded MOBILE Hotspots were onboarded to the IOT network with the correct Onboarding Fee of 40 USD, but were onboarded to the MOBILE network with an Onboarding Fee of 0 USD. As a result, 0 USD in Onboarding Fees have been burned towards the MOBILE subDAO's $A$ Factor, which negatively affects the $A$ Score established in HIP 51 for the MOBILE subDAO. The current $A$ Score within the DAO Utility Score is as follows: +Current MOBILE Hotspots, such as FreedomFi and Bobcat 500, contain both IOT and a MOBILE network capabilities. As such, HIP-53 specifies that MOBILE Hotspots should burn a 40 USD Onboarding Fee to be onboarded to the network. All onboarded MOBILE Hotspots were onboarded to the IOT network with the correct Onboarding Fee of 40 USD, but were onboarded to the MOBILE network with an Onboarding Fee of 0 USD. As a result, 0 USD in Onboarding Fees have been burned towards the MOBILE subDAO's $A$ Factor, which negatively affects the $A$ Score established in HIP 51 for the MOBILE subDAO. The current $A$ Score within the DAO Utility Score is as follows: $A = \text{max}(1, \sqrt[4]{\text{DNP Active Device Count} \times \text{DNP Device Activation Fee}})$ From 2526880ccbf4d13f7bde0d94014d5ee78638c8eb Mon Sep 17 00:00:00 2001 From: Andy Zyvoloski <104723888+heatedlime@users.noreply.github.com> Date: Mon, 19 Jun 2023 16:42:52 -0500 Subject: [PATCH 55/56] Update 0000-designate-mobile-network-onboarding-fees-and-device-definition.md Co-authored-by: Abhay Kumar <75+abhay@users.noreply.github.com> --- ...nate-mobile-network-onboarding-fees-and-device-definition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md index bf3ebf243..89dfe175a 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0000-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -37,7 +37,7 @@ Another alternative is to change the way the $A$ score is calculated to benefit A complementary HIP is to require that for each MOBILE Hotspot that was previously onboarded at 0 USD, there is to be 40 USD worth of DCs burned to the MOBILE subDAO. Such a HIP should not require any specific payer for the DCs; it would be the responsibility of the MOBILE subDAO to find the payer(s) and to ensure the payment is settled. Given there is no mechanism currently for this be done, such a feature can not be included in this HIP. ## Deployment Impact -After the passing of this HIP, the Helium Foundation will need to modify the chain variable that defines the onboarding fee for the MOBILE subDAO. +After the passing of this HIP, the Helium multisig will need to modify the variable that defines the onboarding fee for the MOBILE subDAO. ## Success Metrics The success metric will be that any MOBILE Hotspot that is added to the MOBILE network will have paid its Onboarding Fee. From f49f2fdcb2737251b938deae2ecdb27a2b22cf28 Mon Sep 17 00:00:00 2001 From: HIP Editors <93347218+hiptron@users.noreply.github.com> Date: Mon, 19 Jun 2023 18:06:09 -0400 Subject: [PATCH 56/56] Assign HIP number and prepare for merge --- ...-mobile-network-onboarding-fees-and-device-definition.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) rename 0000-designate-mobile-network-onboarding-fees-and-device-definition.md => 0089-designate-mobile-network-onboarding-fees-and-device-definition.md (95%) diff --git a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md b/0089-designate-mobile-network-onboarding-fees-and-device-definition.md similarity index 95% rename from 0000-designate-mobile-network-onboarding-fees-and-device-definition.md rename to 0089-designate-mobile-network-onboarding-fees-and-device-definition.md index 89dfe175a..260921758 100644 --- a/0000-designate-mobile-network-onboarding-fees-and-device-definition.md +++ b/0089-designate-mobile-network-onboarding-fees-and-device-definition.md @@ -1,9 +1,9 @@ -# HIP XX: MOBILE Network Onboarding Fees +# HIP 89: MOBILE Network Onboarding Fees - Authors: [Andy Zyvoloski](https://github.com/heatedlime), [Keith Rettig](https://github.com/keithrettig) - Start Date: 6/14/2023 - Category: Technical & Economic -- Original HIP PR: # -- Tracking Issue: # +- Original HIP PR: [#701](https://github.com/helium/HIP/pull/701) +- Tracking Issue: [#714](https://github.com/helium/HIP/issues/714) - Voting Requirements: veMOBILE ## Summary