ERC-4626 Explained: How Yearn Pushed Standard DeFi Vaults in 2026

ERC-4626 is an Ethereum standard for tokenized vaults. A vault is a smart contract that takes in one token, called the underlying asset, and gives depositors shares that represent a claim on the vault's pooled assets. The standard defines a common set of functions for deposits, withdrawals, share conversion and reporting total assets.

Before this kind of standard, every yield vault had its own interface. A wallet, aggregator or lending market that wanted to integrate with ten vaults had to write ten custom integrations. Each one could behave slightly differently when it came to rounding, fees or withdrawals.

ERC-4626 builds on the ERC-20 token standard, so the vault shares themselves behave like normal tokens. You can hold them in a wallet, send them, or use them as collateral in other protocols if those protocols accept them.

The standard does not decide what a vault invests in. A vault can lend money, provide liquidity, hold tokenized treasuries or run a complex set of strategies. ERC-4626 only describes how the vault accepts money and reports its value.

Yield vaults grew quickly in DeFi, and many of them were built by different teams with different code. A depositor moving between vaults had to learn new screens, new share math and new withdrawal rules. Aggregators and front ends had to maintain a separate adapter for each one.

A standard interface lowers that friction. If two vaults expose the same functions and return values in the same way, a tool can compare them, route deposits and show balances without custom logic for each contract.

Standardization also helps risk teams. When the accounting is consistent, it is easier to write monitoring scripts that check total assets, share prices and withdrawal capacity across many vaults at once.

The trade-off is that a standard can make it easier to assume two vaults are alike when they are not. Two vaults can share an identical interface and still hold very different strategies, collateral or admin powers. The standard reduces integration work, not investment risk.

The core idea is share-based accounting. When you deposit, the vault calculates how many shares to mint based on the current ratio of shares to assets. When you redeem, it burns your shares and returns assets based on the same ratio. As the vault earns yield, total assets rise while the share supply stays the same, so each share is worth more over time.

The standard includes deposit and mint, which both add funds but differ in whether you specify the asset amount or the share amount. It also includes withdraw and redeem, which work the same way on the exit side. Preview functions such as previewDeposit and previewRedeem let a front end show what you would receive before you sign a transaction.

Conversion functions, such as convertToShares and convertToAssets, expose the current exchange rate. Limit functions such as maxDeposit and maxWithdraw tell you whether a vault is accepting new money or has a cap in place.

Rounding rules matter. The standard specifies which way rounding should go so that the vault does not give away value to depositors through small errors. Integrators should read the details in the official specification rather than relying on memory.

Yearn Finance is one of the best-known yield aggregators in DeFi. Its early product, the yVaults, let users deposit tokens and had the protocol move funds between strategies to chase returns. Older Yearn coverage describes a structure with a 20 percent performance fee on yield each time a vault harvested a strategy, plus a 2 percent management fee. Check current Yearn documentation for the fees on any specific vault, since these can change.

In its later design, Yearn has pushed for a vault framework built around ERC-4626. The aim is for vaults to present a familiar interface to users and other protocols, and for strategies to plug into that framework in a consistent way.

Yearn has also publicly described its vaults as a way to package strategies for other teams. Under this model, a curator or developer can deploy a vault with their own strategy and risk settings while still using the shared interface.

The results used for this guide do not include the full text of any single Yearn announcement about vault standardization. For the exact wording, scope and timing of that effort, read Yearn's own documentation and announcements directly.

Yearn's later vault design separates the vault contract from the strategy contract. The vault handles user deposits, withdrawals and share accounting. The strategy handles the actual investing. Under this split, the strategy can itself be tokenized and managed by defined roles rather than one all-powerful admin.

Role-based permissions are an important part of this model. Different addresses can be given different powers, such as adding a strategy, changing a debt limit, harvesting yield or pausing activity. Reviewing who holds each role is one of the most useful checks a depositor can do.

The design aims to let more than one team operate vaults on the same framework. A protocol or risk manager can create a vault, set its strategy and allocation rules, and publish it for users, while the shared contracts handle the common mechanics.

Permissionless deployment sounds open, and it is, but it also means quality varies. A vault can be deployed by anyone who meets the technical requirements. Users should judge each vault on its own team, audits, configuration and track record rather than on the framework name alone.

