Contents
Say "vault" in DeFi and you could be talking about two very different products. One is a pool of stablecoins lent out against collateral, operating under rules enforced by smart contracts. The other is a fund in all but name: a manager decides where the money goes, and the contracts keep the books. The word suggests a safe, and neither of them works like one.
Both show a yield on the front end and both carry the same label, so people compare them as if they were the same thing. They are not interchangeable.
One standard, two businesses
Both kinds are commonly built on ERC-4626, the Ethereum standard whose official title is, quite literally, Tokenized Vaults.1 Its authors wrote it in late 2021 because every yield product exposed its own interface. They cited lending markets, aggregators and interest-bearing tokens as examples, and noted that each protocol integrating them had to build its own adapters.1
The standard defines the interface and little else. A depositor calls deposit or mint to put in an asset and receive shares, then withdraw or redeem to hand shares back and take the asset out. totalAssets reports how much the vault manages, convertToShares and convertToAssets translate between the two, and a set of preview and max functions tell an integrator what a call would return and which limits apply.1 A wallet or an aggregator that supports the standard can integrate a much wider range of vaults without building a separate interface for each one, which helps explain how quickly the word spread.
What the standard leaves out matters more. Its authors chose not to specify how a vault accounts for its assets or where it allocates them, and wrote that vaults are expected to be "treated as black boxes on-chain and inspected off-chain before use".1 The specification even describes totalAssets as an estimate useful for display, which does not have to be exact.1 Two contracts can expose exactly the same functions while one lends USDC on Morpho and the other runs a basis trade on a centralized exchange. The interface tells you how to get in and out, and nothing about who carries the risk once you are in. The two families described below are practical distinctions; the standard itself draws no line between them.
ERC-4626 also assumes that a deposit or a withdrawal completes in a single transaction, although its authors already expected some vaults to require a request before a withdrawal.1 ERC-7540, published in 2023 as an extension, standardizes that request-then-claim flow.2 A request stays pending until the vault makes it claimable, and the depositor then claims the shares through deposit; redemptions follow the same path through requestRedeem. When a request becomes claimable, and at what price, is left to each vault.2 On the deposit side, the flow looks like this:
// ERC-7540: two steps for the depositor, one for the vault in between.
// 1. Request. The assets move into the vault and wait.
uint256 requestId = vault.requestDeposit(assets, controller, owner);
// 2. The vault prices the request and makes it claimable.
// When and how is up to each implementation.
// 3. Claim. deposit() mints the shares to the receiver.
uint256 claimable = vault.claimableDepositRequest(requestId, controller);
uint256 shares = vault.deposit(claimable, receiver, controller);
Lending vaults: a pawnshop with public rules
A lending vault works a lot like a pawnshop. Borrowers bring collateral, walk out with a loan worth less than what they left behind, and pay interest until they repay. The vault's depositors supply the cash and earn that interest, minus the curator's fee.
In DeFi the collateral is a token, for example ETH or a wrapped version of bitcoin, and the loan is often a stablecoin such as USDC. The curator picks which lending markets the vault can supply, each with its own collateral, oracle and maximum loan-to-value, and caps how much of the vault each one can take.
Morpho Vault V2 shows how far this can be written into the contract. The work is split between roles held by different addresses:3
- The owner appoints the curator and the sentinels, and cannot move the assets.
- The curator decides which markets and protocols the vault may reach, through connectors called adapters, and caps its exposure to each collateral, oracle or market.
- The allocator moves the money between those destinations, within the caps.
- A sentinel holds emergency powers that can only reduce risk, covered further below.
Most of the curator's changes sit behind a timelock that can run up to three weeks, so depositors see them coming and can leave before they apply.4 Fees are capped in the contract too: up to 50% of the interest earned as a performance fee, and up to 5% a year as a management fee.4
A pawnshop sells the watch if its owner misses the repayment date. DeFi loans have no such date. A position is liquidated when it no longer meets the market's collateral requirements, measured with oracle prices, which can happen because the collateral falls or because the debt grows, through accrued interest or a rise in the borrowed asset. Liquidations are permissionless, and liquidators earn an incentive for repaying the debt and taking the collateral.
Because every position lives onchain, the vault's accounting rests on public state and oracle prices that anyone can check at any block. Withdrawals go through as long as the vault holds idle cash or its markets still have liquidity. When a market runs dry, withdrawals from it stall, and its interest rate model raises the cost of borrowing as utilization climbs. That pushes borrowers to repay and draws in new lenders, though nothing guarantees how fast. Vault V2 adds a last resort: a depositor can leave in kind, swapping vault shares for a direct position in an underlying market, at a penalty of at most 2%.4
What a run on lending vaults looks like
November 2025 gave a clear picture of that last point. A yield-bearing dollar token that several lending platforms accepted as collateral lost most of its value after its issuer disclosed a large loss at an outside fund manager. On Morpho, the direct damage was small: according to Chorus One, one curated vault out of roughly 320 held the token, for about $700,000 of bad debt.5
The run that followed was the harder test. Depositors pulled money from many vaults at once, including large stablecoin vaults run by Steakhouse and Gauntlet that had never held the token. Each vault paid out its idle cash first. Once that was gone, borrowing in the affected markets reached 100% of the available liquidity, withdrawals waited, and interest rates climbed as high as 190% to push borrowers to repay.5 Most vaults recovered within hours, and about 80% of withdrawals were completed within three days.5
Chorus One's reading is that the design did its job, because isolated markets kept the loss in one place. The same isolation explains the queue: a curated vault can only draw on its own markets, so its liquidity can run out quickly even when its losses are close to zero.5
Fund vaults: an onchain back office
A fund vault starts from the other end. Its smart contracts can automate much of the back-office work a fund administrator and a transfer agent would do: keeping the share register, processing subscriptions and redemptions, accruing fees and applying the net asset value (NAV) used to price shares. Investment decisions stay with the manager, who can deploy across DeFi protocols, tokenized T-bills, other chains or an account on a centralized exchange (CEX), within whatever the mandate allows.
Some of those positions can't be seen onchain at all. A perp position on a CEX is the obvious case. The manager can give a valuation agent read-only API access to the account, which helps, but the data still comes from the exchange and reaches the vault through people. So the NAV is usually calculated or reported at set intervals, by the manager or an appointed valuation agent, and deposits and redemptions may then be processed in batches at that price. In ERC-7540 terms, a request waits as pending until the next valuation, then becomes claimable at the new price.2
Anyone who has worked at a fund will recognize dealing days in the result. An open-ended fund publishes when it deals and its cut-off time, may ask for notice before large redemptions, and relies on an administrator to strike the NAV. A fund vault has to answer the same questions: how often the NAV is reported and by whom, how long a request can wait, and what happens when redemptions exceed the cash on hand. Some of the answers sit in the contract, and the rest in the documents the manager publishes.
Some fund vaults also support synchronous deposits and withdrawals when their strategies can be valued onchain and enough liquidity is on hand. Either way, the manager here is overseeing a portfolio, which is a very different job from setting a lending vault's risk parameters.
Side by side
| Lending vault | Fund vault | |
|---|---|---|
| Strategy | Supplies assets to approved lending markets | Deploys capital within the mandate |
| Return | Borrower interest, minus fees | The strategy's performance, positive or negative |
| Valuation (NAV) | Onchain accounting and oracle prices | Calculated or reported at set intervals |
| Liquidity | Depends on liquidity in the underlying markets | Synchronous or request-and-claim, depending on the strategy |
| Curator or manager's role | Risk parameters, allocations and caps | Selecting and managing investments |
| Fees | Curator fees; capped at 50% of interest and 5% a year on Morpho Vault V2 | Management and performance fees, as set by the manager |
| Main risks | Bad debt, oracle failure, liquidity squeezes | Manager error or misconduct, valuation, venue and protocol risk |
| You rely on | Contracts, oracles and the curator's parameters | The manager, the valuation process and the controls around them |
Rules or people
The Binance hot-wallet hack at the end of October showed the split in real time. Between 20:58 and 21:01 UTC on 29 October, a wallet linked to the attacker supplied 60 million USDT to Aave V3 on Ethereum and borrowed 19,762 ETH, worth about $44.6 million at the time.6 It was trading exposure to a stablecoin its issuer can freeze for ETH, which has no issuer. Decrypt found no sign that Aave itself had been exploited; the attacker used ordinary lending operations.7 With the debt in ETH, it was a rise in ETH that would have pushed the position toward liquidation. Aave is a pooled lending protocol rather than a curated vault, but the episode draws the same line.
The response came from people around the code. Tether and Circle froze addresses linked to the hack.7 8 On Aave, LlamaRisk, Aave Labs, TokenLogic and Certora formed a response group, and guardian multisigs, small groups of key holders with limited emergency powers, froze 175 reserves on V3 across 16 networks and 117 on V4 across four networks between 21:42 and 23:04 UTC.9 6 A freeze blocks new supply and new borrowing. Repayments, withdrawals and liquidations kept running, so no position was locked.6 The group chose a freeze over cutting supply and borrow caps because the guardians could reverse it at once, whereas restoring cut caps would have taken a governance vote and about five days.6
According to LlamaRisk, the attacker's position held about $59.9 million of USDT against $43.8 million of debt and never put Aave's suppliers at risk.9 The freeze still had a cost that lending depositors will recognize: suppliers pulled stablecoins out, and utilization on those reserves rose to between 92% and 100%.6 Aave lifted the freeze the next day and said its contracts had not been affected. USDT, USDC and several other assets held across the attacker's wallets stayed at zero loan-to-value for a while, so they could not back new borrowing.10 Each of those actions narrowed what the markets would accept, and none of them moved anyone's funds.
A lending vault's guarantees come from parameters nobody can change overnight, which is why depositors trust them, and the same rigidity means the vault won't improvise when a parameter turns out to be wrong. Emergency powers exist (Morpho Vault V2 has a sentinel role that can pull allocations, cut caps and revoke pending changes), but they can only reduce risk.3
In a fund vault, the manager can leave a venue that looks shaky, hedge, or move to stablecoins before most people have finished reading the news, and depositors get the benefit of that judgment. They also depend on it, along with the reporting and the checks around the manager: independent valuation, separate roles, and limits on how far a reported NAV can move between updates, which some platforms enforce in their contracts.
Which one is safer depends on the failure you worry about most. A lending vault swaps the manager for parameters; a fund vault keeps the manager and asks depositors to trust the people and the reporting. Real products sit somewhere between the two, depending on how much of the process the contracts enforce and how much rests on someone's judgment.
Converging from both sides
The boundary between the two is becoming less clear. In Morpho Vault V2, curators can add adapters to protocols outside Morpho, which moves those vaults toward the fund end.4 The ones Morpho treats as Morpho Vaults lock their allocations to a registry its governance approves, which keeps them close to the lending end.11
From the other side, fund vaults often park idle cash in lending vaults between settlements. A single deposit can then sit in both: the fund vault holds shares of a lending vault, which lends the cash out against collateral, and the front end shows the word "vault" at every layer. Whatever sits underneath, the label only describes how deposits come in and withdrawals go out.
Four questions to ask about any vault
Before comparing yields, check where the money goes, how it is valued, who can move it and how depositors get out. The two families answer differently.
| Question | Lending vault | Fund vault |
|---|---|---|
| Where does the money go? | Markets and protocols the curator has enabled, within caps | Wherever the mandate allows, onchain or off |
| How is it valued? | From onchain state and oracle prices, at any block | By the manager or a valuation agent, at set intervals |
| Who can move it? | The allocator, within limits the curator sets behind timelocks | The manager, within the mandate and the controls around it |
| How do depositors get out? | At once while the markets have liquidity; otherwise they wait, or exit in kind where the vault allows it | At the next settlement, or at once when the vault supports synchronous withdrawals |
Many vaults answer from both columns, and their documents should say which answer applies to which part of the money.
Frequently asked questions
What is a vault in DeFi? A smart contract that takes deposits in one asset and issues shares that represent a claim on what it holds. Most follow ERC-4626, which standardizes the deposit and withdrawal interface but not the strategy behind it.1
What is the difference between a lending vault and a fund vault? A lending vault supplies its deposits to lending markets within limits set by a curator, and values itself from onchain state and oracle prices. A fund vault runs a fund's back office in smart contracts, while a manager invests wherever the mandate allows and the NAV is often reported at set intervals.
What is ERC-7540? An extension of ERC-4626, published in 2023, that standardizes asynchronous deposits and redemptions. A request is submitted, becomes claimable once the vault processes it, and is then claimed.2
Can depositors always withdraw from a lending vault at once? Only while the vault holds idle cash or its markets have liquidity. When utilization reaches 100%, withdrawals wait until borrowers repay or new lenders arrive. During the November 2025 run, about 80% of withdrawals from Morpho vaults were completed within three days.5 Morpho Vault V2 also allows an exit in kind, at a penalty of at most 2%.4
Why is a fund vault's NAV reported rather than computed onchain? Some of its positions, such as a perp position on a centralized exchange, cannot be read by a smart contract, so their value has to be reported by the manager or a valuation agent. Some platforms limit how far a reported NAV can move between updates.
Further reading: The Vault Decade: how onchain asset management evolved
Sources
-
ERC-7540: Asynchronous ERC-4626 Tokenized Vaults. ↩ ↩2 ↩3 ↩4
-
Chorus One, DeFi Curators in 2025: Navigating Chaos, Building Resilience, 2 December 2025. ↩ ↩2 ↩3 ↩4 ↩5
-
Altcoin Buzz, Aave Freezes 292 Reserves After Binance Hot Wallet Drain, 1 November 2026. ↩ ↩2 ↩3 ↩4 ↩5
-
Decrypt, Binance Hacker Hunts for Exit Ramps as DeFi Exchanges Pause Markets, 29 October 2026. ↩ ↩2
-
Cointelegraph, Binance hack rattles markets as BNB falls 8%, 29 October 2026. ↩
-
Aave governance forum, Binance hot wallet exploit: Aave's response (LlamaRisk). ↩ ↩2
-
Odaily, Aave V3 and V4 have fully lifted market freezes, 30 October 2026, relaying Aave's statement on X. ↩