Skip to main content

Safeguards for Fairness and Stability

HYFY includes a set of built-in protections designed to keep claims fair, monthly processing predictable, and treasury actions conservative. These protections sit behind the scenes and help the tokenomics behave consistently as usage grows.

Claim Fairness​

Monthly claims are protected by several mechanisms that reduce gaming and keep rewards tied to real participation:

  • quiet-month protections reduce the advantage of claiming in unusually low participation months
  • carry-forward rules can hold back part of a monthly claim pool when activity is abnormally quiet
  • weighted claimant participation looks at meaningful claim activity instead of relying only on raw wallet count
  • throughput limits reduce extreme month-to-month banking behavior
  • claim requests close shortly before the monthly cycle is finalized instead of remaining open until the last moment

Claim Activation And Verification​

Claim activation is intentionally staged rather than immediate. Before claims become active for a month, the system prepares the monthly records, stores the relevant outputs, and waits through a brief review period before activation.

This gives the protocol a cleaner and more auditable claim cycle than a single-step publish flow.

Claiming depends on identity verification and a defined monthly submission window. The protocol also uses a staged activation flow so monthly claim data can be published and reviewed before claiming opens.

Karma Balance Protection​

HYFY separates claimable and non-claimable utility behavior more carefully than simple point systems. If the lifetime community claims budget gets low, newly earned Karma can be split into:

  • a claimable balance
  • a utility-only balance

This helps protect the long-term claims pool while still preserving in-app utility.

Liquidity And Treasury Safety​

Liquidity-sensitive treasury actions are guarded conservatively. The protocol does not rely on a single intraday condition or incomplete market data before treating a liquidity situation as severe enough to justify action.

In practice, this means treasury release actions stay blocked unless the required market observations are present and sustained conditions are met.

Why This Matters​

These safeguards are meant to make the system sturdier without changing the core user promise:

  • real participation should matter more than timing games
  • treasury actions should stay conservative
  • monthly processing should remain orderly and auditable
  • the app should remain understandable for normal users even as stronger protections operate behind the scenes