Vaults are not always single-chain. Some designs keep the user-facing vault on one network and deploy strategies on other networks where yield sources exist. Yearn's coverage has described a model where a remote strategy receives bridged assets and deposits them into a local ERC-4626 vault on that chain, then periodically reports its results back.

This kind of setup adds layers. There is the vault contract on the home chain, the bridge that moves assets, the remote strategy, and the local vault where funds sit. A failure at any one point can affect depositors, even if the main vault code is sound.

If you use a cross-chain vault, look at which bridges it relies on, how reports from remote strategies are verified, and what happens to funds if a bridge is paused or a chain has an outage. Ask how much value sits on each chain at any time, and whether that exposure is shown publicly.

Cross-chain designs can offer broader yield access, but they also widen the attack surface. Treat the extra moving parts as part of the risk you accept, not as a background detail.

Yearn Finance has faced security incidents in its history. Coverage in late 2025 described an exploit involving an infinite-mint bug that drained value from the protocol, with some of the proceeds reported as sent to Tornado Cash. Earlier years had their own bad events, including incidents that users remember as vault failures. Past incidents do not settle the current safety of any vault, but they show why depositors should follow what happened and how the team responded.

The main risks for any ERC-4626 vault include smart contract bugs, mistakes in the strategy, oracle or pricing errors, bad debt in lending positions, bridge risk, and admin key abuse. A standard interface does not remove any of these.

An infinite-mint bug is especially serious because it can let an attacker create shares or tokens without backing them. Share accounting, token supply checks and access controls are where these bugs often hide, which is why audits and bug bounty programs matter.

A useful habit is to read post-mortems from any vault team you use, and to note whether they paid users, how they explained the cause, and whether they changed the design afterward. Silence after an incident is a warning sign.

Before you deposit into any ERC-4626 vault, work through a short checklist.

• Confirm the contract address from the official project site or documentation, and check it on a block explorer.
• Read the vault's audit reports and note their dates and scope.
• Identify the underlying asset and the strategy in plain terms.
• Check the fee schedule, including performance and management fees.
• Find out who holds admin and strategy roles, and whether a timelock applies to changes.
• Test the withdrawal path with a small amount if possible.
• Look at any withdrawal queue, lock-up or caps.
• Review how the vault behaved during past market stress.
• Check whether the team has a clear incident response and a public history of disclosures.
• Decide how much you can afford to lose if the vault fails entirely.

If a vault cannot answer these questions in its documentation, that is useful information in itself. Many users skip this step because the interface looks familiar, but familiarity is not a security check.

Remember that share tokens can also be transferred. Make sure you know which token contract you are holding, because scam tokens sometimes copy the name and symbol of a legitimate vault share.

Yield numbers change constantly. Vault returns, total value locked, fee levels and strategy allocations can all shift from week to week or even hour to hour. This guide does not state current figures for any vault, because any number written here would go stale quickly.

To see current data, use the vault's own interface and documentation, then check the contract on a block explorer for total supply and recent activity. Public analytics dashboards can show total value locked and historical share prices, but compare their numbers against on-chain data before relying on them.

When you compare vaults, put them on the same basis. Look at the net yield after fees, the asset you are exposed to, the chain, the withdrawal terms and the number of parties who can change the strategy. A higher advertised yield often reflects more risk, a newer strategy or a temporary incentive.

If the yield comes mostly from token incentives, check how long those incentives last and what happens to the yield when they end. Incentive-driven returns can fall sharply once the rewards stop.

Some vault teams and curators publish their strategies under names that suggest careful risk management. Gauntlet is one example of a DeFi risk manager that curates non-custodial yield vaults for other businesses. Morpho and Euler V2 use curator and vault designs for lending, where a curator chooses which markets a vault can use and sets limits. Those models give users a different set of questions to ask, such as how the curator is paid, how markets are added, and what limits apply.

Aave V3 and Compound V3 are established lending protocols with their own deposit and borrowing mechanics, and they are useful reference points for understanding how lending rates and collateral work underneath many vaults. Convex Finance and vfat.io are yield platforms that package or route liquidity positions, and both add a layer of contracts on top of the underlying pools.

Whenever a vault relies on another protocol, you inherit that protocol's risks too. Read about the underlying venues as well as the vault itself.

This guide does not recommend any product. Use the names above as starting points for your own research, and verify all details in each project's current documentation.