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 4 dependencies

• AssetRequired through Asset versus claim

  1. Strategy
  2. Asset versus claim
  3. Asset

• ClaimRequired through Asset versus claim

  1. Strategy
  2. Asset versus claim
  3. Claim

• TokenRequired through Asset versus claim

  1. Strategy
  2. Asset versus claim
  3. Token

• Asset versus claimDirect prerequisite

  1. Strategy
  2. Asset versus claim

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

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

Strategies turn reusable actions such as lending, staking, swapping, and hedging into an explicit plan whose return path, loss path, constraints, and operator powers can be analyzed together.

Traditional-finance analogy

Investment mandate and operating playbook is the closest comparison recorded for this concept.

Where the analogy stops

• Smart contracts can execute parts of a strategy automatically, but keepers, governance, oracles, integrations, and upgrades can still control outcomes.
• On-chain transparency does not make a strategy profitable, market-neutral, liquid, legally protected, or free from execution and composability risk.

Main actors

• ActorCapital provider
• ActorStrategy designer or manager
• ActorVault, fund, or product contract
• ActorKeeper, allocator, or rebalancer
• ActorUnderlying protocols and counterparties
• ActorGovernance, risk, or emergency authority

Assets and claims

Assets — controlled or transformed resources

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

• AssetContributed assets
• AssetDeployed positions and received assets
• AssetCash or liquidity reserves

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.

• ClaimStrategy ownership or product claim
• ClaimUnderlying protocol claims and debts

A strategy is an ordered plan for using assets and financial primitives to seek a stated result under explicit rules and risks.

Why it exists

Individual actions such as lending, staking, swapping, providing liquidity, and hedging are reusable primitives. A strategy connects several actions into one mandate: what capital may do, when it rebalances, which constraints apply, where returns should come from, and how losses or failed operations are handled.

Traditional-finance analogy

An investment mandate plus an operating playbook is a useful analogy. Smart contracts can automate execution and enforcement, but keepers, managers, governance, oracles, integrations, and upgrades can still influence results. On-chain visibility does not make a strategy profitable, liquid, neutral, or legally protected.

Strategy balance sheet: actors, assets, claims, and liabilities

Capital providers contribute assets directly or through a vault or fund. A designer chooses the intended operations; a manager, allocator, or keeper may execute them. Underlying protocols and counterparties hold assets or create claims and debts. Governance or an emergency authority can change limits or interrupt the plan.

Table: Strategy balance sheet: actors, assets, claims, and liabilities

Layer	Asset or right	Claim or liability
Capital provider	Product or strategy claim	Contributed the principal
Product	Cash and deployed positions	Owes value under user claims and pending exits
Underlying protocols	Supplied assets or collateral rights	Receipt claims, debt, derivative, or withdrawal obligations
Operators	Authorized execution power	Duties, fees, and bounded discretion

Step-by-step mechanism

1. State the objective, reporting asset, time horizon, eligible assets, and unacceptable outcomes.
2. Define each operation, prerequisite state, venue, counterparty, oracle, and authority.
3. Transfer or approve only the capital needed for the initial allocation.
4. Record every received claim, incurred debt, fee, and change in liquidity.
5. Observe triggers and rebalance within leverage, concentration, slippage, and loss limits.
6. Attribute income to its actual payer and separate incentives and price changes.
7. Exit, unwind, or enter an emergency state without hiding stranded assets or residual liabilities.

Return path, loss path, and state changes

Capital flow deploys principal and returns proceeds. Claim flow records lending receipts, LP positions, staking claims, derivatives, debts, and product shares. Return flow begins with borrowers, traders, network issuance, service customers, asset issuers, or an incentive budget. Risk flow reverses through the same dependencies when prices move, counterparties fail, or execution breaks.

netStrategyResult
= namedIncome
  + realizedGains
  + valuationChange
  + incentives
  - financingCosts
  - executionCosts
  - fees
  - realizedLosses

The terms must use one reporting unit and time window. Deposits and withdrawals are capital flows, not investment profit.

Return source and loss allocation

A strategy creates no value merely by composing calls. Each return must have a payer or economic source. Direct losses first reduce strategy net assets; debt, liquidation, senior claims, reserves, insurance, or product terms determine who absorbs the loss next.

Engineer or auditor lens

Test allowed assets and targets, approval scope, position limits, debt ceilings, oracle freshness, slippage, reentrancy, callback behavior, keeper authorization, front-running, partial execution, stale pending state, valuation, fee checkpoints, rebalancing races, pause and unwind paths, upgrade powers, and recovery of stranded tokens. Prove accounting across the whole operation sequence, not one successful call in isolation.

Aave’s supply documentation illustrates a lending operation whose interest comes from borrowers and depends on utilization. Lido’s token integration guide illustrates staking-derived claims and queued withdrawals. These are building blocks, not evidence that a composition using them is safe or profitable. Both references were reviewed 2026-08-10.

Common misunderstandings

• “A strategy is the same as a product.” A strategy is the operating plan; a product packages it with claims, accounting, controls, and user terms.
• “Automation removes management risk.” Automation moves discretion into code, parameters, keepers, governance, and upgrades.
• “Positive APY proves productive return.” Incentives, leverage, price changes, and selective time windows can dominate reported yield.

Continue with yield strategy and how a vault packages a strategy.

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 operation has explicit preconditions, assets, claims, liabilities, authority, expected state change, and failure handling

2. SP-02Desired · not evaluated

   Reported return separates deposits and withdrawals from income, incentives, valuation changes, fees, costs, and realized losses

3. SP-03Desired · not evaluated

   Position limits, slippage limits, leverage bounds, allowed integrations, and emergency exits remain enforceable under adverse states

4. SP-04Desired · not evaluated

   Strategy assets, debts, pending operations, and downstream claims reconcile without double counting value

Prerequisites

Direct dependencies recorded by this concept's canonicaldepends_on relationships.

• Asset versus claimPath 4

  The asset-versus-claim distinction asks whether a token is the resource itself or a right whose value depends on another asset or obligor.

Learn next

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

• FundPath 42

  A fund is a pooled investment product defined by an objective, eligible assets, management and control rules, valuation, fees, redemptions, and profit-and-loss allocation.

• Integration riskPath 44

  Integration risk is the possibility that individually functioning components interact through incompatible assumptions, interfaces, units, callbacks, or lifecycle rules.

• VaultPath 67

  A vault is an on-chain asset container that accepts or controls assets, applies accounting and access rules, and may deploy capital through one or more strategies.

Knowledge check

Quiz

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

What problem does Strategy exist to address?

Model answer

Strategies turn reusable actions such as lending, staking, swapping, and hedging into an explicit plan whose return path, loss path, constraints, and operator powers can be analyzed together.

Mark as understood