From 992890592be1363aaeb7cbe12187b85c98187cc8 Mon Sep 17 00:00:00 2001 From: mrfizzy99 <84468997+mrfizzy99@users.noreply.github.com> Date: Wed, 11 Sep 2024 23:50:39 -0500 Subject: [PATCH 01/11] hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This HIP aims to further the refinement of HIP-131, and will further extend the scope of HIP-131 to cover all remaining areas that were not previously included (such as C** areas). It also extends the active duration of HIP-131 (from 150 epochs) to not expire until both phases of HIP-118 are fully implemented and active to the point that the Service Provider is satisfied with it being a replacement of this (HIP-131). Additionally we propose to also put a 42-epoch renewal (every 6 weeks) on valid CDR information. It will also allow a Service Provider to utilize CDR information as part of HIP-118 (Verification Mapping for MOBILE Network) if they choose to do so. Finally, crack down a little more on gaming boosted areas with a requirement with a 7 day CDR requirement that will get invalidated if a invalid CDR is detected, which will be be at the digestion of the Service Provider. --- ...idging-gap-for-anti-gaming-measures-phase2 | 64 +++++++++++++++++++ 1 file changed, 64 insertions(+) create mode 100644 hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 diff --git a/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 b/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 new file mode 100644 index 000000000..74b8e4291 --- /dev/null +++ b/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 @@ -0,0 +1,64 @@ +HIP-xxx - Bridging Gap for Anti-Gaming Measures Phase2 + +Author(s): - Author(s): [Fizzy99](https://github.com/mrfizzy99), [Rendell](https://github.com/RendellD85) +Start Date: 2024-09-05 +Category: Economic, Technical +Original HIP PR: +Tracking Issue: +Voting Requirements: veMOBILE Holder + +--- + +## Summary + +This HIP aims to further the refinement of HIP-131, and will further extend the scope of HIP-131 to cover all remaining areas that were not previously included (such as C** areas). It also extends the active duration of HIP-131 (from 150 epochs) to not expire until both phases of HIP-118 are fully implemented and active to the point that the Service Provider is satisfied with it being a replacement of this (HIP-131). Additionally we propose to also put a 42-epoch renewal (every 6 weeks) on valid CDR information. It will also allow a Service Provider to utilize CDR information as part of HIP-118 (Verification Mapping for MOBILE Network) if they choose to do so. Finally, crack down a little more on gaming boosted areas with a requirement with a 7 day CDR requirement that will get invalidated if a invalid CDR is detected, which will be be at the digestion of the Service Provider. + + +## Related Prior HIPs +* [HIP 103: MOBILE Oracle Hex Boosting](./0103-oracle-hex-boosting.md) +* [HIP 118: Verification Mapping for MOBILE Network](./0118-verification-mapping.md) +* [HIP 125: Temporary Anti-Gaming Measures For Boosted Hexes](./0125-temporary-anti-gaming-measures-for-boosted-hexes.md) +* [HIP 131: HIP-131: Bridging Gap Between Verification Mappers and Anti-Gaming Measures](./0131-bridging-gap-between-verification-mappers-and-anti-gaming-measures.md) + + +## Motivation + +While we thought that 'C' footfall areas would be less utilized for gaming activities, we were wrong. Gamers have found refuge in C footfall areas as the first phase of HIP-131 was implemented. Our hopes that making a CDR requirement to activate PoC rewards becomes the norm for all location asserts. + +## Stakeholders +* Deployers: This preserves POI hex rewards for legitimate and active coverage builders. +* Service Providers: This provides a temporary tool to prevent abuse of POI hexes, helping ensure these strategic regions have legitimate coverage and further improve implementation of HIP-118. + + +## Detailed Explanation + +This HIP would enact the following: +- Extend the valid CDR requirement from HIP-131 from only applying to hotspots in Oracle Boosting Multiplier areas (A**, B**), to apply to all areas (A**, B**, and C**). +- Adjust the HIP-131 requirement (A**, B**, and C**) to require a valid CDR every 42 epochs. +- For Boosteed Service Provider locations, a valid CDR will be required every 7 epochs. If a invalid CDR is registered, it will invalidate the valid CDR. This will left up to the Service provider to quality control what does or does not qualify. +- Extend the duration of HIP-131 (from 150 epochs) to last until both phases of HIP-118 are fully implemented and active. +- Allow HIP-118 (Verification Mapping for MOBILE Network) to utilize CDR information if the Server Provider chooses for all areas, including Serviuce Provider Boosted areas.  + + +## Drawbacks + +Having a 42 epoch renewal may be viewed as counterintuitive, but this allows the network to filter out non-utilized hotspots from earning PoC for extended periods of time throughout the hotspot or radios lifetime. + + +## Unresolved Questions + +None. + + +## Implementation + +Nova Labs and Helium Mobile have agreed to the implementation of this proposal, which will be implemented immediately after passing a vote. +Mobile Oracles will report tagging of the hotspots for suspicious activity by the SPs. This off-chain data will record both tagging and untagging activities for the concerned hotspots. This data will be shared in a way that community applications can allow a deployer to understand concerned hotspots have been flagged. +Current SP has indicated they will use their existing support ticket system to manage deployers that feel they have been mistakenly identified as malicious, including an internal escalation procedure to help mitigate support tickets being left unaddressed indefinitely. + +## Success Metrics + +The desired outcome of this HIP is that Oracle Hex Boosted areas are deployed with mobile hotspots that provide high quality, usable cellular coverage for customers of the MOBILE network and attract potential SPs. +Measuring the success of this HIP will require ongoing collaboration with the SP to understand how many mobile hotspots are potentially flagged as malicious through community forums such as the mobile working group community. +Success of this HIP will be measured by the amount of discouragement of illegitimate deployments, and an increase of CDR data in legitimate hotspots. + From a46aff1a815c5acfe32e97ac6fc864a744461ba0 Mon Sep 17 00:00:00 2001 From: mrfizzy99 <84468997+mrfizzy99@users.noreply.github.com> Date: Wed, 11 Sep 2024 23:53:42 -0500 Subject: [PATCH 02/11] Update hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 Spelling --- hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 b/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 index 74b8e4291..d8f932da8 100644 --- a/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 +++ b/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 @@ -11,7 +11,7 @@ Voting Requirements: veMOBILE Holder ## Summary -This HIP aims to further the refinement of HIP-131, and will further extend the scope of HIP-131 to cover all remaining areas that were not previously included (such as C** areas). It also extends the active duration of HIP-131 (from 150 epochs) to not expire until both phases of HIP-118 are fully implemented and active to the point that the Service Provider is satisfied with it being a replacement of this (HIP-131). Additionally we propose to also put a 42-epoch renewal (every 6 weeks) on valid CDR information. It will also allow a Service Provider to utilize CDR information as part of HIP-118 (Verification Mapping for MOBILE Network) if they choose to do so. Finally, crack down a little more on gaming boosted areas with a requirement with a 7 day CDR requirement that will get invalidated if a invalid CDR is detected, which will be be at the digestion of the Service Provider. +This HIP aims to further the refinement of HIP-131, and will further extend the scope of HIP-131 to cover all remaining areas that were not previously included (such as C** areas). It also extends the active duration of HIP-131 (from 150 epochs) to not expire until both phases of HIP-118 are fully implemented and active to the point that the Service Provider is satisfied with it being a replacement of this (HIP-131). Additionally we propose to also put a 42-epoch renewal (every 6 weeks) on valid CDR information. It will also allow a Service Provider to utilize CDR information as part of HIP-118 (Verification Mapping for MOBILE Network) if they choose to do so. Finally, crack down a little more on gaming boosted areas with a requirement with a 7 day CDR requirement that will get invalidated if a invalid CDR is detected, which will be be at the discretion of the Service Provider. ## Related Prior HIPs From c026b9be4548a51bed3527cc2d34f1e6a3dd6bb9 Mon Sep 17 00:00:00 2001 From: mrfizzy99 <84468997+mrfizzy99@users.noreply.github.com> Date: Wed, 11 Sep 2024 23:56:13 -0500 Subject: [PATCH 03/11] Update hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 grammer --- hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 b/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 index d8f932da8..ed365a077 100644 --- a/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 +++ b/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 @@ -35,7 +35,7 @@ While we thought that 'C' footfall areas would be less utilized for gaming activ This HIP would enact the following: - Extend the valid CDR requirement from HIP-131 from only applying to hotspots in Oracle Boosting Multiplier areas (A**, B**), to apply to all areas (A**, B**, and C**). - Adjust the HIP-131 requirement (A**, B**, and C**) to require a valid CDR every 42 epochs. -- For Boosteed Service Provider locations, a valid CDR will be required every 7 epochs. If a invalid CDR is registered, it will invalidate the valid CDR. This will left up to the Service provider to quality control what does or does not qualify. +- For Boosteed Service Provider locations, a valid CDR will be required every 7 epochs. If a invalid CDR is registered, it will invalidate the valid CDR. This will be left up to the Service provider to quality control what does or does not qualify. - Extend the duration of HIP-131 (from 150 epochs) to last until both phases of HIP-118 are fully implemented and active. - Allow HIP-118 (Verification Mapping for MOBILE Network) to utilize CDR information if the Server Provider chooses for all areas, including Serviuce Provider Boosted areas.  From de2e5f32a7a8661d8b1e66f849fad7c82ecdb3ca Mon Sep 17 00:00:00 2001 From: mrfizzy99 <84468997+mrfizzy99@users.noreply.github.com> Date: Wed, 18 Sep 2024 19:42:33 -0500 Subject: [PATCH 04/11] Update hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 Summary --- hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 b/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 index ed365a077..d7cca6c52 100644 --- a/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 +++ b/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 @@ -11,7 +11,7 @@ Voting Requirements: veMOBILE Holder ## Summary -This HIP aims to further the refinement of HIP-131, and will further extend the scope of HIP-131 to cover all remaining areas that were not previously included (such as C** areas). It also extends the active duration of HIP-131 (from 150 epochs) to not expire until both phases of HIP-118 are fully implemented and active to the point that the Service Provider is satisfied with it being a replacement of this (HIP-131). Additionally we propose to also put a 42-epoch renewal (every 6 weeks) on valid CDR information. It will also allow a Service Provider to utilize CDR information as part of HIP-118 (Verification Mapping for MOBILE Network) if they choose to do so. Finally, crack down a little more on gaming boosted areas with a requirement with a 7 day CDR requirement that will get invalidated if a invalid CDR is detected, which will be be at the discretion of the Service Provider. +This HIP aims to further the refinement of HIP-131, and will further extend the scope of HIP-131 to cover all remaining areas that were not previously included (such as C** areas), along with other tweaks and changes. ## Related Prior HIPs From bd3562bb1f1327506b1954134741b98a52d18a18 Mon Sep 17 00:00:00 2001 From: mrfizzy99 <84468997+mrfizzy99@users.noreply.github.com> Date: Fri, 27 Sep 2024 16:54:43 -0500 Subject: [PATCH 05/11] Update hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 abhay suggestions approved Co-authored-by: Abhay Kumar <75+abhay@users.noreply.github.com> --- hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 b/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 index d7cca6c52..071298489 100644 --- a/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 +++ b/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 @@ -1,6 +1,6 @@ HIP-xxx - Bridging Gap for Anti-Gaming Measures Phase2 -Author(s): - Author(s): [Fizzy99](https://github.com/mrfizzy99), [Rendell](https://github.com/RendellD85) +Authors: [Fizzy99](https://github.com/mrfizzy99), [Rendell](https://github.com/RendellD85) Start Date: 2024-09-05 Category: Economic, Technical Original HIP PR: From fe823eb5d3d3827d04be0a7612f62da90e5b9684 Mon Sep 17 00:00:00 2001 From: mrfizzy99 <84468997+mrfizzy99@users.noreply.github.com> Date: Fri, 27 Sep 2024 16:54:59 -0500 Subject: [PATCH 06/11] Update hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 suggestions approved Co-authored-by: Abhay Kumar <75+abhay@users.noreply.github.com> --- hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 b/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 index 071298489..9825d6b3a 100644 --- a/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 +++ b/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 @@ -5,7 +5,7 @@ Start Date: 2024-09-05 Category: Economic, Technical Original HIP PR: Tracking Issue: -Voting Requirements: veMOBILE Holder +Voting Requirements: veMOBILE Holders --- From fe74bf0ad1ead0acf459532688545e12a74b1711 Mon Sep 17 00:00:00 2001 From: mrfizzy99 <84468997+mrfizzy99@users.noreply.github.com> Date: Fri, 27 Sep 2024 16:55:05 -0500 Subject: [PATCH 07/11] Update hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 suggestions approved Co-authored-by: Abhay Kumar <75+abhay@users.noreply.github.com> --- hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 b/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 index 9825d6b3a..30f648cab 100644 --- a/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 +++ b/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 @@ -35,7 +35,7 @@ While we thought that 'C' footfall areas would be less utilized for gaming activ This HIP would enact the following: - Extend the valid CDR requirement from HIP-131 from only applying to hotspots in Oracle Boosting Multiplier areas (A**, B**), to apply to all areas (A**, B**, and C**). - Adjust the HIP-131 requirement (A**, B**, and C**) to require a valid CDR every 42 epochs. -- For Boosteed Service Provider locations, a valid CDR will be required every 7 epochs. If a invalid CDR is registered, it will invalidate the valid CDR. This will be left up to the Service provider to quality control what does or does not qualify. +- For Boosteed Service Provider locations, a valid CDR will be required every 7 epochs. If an invalid CDR is registered, it will invalidate the valid CDR. This will be left up to the Service provider to quality control what does or does not qualify. - Extend the duration of HIP-131 (from 150 epochs) to last until both phases of HIP-118 are fully implemented and active. - Allow HIP-118 (Verification Mapping for MOBILE Network) to utilize CDR information if the Server Provider chooses for all areas, including Serviuce Provider Boosted areas.  From 76a3c17ef5fe3062fc33e4ea71d80e22031402c2 Mon Sep 17 00:00:00 2001 From: mrfizzy99 <84468997+mrfizzy99@users.noreply.github.com> Date: Fri, 27 Sep 2024 16:55:13 -0500 Subject: [PATCH 08/11] Update hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 suggestions approved Co-authored-by: Abhay Kumar <75+abhay@users.noreply.github.com> --- hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 b/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 index 30f648cab..b4c6f288a 100644 --- a/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 +++ b/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 @@ -37,7 +37,7 @@ This HIP would enact the following: - Adjust the HIP-131 requirement (A**, B**, and C**) to require a valid CDR every 42 epochs. - For Boosteed Service Provider locations, a valid CDR will be required every 7 epochs. If an invalid CDR is registered, it will invalidate the valid CDR. This will be left up to the Service provider to quality control what does or does not qualify. - Extend the duration of HIP-131 (from 150 epochs) to last until both phases of HIP-118 are fully implemented and active. -- Allow HIP-118 (Verification Mapping for MOBILE Network) to utilize CDR information if the Server Provider chooses for all areas, including Serviuce Provider Boosted areas.  +- Allow HIP-118 (Verification Mapping for MOBILE Network) to utilize CDR information if the Server Provider chooses for all areas, including Service Provider Boosted areas. ## Drawbacks From b4f2872dceebafcb6202238984cf23bbf109fc40 Mon Sep 17 00:00:00 2001 From: Abhay Kumar <75+abhay@users.noreply.github.com> Date: Mon, 7 Oct 2024 17:53:26 -0700 Subject: [PATCH 09/11] Update hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 --- hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 b/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 index b4c6f288a..7620f0f3c 100644 --- a/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 +++ b/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 @@ -1,4 +1,4 @@ -HIP-xxx - Bridging Gap for Anti-Gaming Measures Phase2 +# HIP-xxx - Bridging Gap for Anti-Gaming Measures Phase 2 Authors: [Fizzy99](https://github.com/mrfizzy99), [Rendell](https://github.com/RendellD85) Start Date: 2024-09-05 From fd5ddc17a8c09fc634cdae75e73ef42f9df75428 Mon Sep 17 00:00:00 2001 From: Abhay Kumar <75+abhay@users.noreply.github.com> Date: Mon, 7 Oct 2024 18:24:34 -0700 Subject: [PATCH 10/11] Several updates for clarity --- ...idging-gap-for-anti-gaming-measures-phase2 | 64 ------------------- ...ing-gap-for-anti-gaming-measures-phase2.md | 62 ++++++++++++++++++ 2 files changed, 62 insertions(+), 64 deletions(-) delete mode 100644 hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 create mode 100644 xxx-bridging-gap-for-anti-gaming-measures-phase2.md diff --git a/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 b/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 deleted file mode 100644 index 7620f0f3c..000000000 --- a/hip-xxx-bridging-gap-for-anti-gaming-measures-phase2 +++ /dev/null @@ -1,64 +0,0 @@ -# HIP-xxx - Bridging Gap for Anti-Gaming Measures Phase 2 - -Authors: [Fizzy99](https://github.com/mrfizzy99), [Rendell](https://github.com/RendellD85) -Start Date: 2024-09-05 -Category: Economic, Technical -Original HIP PR: -Tracking Issue: -Voting Requirements: veMOBILE Holders - ---- - -## Summary - -This HIP aims to further the refinement of HIP-131, and will further extend the scope of HIP-131 to cover all remaining areas that were not previously included (such as C** areas), along with other tweaks and changes. - - -## Related Prior HIPs -* [HIP 103: MOBILE Oracle Hex Boosting](./0103-oracle-hex-boosting.md) -* [HIP 118: Verification Mapping for MOBILE Network](./0118-verification-mapping.md) -* [HIP 125: Temporary Anti-Gaming Measures For Boosted Hexes](./0125-temporary-anti-gaming-measures-for-boosted-hexes.md) -* [HIP 131: HIP-131: Bridging Gap Between Verification Mappers and Anti-Gaming Measures](./0131-bridging-gap-between-verification-mappers-and-anti-gaming-measures.md) - - -## Motivation - -While we thought that 'C' footfall areas would be less utilized for gaming activities, we were wrong. Gamers have found refuge in C footfall areas as the first phase of HIP-131 was implemented. Our hopes that making a CDR requirement to activate PoC rewards becomes the norm for all location asserts. - -## Stakeholders -* Deployers: This preserves POI hex rewards for legitimate and active coverage builders. -* Service Providers: This provides a temporary tool to prevent abuse of POI hexes, helping ensure these strategic regions have legitimate coverage and further improve implementation of HIP-118. - - -## Detailed Explanation - -This HIP would enact the following: -- Extend the valid CDR requirement from HIP-131 from only applying to hotspots in Oracle Boosting Multiplier areas (A**, B**), to apply to all areas (A**, B**, and C**). -- Adjust the HIP-131 requirement (A**, B**, and C**) to require a valid CDR every 42 epochs. -- For Boosteed Service Provider locations, a valid CDR will be required every 7 epochs. If an invalid CDR is registered, it will invalidate the valid CDR. This will be left up to the Service provider to quality control what does or does not qualify. -- Extend the duration of HIP-131 (from 150 epochs) to last until both phases of HIP-118 are fully implemented and active. -- Allow HIP-118 (Verification Mapping for MOBILE Network) to utilize CDR information if the Server Provider chooses for all areas, including Service Provider Boosted areas. - - -## Drawbacks - -Having a 42 epoch renewal may be viewed as counterintuitive, but this allows the network to filter out non-utilized hotspots from earning PoC for extended periods of time throughout the hotspot or radios lifetime. - - -## Unresolved Questions - -None. - - -## Implementation - -Nova Labs and Helium Mobile have agreed to the implementation of this proposal, which will be implemented immediately after passing a vote. -Mobile Oracles will report tagging of the hotspots for suspicious activity by the SPs. This off-chain data will record both tagging and untagging activities for the concerned hotspots. This data will be shared in a way that community applications can allow a deployer to understand concerned hotspots have been flagged. -Current SP has indicated they will use their existing support ticket system to manage deployers that feel they have been mistakenly identified as malicious, including an internal escalation procedure to help mitigate support tickets being left unaddressed indefinitely. - -## Success Metrics - -The desired outcome of this HIP is that Oracle Hex Boosted areas are deployed with mobile hotspots that provide high quality, usable cellular coverage for customers of the MOBILE network and attract potential SPs. -Measuring the success of this HIP will require ongoing collaboration with the SP to understand how many mobile hotspots are potentially flagged as malicious through community forums such as the mobile working group community. -Success of this HIP will be measured by the amount of discouragement of illegitimate deployments, and an increase of CDR data in legitimate hotspots. - diff --git a/xxx-bridging-gap-for-anti-gaming-measures-phase2.md b/xxx-bridging-gap-for-anti-gaming-measures-phase2.md new file mode 100644 index 000000000..463781649 --- /dev/null +++ b/xxx-bridging-gap-for-anti-gaming-measures-phase2.md @@ -0,0 +1,62 @@ +# HIP-xxx - Bridging Gap for Anti-Gaming Measures Phase 2 + +* Authors: [Fizzy99](https://github.com/mrfizzy99), [Rendell](https://github.com/RendellD85) +* Start Date: 2024-09-05 +* Category: Economic, Technical +* Original HIP PR: +* Tracking Issue: +* Voting Requirements: veMOBILE Holders + +--- + +## Summary + +This proposal aims to be a further refinement of HIP-131, and will further extend its scope to cover all remaining areas that were not previously included (such as C** areas), along with other tweaks and changes. + +## Related Prior HIPs +* [HIP 103: MOBILE Oracle Hex Boosting](./0103-oracle-hex-boosting.md) +* [HIP 118: Verification Mapping for MOBILE Network](./0118-verification-mapping.md) +* [HIP 125: Temporary Anti-Gaming Measures For Boosted Hexes](./0125-temporary-anti-gaming-measures-for-boosted-hexes.md) +* [HIP 131: Bridging Gap Between Verification Mappers and Anti-Gaming Measures](./0131-bridging-gap-between-verification-mappers-and-anti-gaming-measures.md) + +## Motivation + +While the community thought that 'C' footfall areas would be less utilized for gaming activities, this was wrong, in practice. Gamers have found refuge in C footfall areas as the first phase of HIP-131 was implemented. Eventually, making a CDR requirement to activate Proof-of-Coverage rewards should become the norm for all location assertion but this HIP does not propose to make this change. + +## Stakeholders + +* Deployers: This preserves POI boosted rewards for legitimate and active coverage builders. +* Service Providers: This provides a temporary tool to prevent abuse of POI boosted hexes, helping ensure these strategic regions have legitimate coverage and further improve implementation of HIP-118. + +## Detailed Explanation + +This HIP would enact the following: +- Extend the valid CDR requirement to apply to all areas (A**, B**, and C**) instead of just HIP-131 defined areas (A**, B**). +- Adjust the valid CDR requirement to be once every 42 epochs. +- Require a valid CDR every 7 epochs for Boosted areas. If an invalid CDR is registered, it will invalidate the valid CDR. The Service Provider will be the final determination of qualifying events. +- Extend the implementation period of HIP-131 until both phases of HIP-118 are fully implemented and active (from 150 epochs). +- Allow Verification Mapping (HIP-118) to utilize CDR information for all areas, including Boosted areas. + +## Drawbacks + +Having a 42 epoch renewal may be viewed as counterintuitive, but this allows the network to filter out non-utilized hotspots from earning PoC for extended periods of time throughout the Hotspot's or Radio's lifetime. + +## Unresolved Questions + +None. + +## Implementation + +Nova Labs / Helium Mobile has agreed to the implementation of this proposal, which will begin immediately after a passing vote. A specific timeline on completion has not been communicated. + +Mobile Oracles will report tagging of the Hotspots for suspicious activity by the Service Providers. This off-chain data will record both tagging and untagging activities for the relevant Hotspots. This data will be publicly accessible with other oracle data. + +Nova Labs has indicated they will use their existing support ticket system to manage deployers that feel they have been mistakenly identified as malicious, including an internal escalation procedure to help mitigate support tickets being left unaddressed indefinitely. + +## Success Metrics + +The desired outcome of this proposal is that Boosted areas are deployed with Hotspots that provide high quality, usable cellular coverage for customers of the MOBILE network and attract potential SPs. + +Measuring the success of this proposal will require ongoing collaboration with the Service Providers to understand how many Hotspots are potentially flagged as malicious through community forums such as the Mobile Working Group. + +Success of this proposal will be measured by the amount of discouragement of illegitimate deployments, and an increase of CDR data in legitimate Hotspots. From c6cbb1ed08f41af327d43a3cd256138b1db73be4 Mon Sep 17 00:00:00 2001 From: HIP Editors <93347218+hiptron@users.noreply.github.com> Date: Mon, 7 Oct 2024 21:28:08 -0400 Subject: [PATCH 11/11] Update filename and frontmatter --- ... => 0133-bridging-gap-for-anti-gaming-measures-phase2.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) rename xxx-bridging-gap-for-anti-gaming-measures-phase2.md => 0133-bridging-gap-for-anti-gaming-measures-phase2.md (95%) diff --git a/xxx-bridging-gap-for-anti-gaming-measures-phase2.md b/0133-bridging-gap-for-anti-gaming-measures-phase2.md similarity index 95% rename from xxx-bridging-gap-for-anti-gaming-measures-phase2.md rename to 0133-bridging-gap-for-anti-gaming-measures-phase2.md index 463781649..758ecc1ab 100644 --- a/xxx-bridging-gap-for-anti-gaming-measures-phase2.md +++ b/0133-bridging-gap-for-anti-gaming-measures-phase2.md @@ -1,10 +1,10 @@ -# HIP-xxx - Bridging Gap for Anti-Gaming Measures Phase 2 +# HIP 133: Bridging Gap for Anti-Gaming Measures Phase 2 * Authors: [Fizzy99](https://github.com/mrfizzy99), [Rendell](https://github.com/RendellD85) * Start Date: 2024-09-05 * Category: Economic, Technical -* Original HIP PR: -* Tracking Issue: +* Original HIP PR: [#1087](https://github.com/helium/HIP/pull/1087) +* Tracking Issue: [#1087](https://github.com/helium/HIP/issues/1087) * Voting Requirements: veMOBILE Holders ---