You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 0052-lorawan-dao.md
+36-18
Original file line number
Diff line number
Diff line change
@@ -10,13 +10,13 @@
10
10
# Summary
11
11
[summary]: #summary
12
12
13
-
This proposal includes a specification of the LoRaWAN Wireless Network Protocol
13
+
This proposal includes a specification of the LoRaWAN Decentralized Network Protocol
14
14
as per the DAO model and L2 implementation outlined in [HIP 51][hip51].
15
15
16
-
In HIP 51, we provide a general structure for onboarding new WNPs to the broader
16
+
In HIP 51, we provide a general structure for onboarding new DNPs to the broader
17
17
Helium Network, with mechanisms in place to ensure that protocol-specific
18
18
attributes such as Proof-of-Coverage rules, data credits pricing, and block
19
-
validation are within control of the emergent WNT DAO.
19
+
validation are within control of the emergent DNT DAO.
20
20
21
21
In this proposal, we specify the implementation of the structure proposed
22
22
through a detailed onboarding proposal for the LoRaWAN Network. We propose
@@ -32,10 +32,10 @@ Community.
32
32
# Detailed Description
33
33
[detailed-description]: #detailed-description
34
34
35
-
We proposed in HIP 51 that each WNP subDAO operate as a sovereign economics and
35
+
We proposed in HIP 51 that each DNP subDAO operate as a sovereign economics and
36
36
governance layer. The LoRaWAN subDAO has five core functions
37
37
38
-
1.*Economics*: The LoRaWAN subDAO handles all bonding curve operations, and by
38
+
1.*Economics*: The LoRaWAN subDAO handles all Programmatic Treasury operations, and by
39
39
extension all LRW emissions to hotspots and purchases or sales from
40
40
third-parties. The economic responsibilities around this involve parameter
41
41
selection for the curve and all associated fees, as well as liquidity risk
@@ -74,7 +74,9 @@ In the notation provided below, P represents Price and S represents Supply. The
74
74
quote currency is LRW (LoRaWAN Token) and the base currency is HNT (Helium
75
75
Token).
76
76
77
-
We propose that the LoRaWAN bonding curves take the following shape:
77
+
In HIP 51, we proposed that programmatic treasuries are designed to be one-way i.e. only DNT token holders can interact with the programmatic treasury with intent to sell. Network participants cannot purchase DNT tokens against HNT, although non-profit actors like DeWi can “donate” tokens into the programmatic treasury without receiving any assets in return. The intended effect of this is to mitigate speculation that could be harmful for DNP miners.
78
+
79
+
We propose that the LoRaWAN Programmatic Treasury takes the following shape:
@@ -114,9 +116,22 @@ subsequently distributes the determined amount of HNT to the LoRaWAN subDAO
114
116
multi-signature wallet, the addresses of which comprise the set of Validators of
115
117
the LoRaWAN Network.
116
118
117
-
For more background on interpreting bonding curves, [Strata protocol
118
-
documentation](https://www.strataprotocol.com/docs/learn/bonding_curves) is
119
-
extremely instructive.
119
+
There is a 0.3% transaction fee on all inflows and outflows within the programmatic treasury. For example, if emissions into the curve in a given epoch amount to 100 HNT, 99.7 HNT worth of LRW tokens will be allocated for stakeholder rewards (miners, validators) and 0.3 HNT worth of LRW tokens will be placed into a subDAO reserve.
120
+
121
+
The subDAO reserve is intended to allow the DNT to perform bespoke operations to create and sustain network growth. The primary use case of the reserve is to fund all state transition transaction fees to the L1, but can be deployed in any manner of ways as per subDAO governance. Such incentives could include
122
+
123
+
1. One-time DNT or HNT bonuses for hotspots providing continuous coverage in new regions deemed to be economically valuable by governance
124
+
125
+
2. Bonus rewards for hotspots and OUIs that are consistent in network activity and meet certain good actor conditions
126
+
127
+
3. Surge-pricing style dynamic multipliers based on data transfer activity for individual regions
128
+
129
+
4. Bespoke incentives for validators and manufacturers on the basis of changing network demands
130
+
131
+
132
+
DAOs are responsible for managing risk within their protocols in that they define programmatic treasury issuance formulas and set transaction fees. They inherently handle the implied effect of DNT market capitalization
133
+
134
+
Note that a given DNP subDAO is not necessarily required to distribute the entirety of HNT it receives into the programmatic treasury, or distribute the entirety of DNTs minted in the process to stakeholders. The subDAO can manage and allocate HNT inflows from the overall network as it sees fit in order to support growth in bespoke areas through incentives for new stakeholders.
120
135
121
136
## Validator Operations
122
137
@@ -191,6 +206,13 @@ both obtaining the original PoC request and for encrypting each layer of the
191
206
challenge packet. This crucial information, which has been hidden until the
192
207
receipt is published, allows the re-creation of the deterministic entropy.
193
208
209
+
HIP-17 specified a rewards mechanism to incentivize hotspots in distinct locations representing a larger area of network coverage as opposed to devices in close proximity to each other. In order to incentivize greater land coverage of hotspots in new areas, we propose that for each new H7 hex in which a set of hotspots is deployed, a one-time 1500 LRW bonus is allocated for the first hotspot that successfully responds to 150 consecutive challenges. Note that this bonus is funded by the subDAO reserve.Note that this bonus is funded by the subDAO reserve. If the hotspot goes offline at any time prior to the completion of 150 challenges, the counter is reset and any other hotspot may complete the task to receive the bonus.
210
+
For example, consider three hotspots deployed simultaneously in a hex that has not previously been covered by the LoRaWan network. Each hotspot to be deployed in that hex is eligible to receive the bonus.
211
+
If there is an interruption in coverage in two of the hotspots at a time prior to the completion of the 150 consecutive challenges, the remaining hotspot receives the bonus.
212
+
If there is an interruption in coverage in one of the hotspots at a time prior to the completion of the 150 consecutive challenges, the remaining hotspots split the bonus equally. If all three hotspots complete the 150 consecutive challenges, they split the bonus equally.
213
+
If all three hotspots experience interruptions prior to the completion of the challenge, the counter resets and the first hotspot to complete 150 consecutive challenges receives the bonus.
214
+
215
+
194
216
## Data Transfer and Pricing Specification
195
217
196
218
Data Credits are utilized in asserting new hotspots and their location on the
@@ -222,11 +244,7 @@ Tokens Allocated to Hotspots.
222
244
223
245
![lrw distribution above market value][lrw-distribution-above-market-value]
224
246
225
-
Note that all manufacturers within the network must stake a minimum of
226
-
1,000,000 LRW tokens in order to be whitelisted to receive rewards. If at any
227
-
point, a manufacturer gives ownership of maintenance and firmware upgrades to a
228
-
third party, all future manufacturer rewards flow to this new entity. The new
229
-
hotspot onboarding fee and location assertion fee should remain the same.
247
+
Note that all manufacturers within the LoRaWAN networksubDAO must stake a minimum of 10,000,000 HNTLRWin order to be whitelisted to receive rewards. The intention of this requirement is to increase the security of the network. In exchange for this stake, manufacturers earn 2% of LRW mined by hotspots they sold and maintain. The intention is to create incentives for manufacturers to build high quality hotspots which maximize mining output and to continue to support previously sold hotspots into the future. If at any point, a manufacturer gives ownership of maintenance and firmware upgrades to a third party, all future manufacturer rewards flow to this new entity.
230
248
231
249
At present, every 24 bytes sent in a packet cost 1 DC, priced at $0.00001. Data
232
250
Credits are generated by burning the requisite amount of HNT as per the Helium
@@ -249,12 +267,12 @@ credits per minute, and attribution to hotspots after consumption occurs pro
249
267
rata network traffic under the unmetered plan.*
250
268
251
269
A subDAO governed transaction fee is placed on issuance and redemption of LRW
252
-
tokens on the bonding curve. This fee is charged in HNT and we propose starting
270
+
tokens on the Programmatic Treasury. This fee is charged in HNT and we propose starting
253
271
it at 0.3% of all transactions. This HNT fee is immediately submitted to the LRW
254
-
bonding curve.
272
+
Programmatic Treasury.
255
273
256
-
*Note that a given WNP subDAO is not necessarily required to distribute the
257
-
entirety of HNT it receives into the curve, or distribute the entirety of WNTs
274
+
*Note that a given DNP subDAO is not necessarily required to distribute the
275
+
entirety of HNT it receives into the curve, or distribute the entirety of DNTs
258
276
minted in the process to stakeholders. The subDAO can manage and allocate HNT
259
277
inflows from the overall network as it sees fit in order to support growth in
260
278
bespoke areas through incentives for new stakeholders.*
0 commit comments