Deflationary Mechanics
HYFY has a fixed original supply of one billion tokens and no function that can mint more after deployment. Its total supply can stay the same or fall, but it cannot expand above that original amount.
In plain language: HYFY burns are funded by genuine economic surplus or genuinely excess treasury reserves. They are not triggered simply because another month has passed.
Burned HYFY is permanently destroyed. The treasury balance falls, the token's totalSupply falls by the same amount, and the transaction can be verified on Polygon.
Two Ways a Burn Can Happen
| Burn path | What starts it | What protects the system |
|---|---|---|
| Monthly economic burn | A finalized month produces a positive burn allocation | Revenue, price, reserve, authorization, finality, and duplicate-execution checks |
| Excess-reserve burn | Treasury HYFY is genuinely above protected operational and claims needs | Only bounded excess is considered; protected obligations remain untouched |
These paths use the same principle: claims and required reserves come before scarcity.
What Must Be True for a Monthly Burn
A monthly burn can complete only when all applicable checks pass:
- The period has been finalized and has not already been burned.
- Reconciled economic activity creates a positive burn allocation.
- The price evidence used to convert value into HYFY is valid and current.
- The treasury still covers protected community claims and required reserves after the burn.
- The burn is within the operator's authority, or the required governance approval has been completed.
- The contract is not paused, network conditions are acceptable, and the transaction simulation succeeds.
If any required check fails, HYFY records a no-burn, review, or reconciliation outcome instead of guessing.
Simple Monthly Example
Assume a finalized month produces a $250 burn budget and the validated reference price is $0.05 per HYFY.
| Step | Illustrative result |
|---|---|
| Finalized burn budget | $250 |
| Validated HYFY reference price | $0.05 |
| Preliminary token amount | 5,000 HYFY |
| Final approved burn after safeguards | Up to 5,000 HYFY |
If the final approved amount is 5,000 HYFY, the treasury destroys those tokens. A total supply of 1,000,000,000 HYFY becomes 999,995,000 HYFY.
This is an explanatory example, not a promised monthly rate. The final amount can be smaller or zero after the applicable safeguards.
Why a Month May Have No Burn
A no-burn month can be the correct result. Common reasons include:
- no positive burn allocation was produced;
- revenue or period reconciliation is incomplete;
- price evidence is stale, inconsistent, or unavailable;
- the treasury must preserve claims or operational reserves;
- a larger action is waiting for governance approval;
- the contract is paused or the period is under review;
- network fees exceed the configured safety limit; or
- the same period was already processed.
This is why HYFY does not guarantee a burn every month. A guaranteed calendar burn would force the treasury to destroy assets even when the economic or safety conditions do not support it.
| Approach | Advantage | Main weakness |
|---|---|---|
| Guaranteed monthly burn | Easy marketing message | Can weaken reserves and burn against unreliable data |
| Conditional HYFY burn | Protects claims, reserves, and data integrity | Burn timing and amount can vary |
HYFY uses the conditional approach because long-term solvency is more important than producing an artificial monthly headline.
Excess-Reserve Protection
The second path is a treasury guardrail, not a routine monthly promise. It considers only operational HYFY that remains genuinely excess after protected obligations.
A large treasury balance alone does not make tokens burnable. If those tokens are needed for community claims, operating reserves, or another governed obligation, they are protected. When true excess exists, only a bounded portion can be retired during an eligible period.
A Burn Is Not a Buyback
HYFY's current burn path destroys treasury-held tokens from the fixed supply. It does not purchase tokens from users or place a market order.
This distinction matters:
- a burn lowers total supply;
- a buyback creates market demand by purchasing tokens; and
- a liquidity addition moves treasury assets into a market position without lowering total supply.
Burns do not guarantee price appreciation, create a price floor, or guarantee liquidity.
Reading Supply Changes
| Treasury event | Treasury balance | Circulating supply | Total supply |
|---|---|---|---|
| 10,000 HYFY community claim | Decreases | Increases | Unchanged |
| 10,000 HYFY liquidity addition | Decreases | Usually increases | Unchanged |
| 10,000 HYFY treasury burn | Decreases | No required increase | Decreases by 10,000 |
| 10,000 HYFY custody transfer | Moves between controlled addresses | Usually unchanged | Unchanged |
Only a completed on-chain burn and the resulting totalSupply change prove that HYFY was destroyed. A proposed allocation or a lower treasury balance is not, by itself, proof of a burn.