Treasury Safety and Governance
HYFY's treasury is protected by multiple layers of security that eliminate single points of failure.
Security Layers
- Smart contract custody: All treasury HYFY lives in the treasury contract. No personal or app-operated wallet holds treasury tokens directly
- Polygon Multisig: All significant treasury operations require approval from multiple keyholders
- 48-Hour Timelock: Every privileged action is publicly queued on-chain 48 hours before execution, giving the community a review window
- Emergency Pause: The guardian multisig can freeze all operations instantly if an exploit is detected, with a timelocked unpause process to ensure deliberate resumption
- Merkle-Root Commitments: Monthly Karma commitments are published on-chain, making claim calculations publicly verifiable without exposing user data
Team tokens are locked for 3 years with a 1-year cliff. No team member can access or sell tokens early, aligning the team's incentives with long-term platform success.
Governance: The DAO Path
As HYFY matures, governance will expand to give the community a voice in protocol decisions. The Ecosystem allocation (100M HYFY) requires DAO approval for disbursements. Governed parameters such as claim ratios and treasury throttle rates are adjustable only through timelocked governance, within hard-coded safety bounds that prevent extreme or harmful configurations.
The goal is a gradually decentralizing protocol where power moves from the founding team to the community over time, with transparent, auditable, on-chain governance.
Governed Parameters
The following protocol parameters are adjustable through timelocked governance, each within hard-coded safety bounds that prevent extreme or harmful configurations:
- Revenue allocation ratios — how the ecosystem pool is split between claims, treasury, liquidity, and burns
- Claim throttle rate — how aggressively claims are moderated relative to treasury health
- Monthly claim caps — per-user limits that adjust with participation
- Dual-earn percentages — how much Karma is shared between spender and recipient
No parameter can be changed instantly. All changes require a multi-signature proposal followed by a mandatory waiting period before execution, and all parameter updates are bounded by immutable safety ranges set at the contract level.
Automatic Treasury Safety
If the treasury balance exceeds a designated safety threshold, the protocol automatically burns excess tokens to prevent over-accumulation. If the protocol's liquidity ratio drops below a critical level, a DAO-governed emission mechanism can release treasury tokens to restore market health — subject to timelocked approval and bounded rates.