HRP Vote Open Skill

You help start the community vote for a Helium Release Proposal by creating the vote summary gist, opening a PR against helium/helium-vote, and updating the HRP status.

Prerequisites

• The HRP must have status: Proposed (with features for a normal vote, or without features for a no-change proxy vote)
• hiptron GitHub token must be configured — if missing, gh-hiptron.sh will print setup instructions
• The user must be ready to finalize — once voting opens, the HRP content is frozen

GitHub commands

All GitHub API commands (gists, PRs, pushes) run as the hiptron user via the wrapper script:

${CLAUDE_PLUGIN_ROOT}/scripts/gh-hiptron.sh

Use this instead of bare gh for every GitHub operation in this skill.

Steps

1. Identify the target HRP

• Find the active HRP (status: Proposed, upcoming vote-date) or use the month the user specifies
• Read the full release file
• If the HRP has no features, confirm: "This is a no-change release — open a proxy vote for HRP {Month Year}?" Use the no-change template in step 2.
• Otherwise, confirm: "Ready to open voting for HRP {Month Year}? The HRP content will be frozen from this point forward."

2. Generate the vote summary

Create a markdown document summarizing the HRP for voters. This is what voters see on heliumvote.com. The format is concise — just a summary paragraph, the feature list, and boilerplate sections.

Template for releases with features:

# Helium Release Proposal: {YYYY-MM}

## Summary
This proposal defines the {Month Year} Helium release that will be deployed after a successful outcome of this vote. The linked release notes have context and explicit details on implementation.

- Authors: Helium Core Developers
- Full release note text: [{YYYY-MM}](https://github.com/helium/helium-release-proposals/blob/main/releases/{filename})

## Roadmap Features
{numbered list of feature names — just the names, no descriptions}

## Approval Requirements

* This HRP is considered approved if 67% of the voting power is reached.
* This HRP must reach the quorum of 100,000,000 veHNT to be considered valid.

***

## Governance

Helium Network governance is discussed in the community [Discord](https://discord.gg/helium). Governance related updates are shared in the monthly newsletter, monthly community calls, and quarterly tokenholder updates.

Template for no-change releases:

# Helium Release Proposal: {YYYY-MM} - No Changes

## Summary
This proposal defines the {Month Year} Helium release which contains no changes to the Helium protocol. There will be no planned deployment this month but this vote is a placeholder to allow proxies to continue to provide an active vote status.

## Roadmap Features
"There will be no protocol updates in the {Month Year} Release."

## Approval Requirements

* This HRP is considered approved if 67% of the voting power is reached.
* This HRP must reach the quorum of 100,000,000 veHNT to be considered valid.

***

## Governance

Helium Network governance is discussed in the community [Discord](https://discord.gg/helium). Governance related updates are shared in the monthly newsletter, monthly community calls, and quarterly tokenholder updates.

Concrete example — here's what the April 2026 vote summary would look like:

# Helium Release Proposal: 2026-04

## Summary
This proposal defines the April 2026 Helium release that will be deployed after a successful outcome of this vote. The linked release notes have context and explicit details on implementation.

- Authors: Helium Core Developers
- Full release note text: [2026-04](https://github.com/helium/helium-release-proposals/blob/main/releases/20260401-core-devs.md)

## Roadmap Features
1. Staked HNT Position Transfers

## Approval Requirements

* This HRP is considered approved if 67% of the voting power is reached.
* This HRP must reach the quorum of 100,000,000 veHNT to be considered valid.

***

## Governance

Helium Network governance is discussed in the community [Discord](https://discord.gg/helium). Governance related updates are shared in the monthly newsletter, monthly community calls, and quarterly tokenholder updates.

Show the generated summary to the user for confirmation before creating the gist.

3. Create the gist

Create a public gist with the vote summary:

# Write the summary to a temp file first, then pass it positionally
"${CLAUDE_PLUGIN_ROOT}/scripts/gh-hiptron.sh" gist create --public --desc "HRP {YYYY-MM} Vote Summary" /tmp/HRP-{YYYY-MM}-Vote-Summary.md

Note the raw URL of the gist — you'll need it for the proposal entry.

4. Open PR against helium/helium-vote

Use the vote-pr.sh script — it handles everything via the GitHub API as hiptron (no local clone needed):

"${CLAUDE_PLUGIN_ROOT}/scripts/vote-pr.sh" \
  --month "{YYYY-MM}" \
  --gist-url "{raw gist URL}" \
  --hrp-file "releases/{filename}"

The script fetches helium-proposals.json, appends the vote entry, creates a branch, commits, and opens the PR. It prints the PR URL on success.

Note the PR URL from the output.

5. Update the HRP frontmatter

Add tracking fields and update status:

• status: Frozen
• vote-summary-url: {raw gist URL}
• vote-pr: {PR URL or helium/helium-vote#NN}

Commit this change directly to main with message: Freeze HRP {Month Year} for voting

Note: the HRP is frozen immediately even though the helium-vote PR hasn't been merged yet. This signals to contributors that content is locked. If the vote PR is later rejected or the multisig doesn't sign, run /hrp:vote-close with the cancelled option to revert to Proposed.

6. Report

Tell the user:

• Gist created (with URL)
• PR opened against helium/helium-vote (with URL)
• HRP status updated to Frozen
• Next step: a maintainer reviews and merges the vote PR, then the multisig signers approve the on-chain proposal
• When the vote goes live, come back and say "the vote is live" to record the vote-live-date and vote-url (step 7)

7. Record vote-live-date and vote-url (when user returns)

This step runs later — when the user says "the vote is live" or "the multisig signed."

Look up the vote URL from the on-chain proposal:

"${CLAUDE_PLUGIN_ROOT}/scripts/lookup-vote-url.sh" --month "{YYYY-MM}"

This returns JSON with url and publicKey. If the script fails (proposal not yet on-chain), ask the user to try again later or provide the URL manually.

Update the HRP frontmatter:

• vote-live-date: {today's date, YYYY-MM-DD}
• vote-url: {heliumvote.com URL from lookup}

Commit to main with message: Record vote-live-date for HRP {Month Year}