From 4dc0b4338c22fdaa76092c1e122e507e6f37fafd Mon Sep 17 00:00:00 2001 From: Adrian <44499545+waveform06@users.noreply.github.com> Date: Wed, 5 Mar 2025 14:02:36 +0000 Subject: [PATCH 1/9] Update governance.mdx --- docs/governance/governance.mdx | 51 ++++++++++++++++++---------------- 1 file changed, 27 insertions(+), 24 deletions(-) diff --git a/docs/governance/governance.mdx b/docs/governance/governance.mdx index a253ded24..ba2e70da8 100644 --- a/docs/governance/governance.mdx +++ b/docs/governance/governance.mdx @@ -17,31 +17,34 @@ import { TopLedgerEmbed } from '@site/src/theme/TopLedgerEmbed' Helium governance exists to manage the process by which the network can be modified, whether in its technical architecture, the token's economic model, or meta-governance changes. It is governed by -the global community of owners of Helium tokens ([HNT](/tokens/hnt-token), -[MOBILE](/tokens/mobile-token), or [IOT](/tokens/iot-token)). These token owners include Hotspot -deployers, network users, wireless network operators, hardware manufacturers, and more. Tokens must -be locked for voting on network changes, ensuring long-term stakeholder alignment. - -Anyone can submit a Helium Improvement Proposal ([HIP](/governance/hip)) as a first step to -modifying the network. All HIPs are published in the public Helium GitHub repository, then discussed -and debated in public forums, including the Helium community Discord server, and on monthly -community calls. Any Helium token owner is eligible to vote on HIPs within the domain of that -specific token. To vote, a Helium token owner must first lock their tokens for a period of time, up -to four years, which grants the owner voting power determined by the number of locked tokens and the -lock duration. - -As Helium is a network of networks, there are currently three different jurisdictions for -governance: - -1. Locking HNT allows for voting on HIPs governing the Helium network as a whole. -1. Locking IOT enables voting on HIPs governing the IoT subnetwork. -1. Locking MOBILE enables voting on HIPs governing the mobile subnetwork. +the global community of owners of Helium ([HNT](/tokens/hnt-token) tokens. + +These token owners include Hotspot deployers, network users, wireless network operators, hardware +manufacturers, network mappers and more. Tokens must be locked for voting on network changes, ensuring +long-term stakeholder alignment. + + +Since the implementation of [HIP-141](https://github.com/helium/HIP/blob/main/0141-single-token-governance-and-release-proposals.md#votes-with-code) the governance process has changed. In the future the Helium Community +will vote with veHNT on a periodic basis (initially monthly) to approve upcoming protocol upgrades proposed +by the Protocol Developers. This evolution of the HIP process may be characterized as a Helium Release Process +(HPR). + +All changes under this process must come with audited and deployable code. Each Release Vote will be inititalised +at the existing Helium Monthly [Community Call](https://helium.foundation/community-call), and will apply to new code deployed across the Helium network. +Emergency or security-related deployments that are necessary for protocol safety, as well as bug fixes, may be +deployed on an ad-hoc basis, but must be announced and ratified through subsequent Release Votes. + +Anyone can submit a Github PR to the latest [HRP](https://github.com/helium/helium-release-proposals) before +the community call but must submit such requests with completed and audited code for the implementation request. + +Helium is a network of networks, all managed with one token for governance. Locking HNT allows for voting on +governance of the top level Helium network and the subnetworks of IOT and MOBILE with a single token. The Helium Foundation serves as a steward for the governance process. The Foundation established the initial framework and manages the open Helium GitHub repositories. The Foundation does not vote on -HIPs but does vet proposals for compliance with the law and technical feasibility. The Foundation's -role is to provide expert advice and guidance and to guide implementation of the HIPs after they -have passed. +changes but does vet proposals for compliance with the law and technical feasibility. The Foundation's +role is to provide expert advice and guidance and to guide implementation of the results of votes after +they have passed. Information about governance is subject to change as the Helium Network constantly evolves. It is led by the open-source community that continues to build it. @@ -67,8 +70,8 @@ links and resources. 1. **Discord**: The [Helium Discord](https://discord.gg/helium) platform serves as the primary communication channel for the Helium Network Community. It offers real-time discussions, support, and engagement opportunities. -2. **GitHub Repository**: The [HIP GitHub](https://github.com/helium/HIP) repository provides access - to the Helium Improvement Proposals and related discussions. +2. **GitHub Repository**: The [HRP GitHub](https://github.com/helium/helium-release-proposals) repository and previous [HIP GitHub](https://github.com/helium/HIP) repository provides access + to the Helium Release Proposals, Helium Improvement Proposals and related discussions. 3. **Social Media and Ecosystem Voices**: The Helium Foundation and various influencers on platforms like Twitter, Discord, and YouTube provide updates, debates, and explanations of HIPs and governance-related matters. From 23772e259353d90d4bb1d3a3fb819a2efa12ab3f Mon Sep 17 00:00:00 2001 From: Adrian <44499545+waveform06@users.noreply.github.com> Date: Fri, 9 May 2025 22:42:19 +0100 Subject: [PATCH 2/9] Update docs/governance/governance.mdx Co-authored-by: Abhay Kumar <75+abhay@users.noreply.github.com> --- docs/governance/governance.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/governance/governance.mdx b/docs/governance/governance.mdx index ba2e70da8..d3a4f2ea0 100644 --- a/docs/governance/governance.mdx +++ b/docs/governance/governance.mdx @@ -32,7 +32,7 @@ by the Protocol Developers. This evolution of the HIP process may be characteriz All changes under this process must come with audited and deployable code. Each Release Vote will be inititalised at the existing Helium Monthly [Community Call](https://helium.foundation/community-call), and will apply to new code deployed across the Helium network. Emergency or security-related deployments that are necessary for protocol safety, as well as bug fixes, may be -deployed on an ad-hoc basis, but must be announced and ratified through subsequent Release Votes. +deployed on an ad-hoc basis, but must be announced and ratified through subsequent votes. Anyone can submit a Github PR to the latest [HRP](https://github.com/helium/helium-release-proposals) before the community call but must submit such requests with completed and audited code for the implementation request. From 5d5d391636d0614f96fe4f8c388bc8d4c8948162 Mon Sep 17 00:00:00 2001 From: Adrian <44499545+waveform06@users.noreply.github.com> Date: Fri, 9 May 2025 22:42:33 +0100 Subject: [PATCH 3/9] Update docs/governance/governance.mdx Co-authored-by: Abhay Kumar <75+abhay@users.noreply.github.com> --- docs/governance/governance.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/governance/governance.mdx b/docs/governance/governance.mdx index d3a4f2ea0..88fe7dc34 100644 --- a/docs/governance/governance.mdx +++ b/docs/governance/governance.mdx @@ -24,7 +24,7 @@ manufacturers, network mappers and more. Tokens must be locked for voting on net long-term stakeholder alignment. -Since the implementation of [HIP-141](https://github.com/helium/HIP/blob/main/0141-single-token-governance-and-release-proposals.md#votes-with-code) the governance process has changed. In the future the Helium Community +Since the implementation of [HIP-141](https://github.com/helium/HIP/blob/main/0141-single-token-governance-and-release-proposals.md#votes-with-code) the governance process has changed. The Helium Community will vote with veHNT on a periodic basis (initially monthly) to approve upcoming protocol upgrades proposed by the Protocol Developers. This evolution of the HIP process may be characterized as a Helium Release Process (HPR). From 62c4866a730a628c22f9db9e710de0beb798e5e9 Mon Sep 17 00:00:00 2001 From: Adrian <44499545+waveform06@users.noreply.github.com> Date: Fri, 9 May 2025 22:42:47 +0100 Subject: [PATCH 4/9] Update docs/governance/governance.mdx Co-authored-by: Abhay Kumar <75+abhay@users.noreply.github.com> --- docs/governance/governance.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/governance/governance.mdx b/docs/governance/governance.mdx index 88fe7dc34..2c8d886c0 100644 --- a/docs/governance/governance.mdx +++ b/docs/governance/governance.mdx @@ -29,7 +29,7 @@ will vote with veHNT on a periodic basis (initially monthly) to approve upcoming by the Protocol Developers. This evolution of the HIP process may be characterized as a Helium Release Process (HPR). -All changes under this process must come with audited and deployable code. Each Release Vote will be inititalised +All changes under this process must come with audited and deployable code. Each release vote will be initialized at the existing Helium Monthly [Community Call](https://helium.foundation/community-call), and will apply to new code deployed across the Helium network. Emergency or security-related deployments that are necessary for protocol safety, as well as bug fixes, may be deployed on an ad-hoc basis, but must be announced and ratified through subsequent votes. From aeb71008d3cbbcbbc32ab682a92a5b6dfd4c5496 Mon Sep 17 00:00:00 2001 From: Adrian <44499545+waveform06@users.noreply.github.com> Date: Fri, 9 May 2025 22:42:58 +0100 Subject: [PATCH 5/9] Update docs/governance/governance.mdx Co-authored-by: Abhay Kumar <75+abhay@users.noreply.github.com> --- docs/governance/governance.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/governance/governance.mdx b/docs/governance/governance.mdx index 2c8d886c0..740202041 100644 --- a/docs/governance/governance.mdx +++ b/docs/governance/governance.mdx @@ -38,7 +38,7 @@ Anyone can submit a Github PR to the latest [HRP](https://github.com/helium/heli the community call but must submit such requests with completed and audited code for the implementation request. Helium is a network of networks, all managed with one token for governance. Locking HNT allows for voting on -governance of the top level Helium network and the subnetworks of IOT and MOBILE with a single token. +governance of the top level Helium network and the subnetworks of IoT and Mobile with a single token. The Helium Foundation serves as a steward for the governance process. The Foundation established the initial framework and manages the open Helium GitHub repositories. The Foundation does not vote on From e67b2309bd670bd98e66adc0e1c9db92f612c62a Mon Sep 17 00:00:00 2001 From: Adrian <44499545+waveform06@users.noreply.github.com> Date: Fri, 9 May 2025 22:43:18 +0100 Subject: [PATCH 6/9] Update docs/governance/governance.mdx Co-authored-by: Abhay Kumar <75+abhay@users.noreply.github.com> --- docs/governance/governance.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/governance/governance.mdx b/docs/governance/governance.mdx index 740202041..9e72499f0 100644 --- a/docs/governance/governance.mdx +++ b/docs/governance/governance.mdx @@ -70,7 +70,7 @@ links and resources. 1. **Discord**: The [Helium Discord](https://discord.gg/helium) platform serves as the primary communication channel for the Helium Network Community. It offers real-time discussions, support, and engagement opportunities. -2. **GitHub Repository**: The [HRP GitHub](https://github.com/helium/helium-release-proposals) repository and previous [HIP GitHub](https://github.com/helium/HIP) repository provides access +2. **GitHub Repository**: The [HRP](https://github.com/helium/helium-release-proposals) repository and [HIP](https://github.com/helium/HIP) repository provides access to the Helium Release Proposals, Helium Improvement Proposals and related discussions. 3. **Social Media and Ecosystem Voices**: The Helium Foundation and various influencers on platforms like Twitter, Discord, and YouTube provide updates, debates, and explanations of HIPs and From 44656f1d71744d634ecced5bf92037236df2f7b5 Mon Sep 17 00:00:00 2001 From: Adrian <44499545+waveform06@users.noreply.github.com> Date: Sun, 11 May 2025 20:07:41 +0100 Subject: [PATCH 7/9] Update docs/governance/governance.mdx Co-authored-by: Abhay Kumar <75+abhay@users.noreply.github.com> --- docs/governance/governance.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/governance/governance.mdx b/docs/governance/governance.mdx index 9e72499f0..ab3a98d4f 100644 --- a/docs/governance/governance.mdx +++ b/docs/governance/governance.mdx @@ -27,7 +27,7 @@ long-term stakeholder alignment. Since the implementation of [HIP-141](https://github.com/helium/HIP/blob/main/0141-single-token-governance-and-release-proposals.md#votes-with-code) the governance process has changed. The Helium Community will vote with veHNT on a periodic basis (initially monthly) to approve upcoming protocol upgrades proposed by the Protocol Developers. This evolution of the HIP process may be characterized as a Helium Release Process -(HPR). +(HRP). All changes under this process must come with audited and deployable code. Each release vote will be initialized at the existing Helium Monthly [Community Call](https://helium.foundation/community-call), and will apply to new code deployed across the Helium network. From d509802202ed2cb8db290bb95e7525abff46f95b Mon Sep 17 00:00:00 2001 From: Adrian <44499545+waveform06@users.noreply.github.com> Date: Sun, 11 May 2025 20:07:56 +0100 Subject: [PATCH 8/9] Update docs/governance/governance.mdx Co-authored-by: Joey Hiller <1965053+jthiller@users.noreply.github.com> --- docs/governance/governance.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/governance/governance.mdx b/docs/governance/governance.mdx index ab3a98d4f..d45248642 100644 --- a/docs/governance/governance.mdx +++ b/docs/governance/governance.mdx @@ -34,7 +34,7 @@ at the existing Helium Monthly [Community Call](https://helium.foundation/commun Emergency or security-related deployments that are necessary for protocol safety, as well as bug fixes, may be deployed on an ad-hoc basis, but must be announced and ratified through subsequent votes. -Anyone can submit a Github PR to the latest [HRP](https://github.com/helium/helium-release-proposals) before +Anyone can submit a GitHub PR to the latest [HRP](https://github.com/helium/helium-release-proposals) before the community call but must submit such requests with completed and audited code for the implementation request. Helium is a network of networks, all managed with one token for governance. Locking HNT allows for voting on From 0934b63301fb1f9d50389a7173ac89c4035503cb Mon Sep 17 00:00:00 2001 From: Adrian <44499545+waveform06@users.noreply.github.com> Date: Sun, 11 May 2025 20:08:10 +0100 Subject: [PATCH 9/9] Update docs/governance/governance.mdx Co-authored-by: Joey Hiller <1965053+jthiller@users.noreply.github.com> --- docs/governance/governance.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/governance/governance.mdx b/docs/governance/governance.mdx index d45248642..15897fa84 100644 --- a/docs/governance/governance.mdx +++ b/docs/governance/governance.mdx @@ -38,7 +38,7 @@ Anyone can submit a GitHub PR to the latest [HRP](https://github.com/helium/heli the community call but must submit such requests with completed and audited code for the implementation request. Helium is a network of networks, all managed with one token for governance. Locking HNT allows for voting on -governance of the top level Helium network and the subnetworks of IoT and Mobile with a single token. +governance of the top level Helium network and the subnetworks of IoT and Mobile. The Helium Foundation serves as a steward for the governance process. The Foundation established the initial framework and manages the open Helium GitHub repositories. The Foundation does not vote on