Yield strategy

Reading depth

Each view includes the earlier layers; the complete engineer or auditor page is shown by default.

BeginnerCore purpose and mental modelPractitionerAdds mechanisms and economicsEngineer or auditorAdds state and verification

Dependency check

Advanced detail assumes prerequisite knowledge

Before using practitioner mechanisms or engineer and auditor checks, review any unfamiliar dependency. These paths come from canonical depends_on relationships; Web3 Academy does not track completed lessons.

Review 5 dependencies

• AssetRequired through Asset versus claim

  1. Yield strategy
  2. Strategy
  3. Asset versus claim
  4. Asset

• ClaimRequired through Asset versus claim

  1. Yield strategy
  2. Strategy
  3. Asset versus claim
  4. Claim

• TokenRequired through Asset versus claim

  1. Yield strategy
  2. Strategy
  3. Asset versus claim
  4. Token

• Asset versus claimRequired through Strategy

  1. Yield strategy
  2. Strategy
  3. Asset versus claim

• StrategyDirect prerequisite

  1. Yield strategy
  2. Strategy

A yield strategy deploys assets through one or more financial primitives to seek named cash flows or asset growth while accepting explicit costs and loss paths.

Category: Products and vaultsContainer outline category cue

System record

Start with the economic purpose, participants, resources, and entitlements before studying implementation detail.

Why it exists

Yield strategies coordinate repeatable capital allocation, compounding, rebalancing, and risk controls so a product can pursue returns without users executing every step themselves.

Traditional-finance analogy

Income-oriented investment strategy is the closest comparison recorded for this concept.

Where the analogy stops

• DeFi strategies can compose lending, staking, liquidity, derivatives, incentives, and leverage atomically, creating shared smart-contract and liquidation dependencies.
• Displayed APY can include temporary token incentives, leverage, valuation assumptions, and compounding rather than durable cash income.

Main actors

• ActorCapital provider
• ActorStrategy manager, allocator, or keeper
• ActorBorrowers, traders, networks, or service customers that pay returns
• ActorUnderlying protocols and counterparties
• ActorVault, fund, or product
• ActorGovernance or risk authority

Assets and claims

Assets — controlled or transformed resources

Assets are resources the mechanism moves, holds, values, or transforms.

• AssetPrincipal assets
• AssetDeployed lending, staking, liquidity, derivative, or RWA positions
• AssetEarned fees, interest, issuance, incentives, or asset income

Claims — entitlements and corresponding dependencies

Claims are rights to value, repayment, redemption, control, or another party's performance; each depends on an obligation or system that must honor it.

• ClaimProduct or strategy ownership claim
• ClaimUnderlying protocol claims and debts

A yield strategy deploys assets through named financial operations to seek income or asset growth while accepting explicit costs and loss paths.

Why it exists

Different primitives expose different return payers and risks. A yield strategy selects, combines, monitors, compounds, and rebalances those positions so a product can pursue an objective without each user operating every step.

Traditional-finance analogy

An income-oriented investment strategy is a useful analogy. DeFi can compose lending, staking, AMMs, derivatives, incentives, and leverage within shared smart-contract state. Displayed APY can therefore contain temporary subsidies, price marks, leverage, and assumed compounding rather than durable cash income.

Decompose the return

Table: Decompose the return

Strategy component	Economic payer or source	Main paired loss path
Lending	Borrowers pay interest	Default, bad debt, and illiquidity
Staking	Issuance, transaction users, or services	Penalties, slashing, and token dilution
AMM liquidity	Traders pay swap fees	Inventory change, adverse selection, and impermanent loss
Derivative carry	Opposing traders or market imbalance pay funding or premium	Basis, funding reversal, margin, and liquidation
RWA income	Off-chain issuer, borrower, or underlying asset pays	Legal, custody, credit, valuation, and redemption failure
Incentives	Treasury or token-distribution budget pays	Emissions end or token value falls

For one reporting asset and time window:

netYieldResult
= interest
  + tradingFees
  + stakingPayments
  + serviceOrAssetIncome
  + incentives
  + realizedAndUnrealizedPriceChange
  - financingCosts
  - executionCosts
  - productFees
  - realizedLosses

Do not add returns across assets, periods, or valuation rules without explicit conversion. APY annualizes an assumed path; it is not a promised future payment.

Step-by-step accounting lifecycle

