diff --git a/0069-reassertion-fee-reduction.md b/0069-reassertion-fee-reduction.md index 2cb5c2051..ec03df8c4 100644 --- a/0069-reassertion-fee-reduction.md +++ b/0069-reassertion-fee-reduction.md @@ -13,11 +13,13 @@ The average daily mining reward per hotspot is currently equal to around 50,000 As a result, it would take nearly a month for the average hotspot to earn enough to pay for one location reassertion. -Therefore, if we are trying to expand the network and want hotspots in saturated areas to move into less saturated areas (or moreover in lone wolf like areas), want to ease the burden on new people joining the network, and ease the burden on people making human errors, the current reassertion price is not viable and needs to be reduced. +Therefore, if we are trying to expand the network and want hotspots in saturated areas to move into less saturated areas, want to ease the burden on new people joining the network, and ease the burden on people making human errors, the current reassertion price is not viable and needs to be reduced. + # Stakeholders -In reality, since less DC burned has an economic impact, this hip affects everyone. Directly, this hip affects everyone that is reasserting their hotspots. Additionally, since people will need to be able to see their reassertion fee amounts prior to submitting the reassertion fee DC burn transaction which is a function of the Vendor Apps, this HIP directly affects all owners of Vendor apps. +In reality, since the amount of DC burned has an economic impact, this hip affects everyone. Directly, this hip affects everyone that is reasserting their hotspots. Additionally, since people will need to be able to see their reassertion fee amounts prior to submitting the reassertion fee DC burn transaction which is a function of the Vendor Apps, this HIP directly affects all owners of Vendor apps. + # Detailed Explanation @@ -30,23 +32,22 @@ Therefore, if we are trying to expand the network and want hotspots in saturated In order to help expand the network and ease the burden on new people joining the network, I'm proposing that the reassertion price be reduced from 1,000,000 DC, to half which is 500,000 DC. -Please note that I specifically chose 500,000 DC and not less (say 10,000 DC), to help prevent people from taking advantage of reduced reassertion fees. +Please note that I specifically chose 500,000 DC and not less (say 10,000 DC), to help prevent people from taking advantage of reduced reassertion fees, and to lesson the economical effect on the Network. In addition, to prevent location spoofing as a result of reassertion fees deduction, any given individual hotspot may only have its reassertion fees reduced every 525k blocks (approximately once per year). Furthermore, in order to help prevent abuse of the reassertion fee reduction, there will be a minimum distance of 10KM (between the original location to the reasserted location) requirement. -Finally, the reassertion fee reduction will only apply to those inserting their hotspots into Res8 hexes of < 3 (less than 3) hotpots. +Finally, the reassertion fee reduction will only apply to those inserting their hotspots into Res8 hexes of < 3 (less than three) hotpots. With the reassertion fees reduced to 500,000 DC, it would still require the average hotspot to spend approximately 10 days worth of mining for the reassertions. Thus, the 500,000 DC fee in addition to the three aforementioned gaming prevention methods are still preventing excessive/unnecessary reassertions, while also making it easier for those that want to expand the network and actually move their hotspots locations to that end. + +**To clarify all methods provided to help prevent location spoofing or gaming as a result of the reassertion fees deduction in summary:** - -**To clarify all methods provided to help prevent location spoofing as a result of the reassertion fees deduction in summary:** - - - This HIP only applies to **RE**assertions. Not the first assertion/onboarding. To clarify, the original/first location assertion price would not be changed, merely the reassertion prices (from the 2nd assertion and on.) + - This HIP only applies to **RE**assertions. Not the first assertion/onboarding. To clarify, the original/first location assertion price will not be changed, merely the reassertion prices (from the 2nd assertion and on.) - This HIP only applies to those who are REasserting their hotspots to a distance equal to or greater than 10km (away from the original location point that is being changed). As a direct result, this HIP will not help those trying to increase their TS scales. @@ -59,11 +60,11 @@ Thus, the 500,000 DC fee in addition to the three aforementioned gaming preventi **This HIP will be implemented in two stages:** - 1) Upon community vote approval, the current 1,000,000 DC reassertion fee amount will immediately be reduced to 500,000 DC. - + 1) Upon community vote approval, the current 1,000,000 DC reassertion fee amount will immediately be reduced to 500,000 DC. Stage 2 will only be implemented if we see hotspots moving to a distance of 10km or greater, within Res8 hexes that contain less than 3 hotspots (post stage 1). + 2) In order to dynamically meet the goals of this HIP regardless of the future oracle price, monthly rewards, and daily average DC earned per hotspot, the following mathematical equation/logic will be implemented. - * (((("monthly_reward"/100000000 * 0.6115) / Active Hotspots) / 30 Days) * Oracle Price) * (8 / 0.00001) = Reassert Fee In DC. + * (((("monthly_reward"/100000000 * (dc_percent + poc_challengees_percent + poc_witnesses_percent)) / Active Hotspots) / 30 Days) * Oracle Price) * (8 / 0.00001) = Reassert Fee In DC. Additionally, there will always be a minimum of 100,000 DC and maximum of 500,000 DC reassertion fee requirement that supersedes the above equation, using the following logic. @@ -71,23 +72,33 @@ Additionally, there will always be a minimum of 100,000 DC and maximum of 500,00 * IF "Reassert Fee In DC" < 100,000 THEN "Reassert Fee In DC" = 100,000 + +**To explain the mathematical equation/logic:** + +(Average Daily Rewards Per Hotspots [HNT/day]) x OraclePrice[USD/HNT] x 8 [Days] x 100.000 [DC/USD] = Reassert Fee In DC. + +In stage two, the reassertion fee will be dynamically calculated by what an average hotspot earns. These earnings change, depending on the monthly rewards target set by the HIP 20 halvings schedule, the number of active hotspots, and the price of HNT. This notwithstanding, the reassertion fee shall never be higher than 500,000 DC (5 USD) and never lower than 100,000 DC (1 USD). + + # Drawbacks -Although the aforementioned gaming prevention methods will drastically reduce the chances of gaming as a result of the reassertion fee reduction, location spoofers may benefit from reduced reassertion fees. Nevertheless, it will be impossible for any given hotspot to benefit from the reasserton fee reduction more than once every 525k blocks (approximately once per year). +Although the aforementioned gaming prevention methods will drastically reduce the possibilities of gaming as a result of the reassertion fee reduction, location spoofers may benefit from reduced reassertion fees. Nevertheless, it will be impossible for any given hotspot to benefit from the reassertion fee reduction more than once every 525k blocks (approximately once per year). + # Rationale Not doing this can possibly result in people who may have moved from an over saturated areas to much less saturated areas, but may not do so on the notion that the reassertion fee in and of itself would cost many months (if not longer) worth of mining. Additionally, without this HIP, the reassertion fee burden will not be lighter for those joining the network (for example people who purchase a second hand hotspot and need to reassert their location), and those who made human errors (such as "fat finger" mistakes of placing their hotspots into the wrong location accidentally). + # Unresolved Questions -On the economic effect, burning less HNT as a result of reduced reassertion fees, has a negative economic impact. Therefore, to what degree will this HIP negatively impact the Network's economics? +On the economic effect, burning less HNT as a result of reduced reassertion fees, has a negative economic impact. However, there may end up being more DC burned from more location assertions (than there were prior to the reassertion fee reduction.) Therefore, will this HIP impact the Network's economics negatively or positively? -On the UX side, the non-scoped factors are the work that is needed in various maker apps, ensuring that all Hotspots can use the variable rate (depending on the aforementioned equation/logic). Additionally, if a maker decides not to respect the reassertion fee reduction amount, the chain may accept the higher fee amount (which cannot be undone). +On the UX side, the non-scoped factors are the work that is needed in various maker apps, ensuring that all hotspots can use the variable rate (depending on the aforementioned equation/logic). Additionally, if a maker decides not to respect the reassertion fee reduction amount, the chain may accept the higher fee amount (which cannot be undone). As far as resourcing, who will build/write the code? - + + # Success Metrics -Success may be measured, once we see people being issued the reassertion fee reduction. - +Success may be measured, once we see hotspots moving to a distance of 10km or greater, within Res8 hexes that contain less than 3 hotspots.