Skip to content

Latest commit

 

History

History
105 lines (76 loc) · 5.48 KB

0068-open-service-subdao.md

File metadata and controls

105 lines (76 loc) · 5.48 KB
Raw

HIP-68: Open Service Subdao

  • Author(s): @sndnsos @haihongS
  • Start Date: 2022/07/23
  • Category: Economic, Technical
  • Original HIP PR: #454
  • Tracking Issue: #457

Summary

HIP-51: Helium DAO proposed that each communications network built on top of the Helium Network has its own subDAO with its own token and governance. Till now, LoRaWAN subDAO, 5G subDAO, and WiFi subDAO are proposed. They are about communication networks. But another very significant subDAO that should be a next step, is to help build the service market on Helium Network.

For the services on CDN and VPN for example, there would be lots of projects that want to use Helium's Network to help run various services. We think for many Heliums nodes, their bandwidth resources, storage spaces, device performance, and all other idle resources, should be more fully taken used now and in the future.

So here we suggest Helium start an open service list for the projects who have the requirement to use Helium Network. The services which could join the open list need to follow some standards made by the community; And for the nodes of the helium network, they could choose to run any services in the list as their wish, getting extra motivation rewards in return.

We suggest starting the Open-Service subDAO under Helium Network which plays some open and special roles, building a services-supporting market in Helium Network.

Background

Helium is growing to have its first million nodes soon, it aims to help different communication networks build on Helium Network including LoRaWAN, Wifi, 5G, CDN, and VPN.

On the one hand, Comparatively, for a miner to join Helium is pretty easy, while it would be kind of difficult for more services to use this global distributed network. Even though the requirement for data delivery is growing fast every year and surely will grow much larger in the future, the traditional market is still not good enough for various projects to deploy their services globally, not to mention to use a cheaper but high-quality decentralized network. On the other hand, Many Helium nodes are used for IoT currently and will help the Cellular Network the most in the future, while the bandwidth/space/performance of many helium nodes are still not made fully used f for more different applications.

This proposal is trying to come up with a win-win solution, or probably a revolution to help optimize the network structure or even market structure to start this Open Service subDao.

Explanation

  • What is the service list?

    The service list is for multiple services to easily join/use Helium Network. The Helium node owner could pick any services in the list, and install/uninstall the services. The project side needs to pay the Data Credits to use the services provided by Helium nodes.

  • For the project side, how to join the list?

    The project side should inform the usage scenarios, the resource it consumes, and publish the source codes, finishing the process to guarantee its security. The subDAO committee will examine and approve/reject the application.

  • For the helium node owners, what do they need to do?

    There need to update the service list, and be able to choose any services to install anytime, also be able to quit the services anytime.

SubDao Governance

Helium node owners and projects which wish to run their services on Helium Network are going to run this SubDao together.

A committee is imperative to form to design an economic model and set specifications and approve projects which are qualified to use Helium Network.

Also, an evaluation system is a pretty meaningful job to give enough references for the Helium node owners to choose the best services for their interests to run.

The project side should purchase Data Credits to pay for the service expense, purchasing and burning HNT to help run the entire Helium Ecosystem. Most of the service fee would go to the node's owner directly, while a very tiny percentage of the service fee is gonna be used to help build and support the running of the committee.

Launch

Meson Network would like to be one of the start projects to launch the service list. As a bandwidth trading platform and the biggest web3 CDN supplier, Meson Network makes use of idle bandwidth resources to help distribute files/data around the world. The globally distributed Helium nodes could help Meson Newtowk to deliver the different kinds of files/data, and get the service fee in return for how much it contributes.

Meson Network is going to draft and finish the application form, proposing the charging standard form, giving the Helium Nodes a choice to share their bandwidth/space to install the Meson service. The team of Meson Network will help the different kinds of Helium to deploy Meson. They could install the patch to share some resources to help Meson Network, and quit anytime as their wish.

Deployment Impact

  • Make Helium Network more commonly used for multiple purposes.
  • Help the Helium node owners get more rewards.
  • Build a network service trading platform and help the development and growth of the Internet, reducing the cost and improving the performance with the tremendous Helium nodes around the world

Unresolved Questions

  • Is it a better choice to get an open service list? Or for each project to join to create an independent subDAO like Meson subDAO?