From 03a8500dffec52c2cf73e44df62122ae34892724 Mon Sep 17 00:00:00 2001 From: zer0tweets Date: Mon, 4 Mar 2024 18:03:47 -0800 Subject: [PATCH 1/3] 0XXX-incentive-escrow-fund-for-fubscriber-referrals.md Adding HIP to implement incentive escrow fund for subscriber referrals, per most recent discussion and approval by the mobile working group. --- ...ve-escrow-fund-for-fubscriber-referrals.md | 60 +++++++++++++++++++ 1 file changed, 60 insertions(+) create mode 100644 0XXX-incentive-escrow-fund-for-fubscriber-referrals.md diff --git a/0XXX-incentive-escrow-fund-for-fubscriber-referrals.md b/0XXX-incentive-escrow-fund-for-fubscriber-referrals.md new file mode 100644 index 000000000..111c15be7 --- /dev/null +++ b/0XXX-incentive-escrow-fund-for-fubscriber-referrals.md @@ -0,0 +1,60 @@ +# Incentive Escrow Fund for Subscriber Referrals + +Service Provider rewards will be used to programmatically issues various incentives (like referral fees) to grow Helium network subscriber base + +## Motivation + +Helium Network utility is a function of the number of subscribers sending paid data to the network. I.e. we want more subscribers. Per HIP53, service provider rewards bucket was originally designed to empower service providers to bring more subscribers to the network using token incentives. +Today, the service provider bucket is mostly unused. Some rewards go to Helium Mobile for the traffic, but 90%+ of it is just never emitted + +We propose a referral incentive program that would channel rewards to the community referring users that take advantage of un-emitted MOBILE in the service provider bucket + +## Stakeholders + +- Service Provider +- Builders +- Subscribers + +## Detailed Explanation + +- Service providers get the ability to delegate a percentage of their rewards towards a programmatic “incentive escrow fund” + +- It is up to the service provider to define and change the percentage at any time. I.e. Helium Mobile can start delegating 50%, keep it for 1 month and then change delegation percentage to 0 + +- Any funds delegated towards the incentive escrow fund are matched pro-rata up to 100% by un-used programmatic emissions from the service provider bucket. I.e. if there are plenty of un-emitted funds in the 10% service provider bucket and Helium Mobile chose to start delegating up to 50% of it’s rewards towards referral incentive escrow (roughly $1K/day in MOBILE), total of $2K/day in MOBILE will be deposited into the escrow + +- Incentive escrow fund is specific to a service provider and multiple funds can exist for different service providers. I.e. Helium Mobile can run its own, Telefonica (when and if approved as an SP) can run its own + +- Service providers can define and run various incentive programs that would reward the community for growing subscribers, using MOBILE delegated into the incentive escrow fund + +- MOBILE in the escrow fund cannot be used for anything other than programmatic incentive programs aimed at new subscriber acquisitions (i.e. referrals or “new subscriber” bonus rewards) + +- Any MOBILE that has not been used by the referral program for a period of 12 calendar months from the moment of the original deposit into the fund is burned + +### Example Incentive Program Proposed by Helium Mobile + +Hotspot owners are incentivized to refer subscribers to the network. Each hotspot is able to generate a referral code, unique to that hotspot. For each successful and qualified subscriber that registered for the network and used said referral code, hotspot owner earns $10 in MOBILE immediately, then another $20 in MOBILE over 5 months, provided the subscriber is still active and in good standing. The gradual reward payout promotes subscriber retention and ensures a higher-quality subscriber base (an anti-gaming mechanism). Referrals are paid out of the incentive escrow fund. + +## Drawbacks + +This proposal introduces an additional layer of complexity to the already complex reward mechanism. + +It may also be argued that allowing service providers the freedom to define the structure of a referral program is prone to gaming. Poorly designed and implemented referral schemes could result in exploits where referral payouts for fake users. + +Finally, since this proposal does require that incentive programs launched by service providers require that referred subscribers send data to the Helium Network, service providers will be using “network’s emissions” to attract subscribers that will bring revenue to the service provider, but not the network. + +## Rationale and Alternatives + +An alternative would be for service providers to pay token rewards directly to network participants vs. using an incentive escrow fund. Depending on the regulatory framework governing crypto in the country where the service provider is domiciled this may involve varying levels of regulatory / compliance risk. + +## Unresolved Questions + +Do we need to implement a gating mechanism, such that referral payouts coming from the incentive escrow fund require that any referred user actually used data on the Helium network vs. just becoming a subscriber with one of the network approved service providers. + +## Deployment Impact + +Nova Labs will collaborate with the foundation engineering team to develop detailed architecture and roadmap. + +## Success Metrics + +This HIP would be considered successful if a referral program launched by at least one service provider resulted in at least 50,000 new network subscribers/users sending at least 6TB of paid data to the network per day. From ccf1a7d7afa7a9c0e9947b87bb578b2b54ebf681 Mon Sep 17 00:00:00 2001 From: zer0tweets Date: Tue, 12 Mar 2024 15:41:26 -0700 Subject: [PATCH 2/3] Update and rename 0XXX-incentive-escrow-fund-for-subscriber-referrals.md to 0XXX-incentive-escrow-fund-for-subscriber-referrals.md Updating missing parts per Abhay's suggestions --- ...ncentive-escrow-fund-for-subscriber-referrals.md | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) rename 0XXX-incentive-escrow-fund-for-fubscriber-referrals.md => 0XXX-incentive-escrow-fund-for-subscriber-referrals.md (90%) diff --git a/0XXX-incentive-escrow-fund-for-fubscriber-referrals.md b/0XXX-incentive-escrow-fund-for-subscriber-referrals.md similarity index 90% rename from 0XXX-incentive-escrow-fund-for-fubscriber-referrals.md rename to 0XXX-incentive-escrow-fund-for-subscriber-referrals.md index 111c15be7..6c6fc87fe 100644 --- a/0XXX-incentive-escrow-fund-for-fubscriber-referrals.md +++ b/0XXX-incentive-escrow-fund-for-subscriber-referrals.md @@ -1,5 +1,12 @@ # Incentive Escrow Fund for Subscriber Referrals +- Author(s): @zer0tweets +- Start Date: 2024-03-12 +- Category: Economic, Technical +- Original HIP PR: +- Tracking Issue: +- Vote Requirements: veMOBILE Holders + Service Provider rewards will be used to programmatically issues various incentives (like referral fees) to grow Helium network subscriber base ## Motivation @@ -11,9 +18,9 @@ We propose a referral incentive program that would channel rewards to the commun ## Stakeholders -- Service Provider -- Builders -- Subscribers +- Service Providers will have a new capability to create referral incentive programs using unused rewards from service provider bucket +- Builders will be able to earn MOBILE rewards for referring subscribres +- Subscribers may be eligible for "referral discounts" in the form of MOBILE, if they stay with the network for a period of time ## Detailed Explanation From 3b5eaec535015ed0e415d5e98912bf9cafeb1a17 Mon Sep 17 00:00:00 2001 From: HIP Editors <93347218+hiptron@users.noreply.github.com> Date: Wed, 13 Mar 2024 12:44:52 -0400 Subject: [PATCH 3/3] Number and update frontmatter --- ...centive-escrow-fund-for-subscriber-referrals.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) rename 0XXX-incentive-escrow-fund-for-subscriber-referrals.md => 0114-incentive-escrow-fund-for-subscriber-referrals.md (94%) diff --git a/0XXX-incentive-escrow-fund-for-subscriber-referrals.md b/0114-incentive-escrow-fund-for-subscriber-referrals.md similarity index 94% rename from 0XXX-incentive-escrow-fund-for-subscriber-referrals.md rename to 0114-incentive-escrow-fund-for-subscriber-referrals.md index 6c6fc87fe..699af21fc 100644 --- a/0XXX-incentive-escrow-fund-for-subscriber-referrals.md +++ b/0114-incentive-escrow-fund-for-subscriber-referrals.md @@ -1,13 +1,17 @@ -# Incentive Escrow Fund for Subscriber Referrals +# HIP 114: Incentive Escrow Fund for Subscriber Referrals -- Author(s): @zer0tweets +- Author: [@zer0tweets](https://github.com/zer0tweets) - Start Date: 2024-03-12 - Category: Economic, Technical -- Original HIP PR: -- Tracking Issue: +- Original HIP PR: [#927](https://github.com/helium/HIP/pull/927) +- Tracking Issue: [#942](https://github.com/helium/HIP/issues/942) - Vote Requirements: veMOBILE Holders -Service Provider rewards will be used to programmatically issues various incentives (like referral fees) to grow Helium network subscriber base +--- + +## Summary + +Service Provider rewards will be used to programmatically issues various incentives (like referral fees) to grow Helium network subscriber base. ## Motivation