Skip to content

Update governance.md with post HIP 138/141 updates #1971

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.

Sign up for GitHub

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

Open
wants to merge 9 commits into
base: master
Choose a base branch
from
Open

Update governance.md with post HIP 138/141 updates #1971

Changes from all commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
4dc0b43
Update governance.mdx
waveform06 Mar 5, 2025
23772e2
Update docs/governance/governance.mdx
waveform06 May 9, 2025
5d5d391
Update docs/governance/governance.mdx
waveform06 May 9, 2025
62c4866
Update docs/governance/governance.mdx
waveform06 May 9, 2025
aeb7100
Update docs/governance/governance.mdx
waveform06 May 9, 2025
e67b230
Update docs/governance/governance.mdx
waveform06 May 9, 2025
44656f1
Update docs/governance/governance.mdx
waveform06 May 11, 2025
d509802
Update docs/governance/governance.mdx
waveform06 May 11, 2025
0934b63
Update docs/governance/governance.mdx
waveform06 May 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
51 changes: 27 additions & 24 deletions docs/governance/governance.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <u>Helium network as a whole</u>.
1. Locking IOT enables voting on HIPs governing the <u>IoT subnetwork</u>.
1. Locking MOBILE enables voting on HIPs governing the <u>mobile subnetwork</u>.
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. The Helium Community
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can drop the "Since the implementation of HIP-141..." and focus on the current implementation.

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
(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.
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
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.

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.
Expand All @@ -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](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
governance-related matters.
Expand Down