Crypto Gloss

ERC-4626

ERC-4626 is an Ethereum standard for tokenized vaults: smart contracts that accept one underlying ERC-20 asset and issue ERC-20 shares representing a claim on the vault’s assets. The standard gives applications a common interface for deposits, withdrawals, and share conversions. It does not choose a vault’s investment strategy, produce yield by itself, or guarantee that a depositor will make a profit.

How an ERC-4626 vault works

A user deposits an asset such as USDC and receives vault shares. Those shares represent a proportional claim, with the vault’s accounting determining how many assets a share can redeem. If a strategy earns more than it loses and pays in fees, the assets-per-share value may rise; losses, fees, and other strategy outcomes can also reduce it. A share balance does not automatically increase like a rebasing token.

The standard defines paired operations such as deposit and mint for entering, and withdraw and redeem for exiting. It also specifies conversion and preview methods. Conversion methods provide standardized estimates; preview methods model a particular operation’s expected result. Neither replaces checking limits, fees, slippage, transaction state, or the vault’s own withdrawal rules.

What the standard does—and does not—standardize

Because vault shares are ERC-20 tokens and the vault exposes familiar methods, wallets, dashboards, and other contracts can often integrate with less custom code. That improves interoperability, but it does not mean every vault is interchangeable or that integration always requires zero extra work. Different strategies, fees, deposit caps, withdrawal delays, unusual assets, and asynchronous processes can still require adapters or special handling.

ERC-4626 standardizes how a vault is called, not how it invests. A project’s receipt or staking token is not automatically ERC-4626 just because it represents a deposit or earns rewards; its contract must implement the standard’s interface and behavior.

Risks and common misconceptions

Vault shares can lose value. A strategy can underperform or suffer losses, assets can become temporarily unavailable, and smart-contract, oracle, underlying-token, and governance risks remain. The standard is not an audit or a safety certification.

One known implementation risk is the first-deposit inflation attack. In a poorly protected, empty vault, an attacker may deposit a small amount and donate more underlying tokens directly to the contract, changing the share conversion rate. Rounding may then leave a later depositor with fewer shares than expected. Implementations use different mitigations, including virtual assets and shares or decimal offsets; users and integrators should still check expected shares and apply suitable slippage limits. The exact protection depends on the implementation.

Also, “preview” does not mean a guaranteed quote: the vault’s state can change before a transaction is mined. Depositors should understand the strategy, fees, liquidity, and contract risks rather than treating a standardized interface as a promise of yield.

Social Media Sentiment

In an August 10, 2026 r/ethdev discussion about testing an ERC-4626 inflation-attack scenario, commenters focused on implementation details and broader security testing. It is one developer thread, not a survey of the whole Ethereum community, but it illustrates why developers discuss the standard alongside rounding, slippage, and vault-specific safeguards.

Last updated: 2026-10

Related Terms

See Also

Sources