Glossary

Vault Share

A vault share is a token representing proportional ownership of assets deposited in a DeFi yield vault.

Key Takeaways

  • A vault share is a fungible token representing your proportional claim on the total assets inside a yield vault. As the vault earns yield, the value of each share increases while your share count stays constant.
  • The share-to-asset ratio is the core accounting mechanism: it starts near 1:1 at launch and grows over time as yield accrues. This model, standardized in ERC-4626, is preferred over rebasing tokens because it composes cleanly with other DeFi protocols.
  • The conversion math is straightforward: shares received equals deposit amount divided by the current price per share. When you redeem, you receive assets equal to your shares multiplied by the (now higher) price per share.

What Is a Vault Share?

A vault share is a token you receive when depositing assets into a DeFi yield vault. It represents your proportional ownership of everything the vault holds. If you own 10% of the outstanding shares, you can redeem them for 10% of the vault's total assets at any time.

Think of vault shares like shares in a mutual fund. When you invest $1,000 into a fund with a net asset value (NAV) of $10 per share, you receive 100 shares. As the fund's investments grow, the NAV rises: at $12 per share, your 100 shares are worth $1,200. You never received additional shares, but each share became more valuable. Vault shares work the same way.

This mechanism solves a fundamental problem in DeFi: how to track each depositor's entitlement to yield without expensive per-user accounting. Instead of recording each user's balance and yield separately, the vault tracks one global number (total assets) and lets the share ratio handle the rest. Every depositor benefits proportionally, and the math stays simple regardless of how many users participate.

How It Works

Vault share accounting revolves around a single variable: the ratio of total underlying assets to total shares outstanding. This ratio, called the price per share or exchange rate, determines how many shares you receive on deposit and how many assets you receive on redemption.

The Share-to-Asset Ratio

When a vault launches, the exchange rate typically starts at 1:1. One deposited token mints one share. As the vault's strategy generates yield (through lending, staking, trading fees, or other mechanisms), the total assets in the vault grow while the total supply of shares stays constant. This causes the price per share to increase.

Consider a simple example:

  1. Alice deposits 1,000 USDC into an empty vault and receives 1,000 shares
  2. The vault deploys USDC into a lending protocol and earns 50 USDC in interest
  3. The vault now holds 1,050 USDC with 1,000 shares outstanding
  4. Price per share rises from 1.00 to 1.05 (1,050 / 1,000)
  5. Bob deposits 1,000 USDC and receives 952.38 shares (1,000 / 1.05)
  6. The vault now holds 2,050 USDC with 1,952.38 shares outstanding: the ratio remains 1.05

When Alice redeems her 1,000 shares, she receives 1,050 USDC (1,000 × 1.05), capturing her proportional yield. Bob's 952.38 shares also entitle him to exactly 1,000 USDC at that moment, because he deposited after yield had already accrued.

The Core Math

Two formulas govern all vault share interactions:

// Depositing: how many shares do I receive?
shares = depositAmount × totalShares / totalAssets

// Redeeming: how many assets do I receive?
assets = shareAmount × totalAssets / totalShares

// Price per share
pricePerShare = totalAssets / totalShares

In practice, vaults add a small offset to these formulas to prevent rounding exploits. The ERC-4626 standard uses a virtual decimals offset that adds virtual shares and assets to the conversion:

// ERC-4626 conversion with virtual offset
shares = (assets × (totalSupply + 10^offset)) / (totalAssets + 1)
assets = (shares × (totalAssets + 1)) / (totalSupply + 10^offset)

This offset prevents the front-running vulnerability known as the inflation attack, where an attacker donates assets to an empty vault to manipulate the share price and steal from subsequent depositors.

Rebasing vs. Share-Based Models

There are two ways a vault can represent yield to depositors:

PropertyRebasing ModelShare-Based Model
How yield appearsToken balance increasesToken value increases
Token countChanges over timeStays constant
ExamplesAave aTokens, Lido stETHYearn yvTokens, wstETH
DeFi composabilityBreaks many integrationsWorks with all standard protocols
User experienceIntuitive: balance goes upRequires understanding exchange rate

Rebasing tokens adjust every holder's wallet balance to reflect yield, which feels intuitive but breaks assumptions that most smart contracts rely on. AMMs, lending vaults, and cross-chain bridges expect balances to change only through explicit transfers. When a rebasing token silently increases balances, these protocols can miscount funds, trigger unexpected liquidations, or produce rounding errors.

