Simple Summary
This proposal determines the allocation of 4,906,847 unclaimed HP coins following the official ERC20 token migration. The community must decide whether to establish a Community Strategic Reserve for long-term ecosystem growth or to permanently burn the idle assets.
## Abstract
The official token migration period from the ERC20-based Hippocrat to the Hippo Protocol has concluded, resulting in an unclaimed balance of approximately 4,906,847 HP. This proposal seeks the community's consensus on how to handle these idle assets. It outlines two distinct paths: redefining the tokens as a "Multi-purpose Strategic Asset for Long-term Ecosystem Growth" to generate sustainable yield, or permanently burning them to ensure a static token economy.
## Motivation
Addressing these idle assets responsibly is critical for the future of the Hippo Protocol. The Foundation strongly advocates for redefining these tokens as a Strategic Reserve rather than simply burning them. Activating these assets provides three core strategic benefits:
1. Bolstering Network Security: Historically, unclaimed tokens have contributed nothing to the network. Staking (delegating) these idle assets to top validators directly strengthens the chain's consensus algorithm.
2. Sustainable Yield: Locking the tokens on-chain eliminates market sell-pressure concerns. The generated Staking Rewards can be used to boost the ecosystem (developer grants, marketing, etc.) without harming the principal.
3. Flexible Strategic Reserve: The Web3 environment evolves rapidly. While staking is crucial for early-stage network stability, this fund acts as a strategic base capable of shifting priorities in the future—such as attracting killer dApps.
## Specification
* Proposal Date: 05/08/2026
* Execution Date: TBD
* Asset Source: Unclaimed HP from Hippocrat ERC20 migration
* Total Amount: ~4,906,847 HP
## Voting Options Breakdown
Option YES: Establish a 'Community Strategic Reserve' (Highly Recommended)
Voting "Yes" means allocating the 4,906,847 HP into a newly formed Community Strategic Reserve. This smart capital deployment generates infinite yield for ecosystem development while strictly minimizing token dilution. To ensure transparency, it operates in distinct phases:
* Phase 1: Strengthening Network Infrastructure (Current Goal)
* 100% of the unclaimed supply will be distributed and staked to reputable validators.
* All generated staking rewards will be accumulated into an 'Ecosystem Grants' pool.
* Phase 2: Multi-purpose Ecosystem Boost (Future Scalability)
* As the ecosystem expands, the community may choose to unstake a portion of the principal for crucial needs like DEX liquidity provisioning or cross-chain bridge deposits.
* Safety Mechanism: Any change in utility or transitioning to Phase 2 strictly requires a separate community governance vote (DAO Approval) before execution.
Option NO: Token Burn
Voting "No" means permanently burning the 4,906,847 unclaimed HP by sending them to an unrecoverable address. This is the simplest method to completely remove potential circulation risk.
* Increased Scarcity: Permanently reduces the total potential supply of coins in the market.
* Inflation Prevention: Eliminates the possibility of these tokens ever entering circulation.
* Enhanced Trust: Provides a clean and immediate resolution to excess supply, demonstrating transparent supply management.
## Rationale
Providing these options gives the community direct control over the protocol's economic framework. While a burn ensures absolute scarcity, the Foundation strongly believes that Option YES provides overwhelming long-term benefits to the Hippo Protocol by ensuring sustainable growth and zero-capital ecosystem boosting. In the words of the proposal: "We are not taking users' assets; we are putting sleeping assets to work to secure the network for everyone."
## Standard Governance Fields
To maintain consistency with standard proposal formats, the following fields have been reviewed and currently require no additional provisions:
* Documentation: None
* Drawbacks: None
* Unresolved Questions: None
* Security Considerations: None
* Prior Art: None
* Backwards Compatibility: None
* Test Cases: None
* Reference Implementation: None
* Future Possibilities: N/A
