# Yield vaults: shares, strategies and the meaning of redemption

A yield vault pools deposited assets into a strategy and records users’ claims as shares. ERC-4626 standardizes a common asset-and-share interface, not the strategy’s safety or return. A share’s conversion value, realizable withdrawal and market price can differ, particularly when limits, fees or losses apply.

Evidence: [ERC-4626: Tokenized Vaults](https://eips.ethereum.org/EIPS/eip-4626); [ERC-4626 security considerations](https://docs.openzeppelin.com/contracts/5.x/erc4626)

Canonical: https://degreesofsatoshi.com/encyclopedia/yield-vaults/
Published: 2026-10-02
Substantively modified: 2026-10-02
Independently verified by an automated reviewer: 2026-10-02T15:08:18.373Z

AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied.

## Key facts

- **Interface:** ERC-4626 defines assets, shares, deposits and withdrawals. ([ERC-4626: Tokenized Vaults](https://eips.ethereum.org/EIPS/eip-4626))
- **Limits:** Maximum operations and previews have distinct semantics. ([ERC-4626: Tokenized Vaults](https://eips.ethereum.org/EIPS/eip-4626))
- **Rounding:** Share conversions and donation effects need careful implementation. ([ERC-4626 security considerations](https://docs.openzeppelin.com/contracts/5.x/erc4626))

## Shares divide a changing pool of assets

Consider a simplified vault with 1,200 underlying units and 1,000 shares. Before fees and rounding, one share corresponds to 1.2 underlying units. Depositing 120 units at that ratio would create 100 shares, leaving 1,320 units backing 1,100 shares.

If the strategy later loses assets, the share claim can shrink. The existence of a standard interface does not specify what the strategy owns, which counterparties it uses or what authority can alter it.

Evidence: [ERC-4626: Tokenized Vaults](https://eips.ethereum.org/EIPS/eip-4626)

## A conversion estimate is not a withdrawal guarantee

ERC-4626 separates informational conversions from previews and maximum operation limits. For example, a conversion can express an idealized share-to-asset relationship while an operation preview accounts for the relevant transaction semantics and fees.

The amount redeemable now can also be limited. A displayed accounting value should not silently be treated as immediately withdrawable cash. Integrations need the actual method’s defined behavior rather than whichever number produces the most attractive display.

Evidence: [ERC-4626: Tokenized Vaults](https://eips.ethereum.org/EIPS/eip-4626)

## Small-unit arithmetic matters at the edges

Deposits and withdrawals round according to their operation’s rules. When a deposit would receive very few share units, rounding can become economically significant. Direct donations can also change the ratio between assets and outstanding shares in some implementations.

OpenZeppelin documents the resulting inflation-attack concern and a mitigation design. That documentation does not certify every vault claiming ERC-4626 compatibility. An assessment must include the deployed implementation, strategy, limits, fees and underlying dependencies.

Evidence: [ERC-4626 security considerations](https://docs.openzeppelin.com/contracts/5.x/erc4626); [ERC-4626: Tokenized Vaults](https://eips.ethereum.org/EIPS/eip-4626)

## Questions

### Does ERC-4626 compliance mean the yield is guaranteed?

No. It standardizes an interface for tokenized vaults. The strategy can lose assets, fees can apply and withdrawals can be limited. Those properties require examination beyond the interface.

Evidence: [ERC-4626: Tokenized Vaults](https://eips.ethereum.org/EIPS/eip-4626)

## Claims and scope

### yield-vaults-quick-answer

A yield vault pools deposited assets into a strategy and records users’ claims as shares. ERC-4626 standardizes a common asset-and-share interface, not the strategy’s safety or return. A share’s conversion value, realizable withdrawal and market price can differ, particularly when limits, fees or losses apply.

Scope: {"collection":"defi","dataAsOf":null,"blockHeight":null}

### yield-vaults-fact-interface

Interface: ERC-4626 defines assets, shares, deposits and withdrawals.

Scope: {"collection":"defi","dataAsOf":null,"blockHeight":null}

### yield-vaults-fact-limits

Limits: Maximum operations and previews have distinct semantics.

Scope: {"collection":"defi","dataAsOf":null,"blockHeight":null}

### yield-vaults-fact-rounding

Rounding: Share conversions and donation effects need careful implementation.

Scope: {"collection":"defi","dataAsOf":null,"blockHeight":null}

## Sources

- [ERC-4626: Tokenized Vaults](https://eips.ethereum.org/EIPS/eip-4626) — Ethereum Improvement Proposals. Vault shares, assets, previews, withdrawal limits and rounding. Locator: Specification; Security Considerations. Retrieved: 2026-10-02.
- [ERC-4626 security considerations](https://docs.openzeppelin.com/contracts/5.x/erc4626) — OpenZeppelin. Share conversion, rounding and donation-based exchange-rate manipulation. Locator: Security concern: Inflation attack; Custom behavior. Retrieved: 2026-10-02.

## Revision history

- 2026-10-02: First publication after primary-source research and independent automated verification.

## Cite this entry

Degrees of Satoshi editorial project. “Yield vaults: shares, strategies and the meaning of redemption.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/yield-vaults/