Revenue Model
HYFY earns platform revenue when users purchase Space Credits through supported payment channels. Revenue records are reconciled against provider events, fees, refunds, and adjustments before they can influence tokenomics.
Only verified net revenue is eligible for the monthly economic process. Gross checkout values, incomplete payments, duplicate webhooks, unconfirmed transactions, and unreconciled adjustments are not treated as final revenue.
After operating needs are accounted for, a governed portion of eligible revenue may support the token ecosystem. Depending on the month and applicable safeguards, that support can include:
- a bounded community-claims allocation;
- treasury reserves for future obligations and system resilience;
- conditional HYFY burns; and
- liquidity operations for the official HYFY/USDC market.
The public allocation policy is intentionally simple at the top level, while the safety calculation beneath it is not published as a gaming recipe. The production base policy assigns 75% of verified net revenue to platform operations and 25% to token-economy support. That support budget is divided 50% to claims, 30% to treasury resilience, 10% to liquidity, and 10% to burns. Final token quantities still depend on governed bounds, participation, treasury state, and verified market inputs.
Monthly Closing Process
Monthly processing is staged. Revenue is aggregated and reconciled, the period's inputs are closed, calculations are performed, and the resulting package is checked before token-sensitive actions become eligible. Finalized monthly facts are protected from silent rewriting, and repeated jobs use idempotency controls so retries do not duplicate allocations or transactions.
A month may complete normally, complete with no claims, carry eligible amounts forward, or stop for review when required data is missing. Low revenue does not create an obligation to manufacture rewards, and failed price or liquidity inputs block dependent actions rather than allowing the system to guess.
Space Credit purchases therefore support the broader HYFY platform, but they do not buy HYFY and do not entitle the purchaser to a return.
From Purchase to Monthly Close
The revenue path contains several checkpoints:
- A purchase is initiated through an approved mobile, web, or crypto payment channel.
- The provider confirms settlement. A checkout screen or client callback alone is not enough.
- Space Credits are recorded once using a unique provider or transaction reference.
- Fees, refunds, reversals, and adjustments are reconciled into the period's net revenue.
- The month is closed only after the required sources agree and outstanding exceptions are resolved or formally accounted for.
- Eligible tokenomics actions are prepared under the active governance settings and safety checks.
This sequence separates user balance delivery from token allocation. A user should receive valid Space Credits promptly after a confirmed purchase, while the tokenomics system waits for a reconciled monthly view before treating the revenue as final.
Worked Dollar Example
Suppose verified purchases, fees, refunds, and adjustments produce $10,000 of reconciled net revenue for a month.
| Destination | Share of its parent budget | Dollar amount |
|---|---|---|
| Platform operations | 75% of net revenue | $7,500 |
| Token-economy support | 25% of net revenue | $2,500 |
| Claims | 50% of support budget | $1,250 |
| Treasury resilience | 30% of support budget | $750 |
| Liquidity | 10% of support budget | $250 |
| Burns | 10% of support budget | $250 |
The four support rows add back to $2,500; together with operations, the complete $10,000 is accounted for. This is the base allocation, not a promise that every downstream action executes. A blocked action remains recorded under the close rules rather than being silently spent elsewhere.
Illustrative HYFY Conversion
If the finalized reference price for this example were $0.05 per HYFY, the $1,250 claims budget would represent a 25,000 HYFY base allocation and the $250 burn budget would represent up to 5,000 HYFY. A balanced $250 liquidity budget could pair $125 USDC with $125 worth of HYFY, or 2,500 HYFY at that example price.
Those token quantities are illustrative. The production close applies price validation, treasury protection, participation controls, rounding, and eligibility before publishing final amounts. A month can therefore have valid revenue but no burn or liquidity transaction when dependent evidence is incomplete.
Why Revenue Does Not Equal Rewards
Revenue is an input, not a direct promise to users. HYFY must continue paying for infrastructure, payment fees, support, development, compliance, and security. The amount available to the token ecosystem can also be limited by treasury health and governed risk controls.
Likewise, buying more Space Credits does not give the purchaser a direct claim on a larger share of HYFY. Claims are based on eligible Karma and the monthly claim process, not on ownership of a receipt. This prevents Space Credit checkout from functioning as a disguised token sale.
Quiet, Failed, and Corrected Months
If participation is unusually low, the system can apply conservative carry-forward or no-claim handling instead of letting a tiny claimant set absorb an outsized distribution. If required revenue or market data is missing, dependent jobs stop for review. If a provider later reports a valid correction, it is recorded as an adjustment rather than rewriting a finalized financial history without evidence.
The goal is not to force activity every month. It is to make every completed month internally consistent, repeatable, and explainable.