From 70383a38be17e80793f97faf37919f4afd300c9d Mon Sep 17 00:00:00 2001 From: Joey Hiller <1965053+jthiller@users.noreply.github.com> Date: Thu, 25 Apr 2024 11:04:21 +0200 Subject: [PATCH 1/8] Rework and clarification. (wip) --- ...-oui-additional-address-space-reshuffle.md | 132 ++++++++---------- 1 file changed, 58 insertions(+), 74 deletions(-) diff --git a/0116-oui-additional-address-space-reshuffle.md b/0116-oui-additional-address-space-reshuffle.md index f75f04327..5526d0c4f 100644 --- a/0116-oui-additional-address-space-reshuffle.md +++ b/0116-oui-additional-address-space-reshuffle.md @@ -1,6 +1,6 @@ # HIP 116: OUI Additional Address Space Reshuffle -- Author(s): [@ccall48](https://github.com/ccall48), [@nowiresfil](https://github.com/nowiresfil) +- Author(s): [@ccall48](https://github.com/ccall48), [@nowiresfil](https://github.com/nowiresfil), [@jthiller](https://github.com/jthiller) - Start Date: 2024-03-25 - Category: Technical - Original HIP PR: [#948](https://github.com/helium/HIP/pull/948) @@ -10,105 +10,84 @@ --- ## Summary -With the initial purchase of an OUI it is mandatory for a LNS operator to either supply a Lora Alliance NetID or purchase -a minimum device address block from the Helium Foundation for $100 per address, with a minimum purchase of 8 for ($800 USD). -[Helium OUI Documentation](https://docs.helium.com/iot/run-an-lns/buy-an-oui) +Network operators leveraging Helium must provision an Organizationally Unique Identifier (OUI) to bring devices onto the network. Along with the OUI, operators without their own NetID must also purchase a block of device addresses (DevAddr) to assign to devices. The cost of purchasing a block of 8 DevAddr is currently $800 USD. This proposal seeks to reduce the cost of purchasing a block of 8 DevAddr to $100 USD. -This proposal is to decrease the purchase cost from $800 to $100 for the same `/29` 8 Address block.
-While also seeking to move the cost of OUI and Addresses space to be burnt from IOT subdao tokens. +The [Helium OUI Documentation](https://docs.helium.com/iot/run-an-lns/buy-an-oui) fully details the current costs and processes. + +In addition to the DevAddr cost reduction, this proposal seeks to ultimately have OUI and DevAddr issuance paid in the subnetwork-native IOT token as an on-chain transaction. This would replace the existing process of purchasing DevAddr with DC from burned HNT. ## Motivation -The initial 8 block address spacing with the original helium console had the ability to multiplex this space out to -around ~ 300K devices which is not possible multiplexing the same block size through the new OpenLNS -initiative on Helium network over ChirpStack. -On simulation runs on a few different hardware types reliably puts this number at a maximum active device count of -around 2k devices well short of the previous ability which made the costing reasonable. +The current cost of purchasing a block of 8 DevAddr is $800 USD. This cost is viewed as a barrier to entry for network operators, especially those looking to self-host their LNS. By reducing the cost of purchasing a block of 8 DevAddr to $100 USD, the Helium Network becomes more accessible to a wider range of network operators. -This should help encourage adopters to use the Helium 00003C NetID rather than bringing an external address space bought -elsewhere. In return drive up devices on the network by lowering the cost of entry for both hosts and deployers. +Moving payment for OUIs and DevAddrs to the IOT token ensures that the revenue of these purchases is fully captured by the IOT subnetwork. ## Stakeholders + This HIP will affect existing and future OpenLNS operators or any individual operating an OUI on the Helium IOT network by lowering the cost of entry for deployment on the IOT network. -- Future operators by a reduced cost of entry. -- Existing operators by reduced cost of additional address block purchases. -Helium Foundation for required develpement work to setup the appropriate mechanism to burn IOT instead of DC. +- Future operators will see a reduced cost of entry. +- Existing operators will see a reduced cost for additional DevAddr block purchases. -Feedback welcome by the official discord channel or by watching the HIP repository on GitHub. +Moving puchases of OUIs and DevAddrs to the IOT token will affect HNT, IOT, and indirectly MOBILE token holders. The amount of HNT burned for these purchases will decrease and the amount of IOT burned will increase. ## Detailed Explanation -This is a breakdown of the prefix size of addresses for the respective prefix size for comparison. -``` -Prefix / number of device address allocations -32 / 1 -31 / 2 -30 / 4 -29 / 8 ________________ <= Current allocation size to reduce from $800 to $100. -28 / 16 -27 / 32 -26 / 64 -25 / 128 -24 / 256 -23 / 512 -22 / 1,024 -21 / 2,048 -20 / 4,046 -19 / 8,192 -18 / 16,384 -17 / 32,768 -16 / 65,536 -15 / 131,072 -14 / 262,144 -13 / 524,288 -12 / 1,048,576 -11 / 2,097,152 -10 / 4,194,304 -9 / 8,388,608 -8 / 16,777,216 -7 / 33,554,432 ________ <= Helium 00003C Allocation size from Lora Alliance. -``` +On behalf of the Helium Network, the Helium Foundation retains a 'Type 0' NetID from the LoRa Alliance, the administrator of LoRaWAN address space. The Type 0 NetID offers the largest allocation of address space (DevAddrs) for the purpose of bringing end-user LoRaWAN devices on to the network. + +The Helium Foundation retains several NetIDs. However, for the purposes of this proposal, only the Type 0 NetID is considered. + +NetIDs are allocated based on membership tier with the LoRa Alliance. Types range from 0 to 7. Type 1, 2, 4, and 5 NetIDs are unused and reserved for future use. This chart shows the number of DevAddr that can be allocated for each NetID type: + +| NetID Type | Number of DevAddr | Comparison | +| ---------- | ----------------- | -------------------------------------------------------------- | +| – | 8 | Size of a single Helium allocation as part of the Type 0 NetID | +| Type 7 | 128 | | +| Type 6 | 1,024 | | +| Type 3 | 131,072 | | +| Type 0 | 33,554,432 | | + +A single DevAddr can handle multiple devices through multiplexing on the LNS. The number of devices that can be multiplexed on a single DevAddr is dependent on the device throughput and the network server implementation. Additional DevAddrs become important as network servers scale to handle more devices. + +### Implementation Timeline + +Upon approval of this HIP, the Helium Foundation will immediately change the cost of purchasing a block of 8 DevAddr to $100 USD. + +The Helium Foundation will also begin the process of moving OUI and DevAddr issuance to the IOT token. As OUI and DevAddr purchases are currently transacted off-chain, the purchases will be implemented to use the IOT token with the completion on-chain transaction method. ## Drawbacks -This would reduce the current possible maximum revenue for address space on the Helium Network. -However, at the time of this HIP after ~3 years of operation and 1 year of the foundation offering the new 00003C -NetID allocation the uptake has already been quite slow, so there is also an argument that the existing pricing -has missed the mark and thus actually is being underutilized. +Decreasing the DevAddr cost would reduce the current possible maximum revenue for address space on the Helium Network. -Existing stakeholders in this area may feel like they were overcharged if the price reduces for more -address space, or if the system moves to a much lower cost per year or per year rental system. -We could offer increased address space per year to the new amount of existing costs already rendered. -Or offer fee free years in lieu of the new proposal. +Existing stakeholders may feel like they were overcharged if the price is reduced for more +address space. ## Rationale and Alternatives -At time of writing the breakdown of device addresses is: +At time of writing, the breakdown of OUIs using Helium Foundation or external NetIDs is: + ``` -Old Helium 000024 : 56 -New Helium 00003C : 29 -Purchased Externaly: 21 -Total OUI's : 106 +Old Helium 000024 : 56 +New Helium 00003C : 29 +Using External NetID : 21 +Total OUI's : 106 ``` -All larger allocations are being purchased externally and assigned to an OUI which is reducing the network burn, -only a few existing 000024 & 00003C users have purchased more than 1 x 8 address block. + +Only a few existing 000024 & 00003C NetID users have purchased more than 1 x 8 DevAddr block. The following are a selection of larger Helium OUIs and their DevAddr allocations. For context on these OUIs and their protocol usage on the network, see the [Dune Data Credit Dashboard](https://dune.com/helium-foundation/helium-data-credits). + +- OUI 1 (Foundation Console) 1024 DevAddr (scaled to this at peak dc gaming) +- OUI 6 (Helium IoT EU) 152 DevAddr (added in 5 blocks) +- OUI 12 (1663 Console) 32 DevAddr +- OUI 1119 (TrackPac) 128 DevAddr (via their own netID) ### Existing Costs And Alternate Costing Ideas -``` -# Current Cost /29: -- Possible total allocations: 4,194,304 -- Network One Time Revenue: $3,355,443,200 -# After Proposal /29 -- Possible total allocations: 4,194,304 -- Network One Time Revenue: $419,430,400 -``` -Move the costs to be paid by burning IOT tokens to help IOT subdao score. +In blocks of 8, there are 4,194,304 total allocations available on the Type 0 NetID. At $800 per block, the total revenue from the sale of all address space is $3,355,443,200. At $100 per block, the total revenue from the sale of all address space would be $419,430,400. ### Acceptable alternatives could include: + ``` 1. Lower the costing of the offering to purchase a 8 block from $800 to $80. 2. Allow the sale of singular address space at around $10 per address. @@ -117,21 +96,26 @@ Move the costs to be paid by burning IOT tokens to help IOT subdao score. ``` ## Unresolved Questions + Would it be more reasonable to move to a lower cost but more address space allocation for a one time fee? Or possibly move to a much lower cost but yearly rent on the existing address space thus helping to be more accessible and help drive up IOT usage. ## Deployment Impact -By making the Helium Network more accessible and lowering the cost to encourage IOT usage being the main + +By making the Helium Network more accessible and lowering the cost to encourage IoT network usage being the main factor. We expect the deployment impact to be positive with the lowering of the cost of offering hosting to existing stakeholders I would expect this to be filtered all the way down to cost of paid hosting services, as well as lower the barrier for small scale deployments to enter and use the network being more attractive. ## Success Metrics -An uptick in OUI deployers and devices traversing the network. With acceptance being more DC burn and IOT rewards -for hotspot hosts. + +The goal of this proposal is to make operating an LNS more accessible by reducing the cost. The downstream effects of more operational LNSs ideally presents as an uptick in IoT devices transmitting data across the network. ## Documentation Updates + A list of known pages in the documentation that will need updating should this HIP be successful. + - Helium OUI Documentation / https://docs.helium.com/iot/run-an-lns/buy-an-oui +- Helium Data Credit Documentation / https://docs.helium.com/tokens/data-credit From 945940f15e5d189c47b1e9b8a4985ed4c160e0e4 Mon Sep 17 00:00:00 2001 From: Joey Hiller <1965053+jthiller@users.noreply.github.com> Date: Thu, 25 Apr 2024 11:28:54 +0200 Subject: [PATCH 2/8] Change category --- 0116-oui-additional-address-space-reshuffle.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0116-oui-additional-address-space-reshuffle.md b/0116-oui-additional-address-space-reshuffle.md index 5526d0c4f..20bbf6596 100644 --- a/0116-oui-additional-address-space-reshuffle.md +++ b/0116-oui-additional-address-space-reshuffle.md @@ -2,7 +2,7 @@ - Author(s): [@ccall48](https://github.com/ccall48), [@nowiresfil](https://github.com/nowiresfil), [@jthiller](https://github.com/jthiller) - Start Date: 2024-03-25 -- Category: Technical +- Category: Economic - Original HIP PR: [#948](https://github.com/helium/HIP/pull/948) - Tracking Issue: [#959](https://github.com/helium/HIP/issues/959) - Vote Requirements: veIOT Holders From 540bbc7fee3bb80393954ec1e69221c49ad2e973 Mon Sep 17 00:00:00 2001 From: Joey Hiller <1965053+jthiller@users.noreply.github.com> Date: Thu, 25 Apr 2024 13:39:17 +0200 Subject: [PATCH 3/8] Minor cleanup --- ...-oui-additional-address-space-reshuffle.md | 28 +++++++++---------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/0116-oui-additional-address-space-reshuffle.md b/0116-oui-additional-address-space-reshuffle.md index 20bbf6596..ea9cf38e7 100644 --- a/0116-oui-additional-address-space-reshuffle.md +++ b/0116-oui-additional-address-space-reshuffle.md @@ -11,7 +11,7 @@ ## Summary -Network operators leveraging Helium must provision an Organizationally Unique Identifier (OUI) to bring devices onto the network. Along with the OUI, operators without their own NetID must also purchase a block of device addresses (DevAddr) to assign to devices. The cost of purchasing a block of 8 DevAddr is currently $800 USD. This proposal seeks to reduce the cost of purchasing a block of 8 DevAddr to $100 USD. +Network operators leveraging Helium LoRaWAN must provision an Organizationally Unique Identifier (OUI) to bring devices onto the network. Along with the OUI, operators without their own NetID must also purchase a block of device addresses (DevAddr) to assign to devices. The cost of purchasing a block of 8 DevAddr is currently $800 USD. This proposal seeks to reduce the cost of purchasing a block of 8 DevAddr to $100 USD. The [Helium OUI Documentation](https://docs.helium.com/iot/run-an-lns/buy-an-oui) fully details the current costs and processes. @@ -21,7 +21,7 @@ In addition to the DevAddr cost reduction, this proposal seeks to ultimately hav The current cost of purchasing a block of 8 DevAddr is $800 USD. This cost is viewed as a barrier to entry for network operators, especially those looking to self-host their LNS. By reducing the cost of purchasing a block of 8 DevAddr to $100 USD, the Helium Network becomes more accessible to a wider range of network operators. -Moving payment for OUIs and DevAddrs to the IOT token ensures that the revenue of these purchases is fully captured by the IOT subnetwork. +Transitioning payment for OUIs and DevAddrs to the IOT token ensures that the revenue of these purchases is fully captured by the IOT subnetwork. ## Stakeholders @@ -31,7 +31,7 @@ by lowering the cost of entry for deployment on the IOT network. - Future operators will see a reduced cost of entry. - Existing operators will see a reduced cost for additional DevAddr block purchases. -Moving puchases of OUIs and DevAddrs to the IOT token will affect HNT, IOT, and indirectly MOBILE token holders. The amount of HNT burned for these purchases will decrease and the amount of IOT burned will increase. +Moving puchases of OUIs and DevAddrs to the IOT token will affect HNT, IOT, and indirectly MOBILE token holders. The amount of HNT burned for these purchases will decrease, and the amount of IOT burned will increase. ## Detailed Explanation @@ -51,6 +51,12 @@ NetIDs are allocated based on membership tier with the LoRa Alliance. Types rang A single DevAddr can handle multiple devices through multiplexing on the LNS. The number of devices that can be multiplexed on a single DevAddr is dependent on the device throughput and the network server implementation. Additional DevAddrs become important as network servers scale to handle more devices. +### Purchasing Process + +Since the Solana migration, the process for purchasing OUIs and DevAddrs has been handled off-chain and faciliated by the Helium Foundation. Work is ongoing to move this process on-chain for parity with the legacy process from the Helium L1. + +As such, a change from $800 per DevAddr block to $100 per DevAddr block would be simple according to the Helium Foundation. In the iterest of working toward an on-chain transaction mechanism, this HIP proposes to only implement IOT-based payments alongside the on-chain implementation. + ### Implementation Timeline Upon approval of this HIP, the Helium Foundation will immediately change the cost of purchasing a block of 8 DevAddr to $100 USD. @@ -72,28 +78,22 @@ At time of writing, the breakdown of OUIs using Helium Foundation or external Ne Old Helium 000024 : 56 New Helium 00003C : 29 Using External NetID : 21 -Total OUI's : 106 +Total OUIs : 106 ``` -Only a few existing 000024 & 00003C NetID users have purchased more than 1 x 8 DevAddr block. The following are a selection of larger Helium OUIs and their DevAddr allocations. For context on these OUIs and their protocol usage on the network, see the [Dune Data Credit Dashboard](https://dune.com/helium-foundation/helium-data-credits). +Only a few existing 000024 & 00003C NetID users have purchased more than 1 x 8 DevAddr block. The following is a selection of larger Helium OUIs and their DevAddr allocations. For context on these OUIs and their protocol usage on the network, see the [Data Credit Dashboard on Dune](https://dune.com/helium-foundation/helium-data-credits). - OUI 1 (Foundation Console) 1024 DevAddr (scaled to this at peak dc gaming) - OUI 6 (Helium IoT EU) 152 DevAddr (added in 5 blocks) - OUI 12 (1663 Console) 32 DevAddr - OUI 1119 (TrackPac) 128 DevAddr (via their own netID) -### Existing Costs And Alternate Costing Ideas - In blocks of 8, there are 4,194,304 total allocations available on the Type 0 NetID. At $800 per block, the total revenue from the sale of all address space is $3,355,443,200. At $100 per block, the total revenue from the sale of all address space would be $419,430,400. -### Acceptable alternatives could include: +### Acceptable Alternatives Could Include -``` -1. Lower the costing of the offering to purchase a 8 block from $800 to $80. -2. Allow the sale of singular address space at around $10 per address. -3. Possibly rent device space per year at a much reduced cost of around $5 per address space, - knowing the space is getting used and paid for yearly. -``` +1. Lower the cost to purchase a 8 DevAddr block from $800 to $80, or another value. +1. Rent device space per year at a reduced cost of around $5 per address. ## Unresolved Questions From 1256cc30a64fdadf1c1d1fabab97adb49cb07a0d Mon Sep 17 00:00:00 2001 From: Joey Hiller <1965053+jthiller@users.noreply.github.com> Date: Wed, 1 May 2024 19:46:50 -0700 Subject: [PATCH 4/8] Update OUI counts, credit IoTWG, note LoRa Alliance member fees --- 0116-oui-additional-address-space-reshuffle.md | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/0116-oui-additional-address-space-reshuffle.md b/0116-oui-additional-address-space-reshuffle.md index ea9cf38e7..a65f67512 100644 --- a/0116-oui-additional-address-space-reshuffle.md +++ b/0116-oui-additional-address-space-reshuffle.md @@ -1,6 +1,6 @@ # HIP 116: OUI Additional Address Space Reshuffle -- Author(s): [@ccall48](https://github.com/ccall48), [@nowiresfil](https://github.com/nowiresfil), [@jthiller](https://github.com/jthiller) +- Author(s): [@ccall48](https://github.com/ccall48), [@nowiresfil](https://github.com/nowiresfil), Members of the IoT Working Group - Start Date: 2024-03-25 - Category: Economic - Original HIP PR: [#948](https://github.com/helium/HIP/pull/948) @@ -75,21 +75,23 @@ address space. At time of writing, the breakdown of OUIs using Helium Foundation or external NetIDs is: ``` -Old Helium 000024 : 56 -New Helium 00003C : 29 -Using External NetID : 21 -Total OUIs : 106 +Old Helium 000024 : 55 +New Helium 00003C : 34 +Using External NetID : 22 +Total OUIs : 111 ``` Only a few existing 000024 & 00003C NetID users have purchased more than 1 x 8 DevAddr block. The following is a selection of larger Helium OUIs and their DevAddr allocations. For context on these OUIs and their protocol usage on the network, see the [Data Credit Dashboard on Dune](https://dune.com/helium-foundation/helium-data-credits). -- OUI 1 (Foundation Console) 1024 DevAddr (scaled to this at peak dc gaming) +- OUI 1 (Foundation Console) 1024 DevAddr (scaled to this at peak DC gaming) - OUI 6 (Helium IoT EU) 152 DevAddr (added in 5 blocks) - OUI 12 (1663 Console) 32 DevAddr -- OUI 1119 (TrackPac) 128 DevAddr (via their own netID) +- OUI 1119 (TrackPac) 128 DevAddr (via their own NetID) In blocks of 8, there are 4,194,304 total allocations available on the Type 0 NetID. At $800 per block, the total revenue from the sale of all address space is $3,355,443,200. At $100 per block, the total revenue from the sale of all address space would be $419,430,400. +As noted in Detailed Explanation, DevAddr can be acquired as part of a NetID and LoRa Alliance membership. The tradeoff, from a financial standpoint, is that LoRa Alliance membership comes at a yearly cost. Currently, access to a Type 0 NetID requires a $50,000 USD membership fee. Access to Type 7 NetIDs are available at a $500/yr licensing fee. + ### Acceptable Alternatives Could Include 1. Lower the cost to purchase a 8 DevAddr block from $800 to $80, or another value. From d45d439edee35b724fd89f2af4fcd4be2b49b86d Mon Sep 17 00:00:00 2001 From: Joey Hiller <1965053+jthiller@users.noreply.github.com> Date: Wed, 1 May 2024 20:20:43 -0700 Subject: [PATCH 5/8] Remove hard wraps --- 0116-oui-additional-address-space-reshuffle.md | 16 ++++------------ 1 file changed, 4 insertions(+), 12 deletions(-) diff --git a/0116-oui-additional-address-space-reshuffle.md b/0116-oui-additional-address-space-reshuffle.md index a65f67512..e671e268c 100644 --- a/0116-oui-additional-address-space-reshuffle.md +++ b/0116-oui-additional-address-space-reshuffle.md @@ -25,8 +25,7 @@ Transitioning payment for OUIs and DevAddrs to the IOT token ensures that the re ## Stakeholders -This HIP will affect existing and future OpenLNS operators or any individual operating an OUI on the Helium IOT network -by lowering the cost of entry for deployment on the IOT network. +This HIP will affect existing and future OpenLNS operators or any individual operating an OUI on the Helium IOT network by lowering the cost of entry for deployment on the IOT network. - Future operators will see a reduced cost of entry. - Existing operators will see a reduced cost for additional DevAddr block purchases. @@ -67,8 +66,7 @@ The Helium Foundation will also begin the process of moving OUI and DevAddr issu Decreasing the DevAddr cost would reduce the current possible maximum revenue for address space on the Helium Network. -Existing stakeholders may feel like they were overcharged if the price is reduced for more -address space. +Existing stakeholders may feel like they were overcharged if the price is reduced for more address space. ## Rationale and Alternatives @@ -99,17 +97,11 @@ As noted in Detailed Explanation, DevAddr can be acquired as part of a NetID and ## Unresolved Questions -Would it be more reasonable to move to a lower cost but more address space allocation for a one time -fee? Or possibly move to a much lower cost but yearly rent on the existing address space thus helping to -be more accessible and help drive up IOT usage. +Would it be more reasonable to move to a lower cost but more address space allocation for a one time fee? Or possibly move to a much lower cost but yearly rent on the existing address space thus helping to be more accessible and help drive up IOT usage. ## Deployment Impact -By making the Helium Network more accessible and lowering the cost to encourage IoT network usage being the main -factor. We expect the deployment impact to be positive with the lowering of the cost of offering hosting -to existing stakeholders I would expect this to be filtered all the way down to cost of paid hosting services, -as well as lower the barrier for small scale deployments to enter and use the network being more -attractive. +By making the Helium Network more accessible and lowering the cost to encourage IoT network usage being the main factor. We expect the deployment impact to be positive with the lowering of the cost of offering hosting to existing stakeholders I would expect this to be filtered all the way down to cost of paid hosting services, as well as lower the barrier for small scale deployments to enter and use the network being more attractive. ## Success Metrics From 45a362a23c44415201ed028b67086c7b9564ffc5 Mon Sep 17 00:00:00 2001 From: Joey Hiller <1965053+jthiller@users.noreply.github.com> Date: Wed, 1 May 2024 20:26:21 -0700 Subject: [PATCH 6/8] Update HIP title --- 0116-oui-additional-address-space-reshuffle.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0116-oui-additional-address-space-reshuffle.md b/0116-oui-additional-address-space-reshuffle.md index e671e268c..666d05c69 100644 --- a/0116-oui-additional-address-space-reshuffle.md +++ b/0116-oui-additional-address-space-reshuffle.md @@ -1,4 +1,4 @@ -# HIP 116: OUI Additional Address Space Reshuffle +# HIP 116: LoRaWAN Device Address Price Adjustment - Author(s): [@ccall48](https://github.com/ccall48), [@nowiresfil](https://github.com/nowiresfil), Members of the IoT Working Group - Start Date: 2024-03-25 From 800da94482884bd055c0239b7ba90a8c913c2a0d Mon Sep 17 00:00:00 2001 From: Joey Hiller <1965053+jthiller@users.noreply.github.com> Date: Wed, 1 May 2024 21:27:18 -0700 Subject: [PATCH 7/8] Update HIP filename --- ...huffle.md => 0116-lorawan-device-address-price-adjustment.md | 0 README.md | 2 +- 2 files changed, 1 insertion(+), 1 deletion(-) rename 0116-oui-additional-address-space-reshuffle.md => 0116-lorawan-device-address-price-adjustment.md (100%) diff --git a/0116-oui-additional-address-space-reshuffle.md b/0116-lorawan-device-address-price-adjustment.md similarity index 100% rename from 0116-oui-additional-address-space-reshuffle.md rename to 0116-lorawan-device-address-price-adjustment.md diff --git a/README.md b/README.md index 9c0209d03..b50bf26ef 100644 --- a/README.md +++ b/README.md @@ -129,7 +129,7 @@ If you have questions or feedback, please see the [Discussion](https://github.co | 113 | [Reward CBRS As Experimental](0113-reward-cbrs-as-experimental.md) | [](https://github.com/helium/HIP/issues/934) | | 114 | [Incentive Escrow Fund for Subscriber Referrals](0114-incentive-escrow-fund-for-subscriber-referrals.md) | [](https://github.com/helium/HIP/issues/942) | | 115 | [Redefining the MOBILE Maker Approval Process](0115-redefining-the-mobile-maker-approval-process.md) | [](https://github.com/helium/HIP/issues/957) | -| 116 | [OUI Additional Address Space Reshuffle](0116-oui-additional-address-space-reshuffle.md) | [](https://github.com/helium/HIP/issues/959) | +| 116 | [OUI Additional Address Space Reshuffle](0116-lorawan-device-address-price-adjustment.md) | [](https://github.com/helium/HIP/issues/959) | | 117 | [Add MNTD. as a Hotspot Vendor to the Helium MOBILE subNetwork](0117-mntd-mobile-hotspot-vendor.md) | [](https://github.com/helium/HIP/issues/962) | | 118 | [Verification Mapping for MOBILE Network](0118-verification-mapping.md) | [](https://github.com/helium/HIP/issues/966) | | 119 | [Closing Gaming Loopholes Within the MOBILE Network](0119-closing-gaming-loopholes-within-the-mobile-network.md) | [](https://github.com/helium/HIP/issues/989) | From c07944c87a477d88fcca274dc869ecc712e3e3f0 Mon Sep 17 00:00:00 2001 From: Joey Hiller <1965053+jthiller@users.noreply.github.com> Date: Thu, 2 May 2024 09:45:41 -0700 Subject: [PATCH 8/8] Update label Co-authored-by: Abhay Kumar <75+abhay@users.noreply.github.com> --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index b50bf26ef..ffb9394ce 100644 --- a/README.md +++ b/README.md @@ -129,7 +129,7 @@ If you have questions or feedback, please see the [Discussion](https://github.co | 113 | [Reward CBRS As Experimental](0113-reward-cbrs-as-experimental.md) | [](https://github.com/helium/HIP/issues/934) | | 114 | [Incentive Escrow Fund for Subscriber Referrals](0114-incentive-escrow-fund-for-subscriber-referrals.md) | [](https://github.com/helium/HIP/issues/942) | | 115 | [Redefining the MOBILE Maker Approval Process](0115-redefining-the-mobile-maker-approval-process.md) | [](https://github.com/helium/HIP/issues/957) | -| 116 | [OUI Additional Address Space Reshuffle](0116-lorawan-device-address-price-adjustment.md) | [](https://github.com/helium/HIP/issues/959) | +| 116 | [LoRaWAN Device Address Price Adjustment](0116-lorawan-device-address-price-adjustment.md) | [](https://github.com/helium/HIP/issues/959) | | 117 | [Add MNTD. as a Hotspot Vendor to the Helium MOBILE subNetwork](0117-mntd-mobile-hotspot-vendor.md) | [](https://github.com/helium/HIP/issues/962) | | 118 | [Verification Mapping for MOBILE Network](0118-verification-mapping.md) | [](https://github.com/helium/HIP/issues/966) | | 119 | [Closing Gaming Loopholes Within the MOBILE Network](0119-closing-gaming-loopholes-within-the-mobile-network.md) | [](https://github.com/helium/HIP/issues/989) |