A vault screen shows 100 shares and a preview of 110 underlying tokens. Those are different units. There is also another question to answer before treating the preview as money available now: how much does the vault currently allow that owner to redeem?
For readers comparing ERC-4626 vault shares and assets, the useful distinction is between ownership, conversion, the operation preview and its limit. This explainer uses the ERC-4626 specification and a named OpenZeppelin reference implementation. The numbers are fictional; no deposit or withdrawal was tested.
Shares are the receipt token; assets are the underlying token
ERC-4626 standardizes an interface for tokenized vaults with one underlying ERC-20 accounting asset. The vault's ERC-20 balance and total supply describe its shares. The asset() method identifies the separate underlying token.
Holding 100 shares does not mean holding 100 units of that asset. The conversion depends on the vault's accounting and implementation. Nor does the standard prescribe a profitable investment strategy or guarantee that the asset keeps a particular market price.
totalAssets() describes underlying assets managed by the vault. Under the standard, that accounting can include assets beyond idle tokens waiting in a simple cash drawer. Read the implementation before treating the number as immediately transferable liquidity. The lending-utilization explainer covers a separate Compound III cash-versus-claim example; its formula is not an ERC-4626 conversion formula.
Four operations choose which amount is fixed
The method names distinguish an exact asset amount from an exact share amount:
| Operation | Amount specified | Amount calculated | Matching preview |
|---|---|---|---|
deposit | Assets paid in | Shares received | previewDeposit(assets) |
mint | Shares received | Assets paid in | previewMint(shares) |
withdraw | Assets received | Shares burned | previewWithdraw(assets) |
redeem | Shares burned | Assets received | previewRedeem(shares) |
For a withdrawal of exactly 10 assets, previewWithdraw(10) estimates the shares needed. For redemption of exactly 10 shares, previewRedeem(10) estimates the assets received. Interchanging those calls can turn the intended amount into a different request.
Keep the owner, caller and receiver separate too. They can be different addresses. The selected implementation checks share allowance when someone other than the owner initiates the withdrawal. An asset approval used for a deposit is not automatically the same permission as spending someone's vault shares.
Conversion, preview and limit answer different questions
The specification gives convertToAssets and convertToShares an idealized conversion role. They exclude operation fees and should not reflect the caller's particular execution conditions. Both round down. They are useful for displaying an accounting relationship, rather than certifying a specific exit.
The matching preview method is closer to the operation. It includes applicable deposit or withdrawal fees under the standard's rules. The standard also defines bounds between a preview and its matching operation in the same transaction. A preview read earlier does not lock the later result or reserve funds. Our transaction-simulation guide explains the broader problem of treating a state-dependent preview as a future guarantee.
These previews intentionally ignore the corresponding deposit or withdrawal limits. Those belong to maxDeposit, maxMint, maxWithdraw and maxRedeem. The last two return different units: maxWithdraw(owner) returns assets, while maxRedeem(owner) returns shares. They must account for the applicable global and owner-specific limits; a fully disabled exit returns zero.
A preview and a zero maximum can therefore coexist without contradicting each other. One prices the hypothetical operation; the other restricts how much can currently proceed. An interface can also be implemented incorrectly or maliciously. Familiar function names do not prove compliance.
A fictional conversion with actual rounding rules
For a concrete worksheet, use OpenZeppelin Contracts v5.5.0, specifically its ERC4626 implementation. This is a pinned code example, not identification of a live vault's deployed code or a claim that every vault uses this version.
Assume a simple vault using the unmodified conversion functions and default decimal offset of zero. Its fictional underlying token A has zero decimals, so one A is also one raw asset unit. Share token S likewise has zero decimals. The deliberately coarse units make rounding visible. Real token and share decimals need their own scales; see the token-decimals guide.
Assume totalAssets() is 1,099 A, total share supply is 999 S, and one owner holds 100 S. Exclude entry and exit fees, unusual token behavior and other activity. In this base implementation, totalAssets() reads the underlying token balance held by the vault; a strategy can override that behavior.
The selected conversion code adds one virtual asset unit and 10^offset virtual share units. With offset zero, the adjusted amounts are 1,100 asset units and 1,000 share units. Those virtual units are conversion terms, not extra tokens minted to the owner or extra cash in the contract.
Assets for shares use shares × 1,100 / 1,000; shares for assets use assets × 1,000 / 1,100, with the operation's required rounding:
| Independent preview at the same fictional starting state | Calculation | Result |
|---|---|---|
| Redeem 100 S | Floor of 100 × 1,100 / 1,000 | 110 A received |
| Deposit 1 A | Floor of 1 × 1,000 / 1,100 | 0 S received |
| Mint 1 S | Ceiling of 1 × 1,100 / 1,000 | 2 A required |
| Withdraw 1 A | Ceiling of 1 × 1,000 / 1,100 | 1 S burned |
| Redeem 1 S | Floor of 1 × 1,100 / 1,000 | 1 A received |
The rows are separate alternatives, not consecutive actions. Rounding down means taking the lower whole number; rounding up means the higher whole number. A positive deposit can round to zero shares in this coarse example. That is a loss-producing result to detect, not a suggested transaction.
If the 100-S redemption were allowed and completed under these assumptions, the real totals would fall to 989 A and 899 S, and the owner's 100 S would be burned. This accounting does not establish profit: we have supplied neither the owner's acquisition cost nor an external market price.
Do not replace the pinned formula with shares × totalAssets / totalSupply and expect identical small-number results. Other implementations can use different permitted conversion designs. OpenZeppelin's vault guide discusses virtual offsets, rounding and donation-related exchange-rate risk; none supplies a blanket safety certificate.
A positive preview can remain while an exit is disabled
Now consider a separate hypothetical customization of that vault. It disables redemption and correctly reports maxRedeem(owner) = 0. Keep the conversion accounting unchanged. previewRedeem(100) can still return 110 A because its job excludes that limit. An attempted positive redemption must respect the zero maximum.
That restriction is a fictional extension, not a feature of the unmodified OpenZeppelin base. In the pinned base, maxRedeem returns the owner's share balance, and maxWithdraw calls previewRedeem(maxRedeem(owner)). The public redeem and withdraw paths check their respective maxima before the shared withdrawal workflow. Restrictions added by an extension need consistent limits and previews; the base code's comments explicitly warn about inconsistent overrides.
Fees can also create a legitimate difference between conversion and operation previews. A fee-free conversion is not an additional payout to add to a fee-inclusive redemption result. Use the matching preview and check the actual implementation's fees, limits, permission requirements and token-transfer behavior. A positive view result by itself does not prove that a later call will succeed.
Queued vaults need their own interface rules
This worksheet concerns the synchronous ERC-4626 conversion pattern. ERC-7540 adds asynchronous request flows with Pending, Claimable and Claimed stages. For its asynchronous redemption flow, previewRedeem and previewWithdraw must revert. Those functions are not universal quote endpoints for every product described as a vault.
A pending request is different from an immediately redeemable share balance. Check whether the particular vault uses requests, what becomes claimable, and how its exchange rate is determined. The specification does not turn a pending request into a universal waiting period or fixed payout.
A vault-reading worksheet
Keep the network, exact vault contract and underlying asset() together. Record asset and share decimals, the owner's share balance, the relevant accounting state, and which of the four operations the screen is describing. Then pair its preview with its maximum in the correct units, rather than presenting conversion value as cash available now.
Check fees and whether the flow is synchronous or request-based. An upgradeable implementation needs its current code and configuration, rather than just a known interface. Leave unavailable inputs unknown; this reading exercise needs no wallet connection, approval or deposit.
Our LP-share explainer follows the separate Uniswap pool-reserve example. A vault share is another accounting layer with its own conversion and exit rules. Read that layer before equating the receipt token, the underlying asset and a withdrawable amount.
Sources
Primary specifications, the pinned implementation and its interface were checked November 1, 2026, Asia/Tbilisi. Figures and the disabled-exit customization are fictional. The worksheet uses exact integer arithmetic; no live vault state, wallet, RPC request, approval, deposit, simulation or withdrawal was tested. This is a mechanics explanation, not a contract audit, yield recommendation or assurance of recoverability.
- ERC-4626: Tokenized Vaults: asset/share units, operations, conversion, previews, maxima and rounding requirements.
- OpenZeppelin: ERC-4626 guide: implementation context, rounding, virtual offsets and fee customization.
- OpenZeppelin ERC4626.sol, v5.5.0: the exact base conversion, limit checks and withdrawal workflow used for the worksheet.
- OpenZeppelin IERC4626.sol, v5.5.0: interface signatures and documented operation semantics, read alongside the fuller specification.
- ERC-7540: Asynchronous vaults: request lifecycle and overridden preview behavior for asynchronous flows.
See something wrong? Brokzi logs material changes. Prepare a correction note.




