• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
HELPHELPby0xb0D31186A39712f15495E77bfca8417603b3748Fenrique.dezentrust.eth

[HGP-01] Migration to HELP V2: Scaling infrastructure and aligning governance

Voting ended 27 days agoSucceeded

TL;DR

We are proposing to migrate HELP from the current V1 token to a new V2 token. The goal is to make HELP easier to understand, more trustless, and ready for institutional-grade partnerships. V2 replaces a pausable and conceptually confusing contract with a clean design: a strict 1,000,000 HELP hard cap, no pause mechanism, and a transparent emission schedule controlled by a Safe + OpenZeppelin Governor DAO.

Current V1 holders are not diluted; they are upgraded. Eligible holders will receive 2.5x their current balance in HELP V2: 40% available immediately and 60% unlocked through a 10-month linear vesting.


Why HELP V1 cannot remain our main token

HELP V1 served as our initial proof of concept, but it carries technical debt that hinders our long-term vision:

  • Confusing cap: V1 has a 10,000,000 HELP theoretical cap but only 400,000 HELP is practically reachable. This confuses aggregators and potential partners.
  • Centralization risks: The V1 contract is pausable by a manager role. While necessary in early stages, this is a red flag for exchanges and decentralized protocols.
  • Inflexible infrastructure: V1 wasn't built to be natively governed by a modern DAO stack, making automated, transparent emissions difficult to implement.

What HELP V2 changes

  1. Immutable hard cap: A fixed 1,000,000 HELP supply. No hidden minting functions, no ambiguity.
  2. No pause mechanism: Once deployed, the token is unstoppable. This ensures HELP behaves as a standard, reliable asset.
  3. Standardized governance: We are moving to a Gnosis Safe + OpenZeppelin Governor architecture. This is the gold standard for on-chain governance, ensuring that the DAO's decisions are executed through audited, industry-standard smart contracts.
  4. Fair upgrade: To account for the new supply structure, eligible V1 holders receive 2.5x their balance.
    • 40% upfront: Immediate liquidity at launch.
    • 60% vesting: Linear release over 10 months to ensure long-term alignment.

Strategic allocations and emissions

  • DAO treasury: Approx. 550,000 HELP controlled by the Safe + Governor. These funds are reserved for dataset building and core protocol growth through a decay-based emission schedule.
  • Team & OTC: Legacy allocations are replaced by a cleaner 125k Team and 125k OTC bucket, both subject to 10-month linear vesting. We are explicitly excluding internal team streams from the 2.5x upgrade to prioritize community holders.
  • Liquidity: We will seed a new V2 liquidity pool on Uniswap with approximately 10,000 HELP, allowing for organic price discovery and community-led liquidity provision.

Implementation & timeline

To ensure a smooth transition, we will follow a strict technical protocol:

  1. Snapshot: A block-specific snapshot will be taken on Base. We will publish a report with the final eligible supply.
  2. Deployment: Launch of HELP V2 and a dedicated claim UI where holders can verify their balances.
  3. V1 deprecation: HELP V1 will be paused and its liquidity removed from DEXs to prevent any accidental usage.
  4. Claim period: Holders can claim their 40% immediately, while the remaining 60% starts its 10-month linear vesting directly via the UI.
  5. Governance handover: Transfer of contract ownership to the Safe + Governor module before the cliff ends, ensuring full DAO control.

Documentation

For a detailed technical breakdown, see the full proposal document: HELP V2 Migration


What this vote decides

By voting YES, you explicitly authorize:

  1. The migration to the V2 contract on Base with a 1M HELP hard cap.
  2. The 2.5x upgrade for eligible holders (including the 10-month vesting structure).
  3. The deprecation of V1 as the canonical token.
  4. The transition to a decentralized governance model managed by Safe + OpenZeppelin Governor.

By voting NO, the project remains on V1, maintaining the current pausable contract, the confusing 10M cap, and the lack of a standardized DAO infrastructure.

Off-Chain Vote

For
13.07K HELP100%
Against
0 HELP0%
Abstain
0 HELP0%
Download mobile app to vote

Discussion

HELP[HGP-01] Migration to HELP V2: Scaling infrastructure and aligning governance

Timeline

Feb 04, 2026Proposal created
Feb 09, 2026Proposal vote started
Feb 23, 2026Proposal vote ended
Feb 23, 2026Proposal updated