Skip to content
Financial Context Wiki

Yield aggregator

A yield aggregator routes deposited assets through automated DeFi strategies, such as lending, liquidity provision, or staking, and may reinvest proceeds. This entry explains vault accounting, strategy execution, and the risks that can reduce or erase yield.

Updated

For educational purposes only; not investment advice. Investing may result in loss.

Direct answer

A yield aggregator is a smart-contract system that pools or routes deposits into one or more DeFi strategies, such as lending, liquidity provision, or staking. It can harvest rewards and reinvest them, but it cannot create risk-free income or guarantee that the displayed APY will persist.

The useful question is not simply “What is the APY?” It is “Which strategy produces the return, who controls the contracts, and what could prevent me from withdrawing?” Aggregators reduce the operational work of moving between strategies, while adding another layer of accounting, permissions, fees, and smart-contract dependencies.

  • Scenario: Is the aggregator used for lending, liquidity provision, staking, or a combination?
  • Return: Is the yield paid by borrowers and trading fees, or mainly by temporary token incentives?
  • Liquidity: Can the underlying positions be unwound when many users withdraw at once?
  • Control: Which contracts, keepers, or administrators can change strategies, limits, or upgrade logic?

How it works

A user approves an asset and deposits it into a vault or router. The contract mints shares that represent the user’s claim on the vault’s managed assets. In an ERC-4626 vault, functions such as deposit, withdraw, convertToShares, and previewRedeem standardize the accounting interface; the strategy allocation itself remains implementation-specific. The aggregator may lend assets, add liquidity, stake, or move funds between approved strategies, then claim and reinvest rewards.

Gross return is not the same as user return. A practical check is: net return = strategy income + fees and incentives - protocol and performance fees - token-price loss - gas and slippage - expected risk loss. Share-price calculations can be affected by rounding, donations, stale or manipulated oracles, withdrawal queues, and losses in an underlying protocol. Smart-contract interactions are public and generally irreversible, so transparency does not remove execution or governance risk.

Example

Suppose a vault advertises a high APY while allocating a stablecoin between a lending market and a liquidity pool. Before depositing, verify the underlying venues, the share-price method, withdrawal limits or queues, fee schedule, oracle dependencies, and the permissions that can change the strategy. Check whether the APY includes emissions that can fall when incentives end.

The aggregator may save gas and automate compounding, but it also concentrates exposure. A failure in the vault, an underlying protocol, a bridge, an oracle, or an administrator’s upgrade can affect every depositor. “The deposit transaction succeeded” therefore does not mean “the strategy is suitable” or “the principal is protected.”

Risks

  • Smart-contract risk: a bug, upgrade, or faulty accounting can misprice shares or block withdrawals.
  • Strategy risk: lending defaults, impermanent loss, staking penalties, or liquidity shortages can reduce assets.
  • Oracle and market risk: stale prices, depegs, volatility, and slippage can make positions or collateral worth less.
  • Governance and operational risk: privileged keys, keepers, bridges, front ends, and emergency controls can fail or be abused.

Crypto assets are volatile, and on-chain transactions are usually irreversible. Use independent contract addresses and documentation, review allowance and withdrawal behavior, test with a small amount, and size the position so a complete loss would be tolerable.

Common misconceptions

Does a higher APY mean a better aggregator?

No. APY can include short-lived token emissions, leverage, or compensation for risks that are not obvious from the interface. Separate recurring fees and borrower or trading demand from incentives, then test whether the strategy can exit under stressed liquidity.

Does ERC-4626 or an audit make a vault safe?

No. ERC-4626 standardizes a tokenized-vault interface; it does not certify the strategy, oracle, permissions, economics, or implementation. An audit can identify some code issues but cannot guarantee correct governance, infrastructure, market liquidity, or future upgrades.

How should a first deposit be checked?

Confirm the network and contract address from an independent source, read the asset and share decimals, inspect preview and limit functions, approve only the required amount, and complete a small deposit-and-withdraw test. Keep long-term holdings separate from the wallet used for experimental protocols.

Sources

Navigation

Search the wiki...