1. Select principal, objective, horizon, liquidity requirement, and maximum acceptable loss.
2. Map each operation to a payer, claim, liability, oracle, control, and exit.
3. Allocate capital within concentration, leverage, debt, and counterparty limits.
4. Accrue income and costs from authoritative state rather than displayed headline rates.
5. Revalue positions, recognize loss, and rebalance under explicit triggers and slippage limits.
6. Harvest or compound only after separating incentives, fees, gas, and financing costs.
7. Report gross, net, realized, unrealized, nominal, and dilution-adjusted outcomes where relevant.

Table: Step-by-step accounting lifecycle

Accounting event	Strategy assets and liabilities	Holder claim
Allocate	Cash falls as protocol claims or positions rise	Claim composition changes; no return is recorded
Accrue	Receivables, rewards, fees, or debt change	Net value changes only after recognized costs
Realize loss	Assets fall or liabilities rise	Holder value falls unless a funded backstop pays
Harvest	Accrued value becomes controlled settlement assets	Claim value is reconciled before compounding
Exit	Positions settle and residual liabilities remain visible	Redeemable value reflects what was recovered

Capital flow deploys and returns principal. Claim flow accumulates receipt tokens, LP shares, staking positions, derivatives, debts, and product shares. Return flow traces each payer. Risk flow traces the same integrations in reverse into product NAV and the strategy holder’s claim.

Return source and loss allocation

No “yield layer” creates money. Borrowers, traders, networks, service customers, asset issuers, sponsors, or market counterparties provide value. Strategy holders usually absorb net losses unless a named reserve, insurer, manager, counterparty, or subordinated tranche bears them under enforceable terms.

Engineer or auditor lens

Test accounting across harvests and reports, changing exchange rates, reward tokens, price conversions, oracle freshness, debt and leverage, slippage, front-running, compounding, claim duplication, fee checkpoints, partial exits, liquidations, reward cessation, integrations, upgrade powers, and emergency unwinds. A successful happy-path harvest does not prove capital preservation.

Aave’s supply-token documentation identifies borrower utilization as one lending-return driver. Ethereum’s reward documentation identifies issuance-linked consensus duties and penalties. These sources illustrate distinct payers and risks rather than a universal yield formula. Both references were reviewed 2026-08-10.

Common misunderstandings

• “Yield is generated by the strategy.” A borrower, trader, network, service, asset issuer, sponsor, or counterparty must provide value.
• “Auto-compounding removes risk.” It changes execution frequency and exposure while adding operations and fees.
• “Market-neutral means loss-neutral.” Basis, funding, execution, liquidity, oracle, and liquidation risk remain.

Return to the general strategy and see how a vault packages it.

Machine-readable model

Key equations

Canonical expressions come from the structured concept record. KaTeX renders the notation, while the plain-text expression and variable table keep its meaning and units inspectable without JavaScript. Read the narrative above for the model's domain, assumptions, and rounding rules.

This concept does not require one canonical equation. Its mechanism and state transitions remain the authoritative explanation; do not invent a formula merely to make the topic look quantitative.

Assurance contract

Security properties

These structured statements define desired behavior. Their stable IDs can bind tests, invariants, specifications, audit findings, or proof results without turning descriptive review advice into an assurance claim.

Desired · not evaluated: No test, audit, or proof result is implied until scoped evidence is linked to this property.

1. SP-01Desired · not evaluated

   Every return component identifies its payer, asset, time window, conditions, and whether it is income, issuance, incentive, or valuation change

2. SP-02Desired · not evaluated

   Gross return, net return, fees, costs, leverage, deposits, withdrawals, and realized and unrealized losses remain separately reconcilable

3. SP-03Desired · not evaluated

   Rebalancing cannot exceed approved assets, integrations, leverage, slippage, debt, or loss limits

4. SP-04Desired · not evaluated

   Return and loss paths remain inspectable through every underlying protocol claim, liability, oracle, and control authority

Prerequisites

Direct dependencies recorded by this concept's canonicaldepends_on relationships.

• StrategyPath 37

  A strategy is an ordered set of financial operations, controls, and rebalancing rules intended to produce a stated outcome from underlying assets and primitives.

Learn next

Concepts that directly depend on this one, ranked by the recommended learning path. Check each page for additional prerequisites.

No concept directly builds on this page in the current graph; use the guided learning paths to choose another branch.

Knowledge check

Quiz

Answer in your own words, then open the model answer.

What problem does Yield strategy exist to address?

Model answer

Yield strategies coordinate repeatable capital allocation, compounding, rebalancing, and risk controls so a product can pursue returns without users executing every step themselves.

Mark as understood