The share-based model avoids all of these issues. Because the share token behaves like a standard ERC-20 token with a fixed supply (per depositor), it integrates seamlessly with DEXs, lending protocols, and yield tokenization platforms. This is why the ERC-4626 standard adopted the share-based model, and why wrapped versions of rebasing tokens (like Lido's wstETH) exist specifically to enable DeFi composability.

The ERC-4626 Standard

Finalized in April 2022, ERC-4626 is the tokenized vault standard that defines a universal interface for vault share accounting. Before ERC-4626, every vault protocol (Yearn, Aave, Compound) implemented its own share logic with different function names, rounding behavior, and edge-case handling. Integrators had to write custom adapters for each protocol.

ERC-4626 standardizes the interface with key functions:

// Core ERC-4626 vault interface
function totalAssets() returns (uint256)      // Total underlying assets held
function convertToShares(uint256 assets)      // Preview: assets → shares
function convertToAssets(uint256 shares)      // Preview: shares → assets
function deposit(uint256 assets, address to)  // Deposit assets, receive shares
function redeem(uint256 shares, address to)   // Burn shares, receive assets
function mint(uint256 shares, address to)     // Specify shares desired
function withdraw(uint256 assets, address to) // Specify assets desired

Because the vault share is itself an ERC-20 token, it can be transferred, traded on a DEX, posted as collateral, or deposited into another vault. This composability is the standard's most important property: yield positions become liquid, programmable tokens that other contracts can integrate without knowing the underlying strategy.

By early 2026, total value locked in ERC-4626-compliant vaults exceeded $30 billion across chains, with major protocols including Yearn V3, Morpho, and numerous yield aggregators adopting the standard.

Use Cases

Yield Aggregation

Yield aggregators use vault shares as their primary accounting mechanism. Users deposit tokens, receive vault shares, and the protocol automatically rotates capital across yield strategies. The auto-compounding of rewards back into the vault increases the total assets, which in turn increases the value of every outstanding share.

Lending Protocols

Lending protocols issue vault shares to depositors who supply liquidity. When borrowers pay interest, the vault's total assets grow, and each lender's shares become redeemable for more of the underlying asset. Protocols like Morpho and Aave use this model (or wrapped versions of it) to track lender positions.

Stablecoin Yield

Stablecoin yield vaults accept stablecoin deposits and deploy them into lending markets, liquidity pools, or real-world asset strategies. The vault shares serve as receipt tokens proving the depositor's claim on both the original principal and accumulated yield. Some yield-bearing stablecoins are themselves ERC-4626 vault shares, where the stablecoin's value appreciates relative to its underlying as yield accrues.

Collateral and Composability

Because vault shares are standard ERC-20 tokens with a deterministic price feed (the exchange rate), they can serve as collateral in lending protocols. A user can deposit ETH into a yield vault, then use the resulting vault shares as collateral to borrow stablecoins. This enables capital efficiency: the depositor earns yield on their ETH while simultaneously accessing liquidity through borrowing.

Liquidity Provider Tokens

LP tokens from decentralized exchanges function as vault shares. When you provide liquidity to an AMM pool, you receive LP tokens representing your share of the pool. As the pool collects trading fees, each LP token becomes redeemable for a growing proportion of the underlying assets.

Risks and Considerations

Inflation Attacks

The first-depositor inflation attack is the most well-known vault share vulnerability. An attacker deposits a minimal amount to receive one share, then donates a large sum directly to the vault (bypassing the deposit function). This inflates the price per share so that when a victim deposits, rounding causes them to receive zero shares, effectively donating their deposit to the attacker. The ERC-4626 virtual offset mitigation and OpenZeppelin's implementation address this by ensuring the math never rounds to zero in practical scenarios.

Smart Contract Risk

Vault shares are only as safe as the underlying smart contract and its yield strategy. Bugs in the vault logic, vulnerabilities in the strategy contracts, or exploits in the protocols where assets are deployed can all result in loss of funds. A smart contract audit reduces but does not eliminate this risk.

Oracle and Pricing Risk

When vault shares are used as collateral, the lending protocol must accurately price them. If the exchange rate reported by convertToAssets can be manipulated (through flash loans or price oracle manipulation), an attacker could inflate the apparent value of their vault shares to borrow more than they should. Protocols mitigate this by using time-weighted average prices or requiring minimum deposit periods.

Liquidity and Redemption Risk

Not all vault assets are instantly liquid. If the underlying strategy locks funds in long-term positions or if many users try to redeem simultaneously, the vault may not have enough liquid assets to honor all redemptions. Some vaults implement redemption queues or withdrawal delays to manage this risk.

Precision and Rounding

Share-based accounting introduces rounding in every conversion. Small depositors may lose fractions of a token to rounding on both deposit and withdrawal. While ERC-4626 specifies that rounding should always favor the vault (protecting existing shareholders), this means depositors systematically receive slightly fewer shares than the theoretical amount, and slightly fewer assets on redemption.

Why It Matters

Vault shares are the accounting primitive that makes yield-bearing positions composable across DeFi. Without a standardized share mechanism, every protocol would need custom integration logic, and yield-bearing assets could not flow freely between protocols. The ERC-4626 standard turned what was a fragmented landscape of incompatible vault implementations into an interoperable ecosystem where vault shares from one protocol can be seamlessly used in another.

For the broader crypto ecosystem, vault shares demonstrate how token standards create network effects: once enough protocols adopt the same interface, the value of adopting it increases for everyone. This is the same dynamic that made ERC-20 the universal token standard: not because it was technically perfect, but because universal adoption made integration costs approach zero. For a deeper analysis of how yield vaults generate returns, see the yield-bearing stablecoins explained research article.

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.