-
Notifications
You must be signed in to change notification settings - Fork 408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HIP 68: Open Service Subdao #457
Comments
On the Meson Discord, I found someone posting a link to this blog post: https://nijatoes.com/posts/can-open-service-subdaos-bring-back-heliums-glory-days/ |
Great find! This is a great amendment to their HIP. Interested in this part:
I still have questions about how it's even possible to run other services on the device. If a raspberry pi can support it, then I suppose the hotspot can, but am I taking processing power away from PoC? Interested to see them test this on some of the most popular hotspots (like a Bobcat 300) and see if the PoC performance is maintained. |
Regarding the "is it taking away power from PoC": The full hotspots used to act as blockchain nodes - with the transition to light hotspots, the devices neither make full use of their computational power anymore. Nor is the full storage capacity still needed that used to store the blockchain. So there are unused resources on the full hotspots that could be utilized otherwise. No idea what/how much can be done with that though (I am not a dev). |
The authors have instructed us to close at this time. They may review this HIP in the future. |
HIP 68: Open Service Subdao
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.
Rendered View
https://github.com/helium/HIP/blob/main/0068-open-service-subdao.md
The text was updated successfully, but these errors were encountered: