The tokenized-vault standard separates ideal conversions, fee-aware previews and transaction limits. Reading only one function can misstate what a user can receive.
What the primary record establishes
ERC-4626 standardises an interface for vault shares backed by an underlying asset. Its convertToAssets and convertToShares functions describe idealised conversions, excluding fees and actual-exchange slippage, with rounding down. The standard does not promise a fixed share price. Ethereum EIPs — ERC-4626 Tokenized Vaults ↗
Preview functions answer a different question and account for the relevant deposit or withdrawal fees. The specification separately defines maximum-operation functions. A preview is not required to enforce the user or global limits represented by those maximum functions. Ethereum EIPs — ERC-4626 Tokenized Vaults ↗
What the distinction changes
Consider a purely illustrative holding of 100 shares with an ideal conversion of two asset units per share. The displayed conversion is 200 units. It does not establish that withdrawing 200 now is permitted or that all fees have already been deducted.
An integration that presents conversion, preview and available limit as one interchangeable number hides different assumptions. A stronger interface names the operation and explains which result is an estimate, which reflects a fee convention and which describes a current operational ceiling.
What to check before drawing a conclusion
Check the actual deployed contract, supported asset, share balance, allowances and relevant max function. Recompute the appropriate preview near submission and inspect transaction protections. Compliance with an interface is not evidence of sound strategy management or asset backing.
Keep smart-contract risk, economic risk and accounting precision separate. Integer rounding can matter for small positions, while changing vault conditions can alter a later result. WFN’s example is arithmetic; it is not a yield or redemption guarantee.