ERC-7540 Explained: Async Vaults for Real-World Assets

Introduction

DeFi vaults were designed for a world where everything settles in the same block. You deposit USDC, shares are minted, and the transaction is complete before the next block is produced. For highly liquid strategies this works. ERC-4626, the tokenized vault standard, codified this pattern and became the backbone of DeFi's vault ecosystem.

But as onchain asset management moves beyond liquid DeFi strategies into tokenized treasuries, private credit, and institutional fund structures, that assumption breaks. Real-world assets don't settle in 12 seconds. They settle in days. Wire transfers take T+1 or T+2. NAV calculations depend on off-chain valuations. KYC checks happen outside the blockchain. Forcing these workflows into a synchronous vault creates architectural failures: unbacked share issuance, settlement reverts, and compliance deadlocks.

ERC-7540 solves this. Finalized in June 2024 and now recognized on ethereum.org, it extends ERC-4626 with asynchronous deposit and redemption flows. The standard introduces a request-then-claim pattern that decouples user intent from execution, enabling vaults to handle settlement delays, batch processing, and external valuation without breaking the onchain interface.

Lagoon builds its entire vault infrastructure on ERC-7540. This article explains what the standard does, how it differs from ERC-4626, and why it is the technical foundation for institutional-grade onchain funds.

Why ERC-4626 Is Not Enough

ERC-4626 standardized how tokenized vaults work on Ethereum. It defined a common interface for deposits, withdrawals, share minting, and share burning, and it did this well for synchronous, liquid strategies. Protocols like Yearn, Morpho, and Aave adopted it widely.

The problem is the atomicity assumption. ERC-4626 requires that every deposit and withdrawal completes within a single transaction. When you call deposit(), the vault must immediately accept your assets and mint shares. When you call redeem(), shares are burned and assets are returned, all in the same block.

This breaks down for three categories of assets and strategies:

• Real-world assets with T+1 or T+2 settlement. Tokenized treasuries, private credit, and structured products depend on bank wires and custodial transfers that take days, not seconds. Minting shares before settlement confirms leaves the vault under-collateralized.

• Strategies requiring external valuation. Any vault that depends on off-chain NAV inputs (a third-party valuation provider, an audited price feed, or a manual appraisal) cannot determine the correct share price at the moment of deposit. The price needs to be calculated after the request, not during it.

• Institutional compliance requirements. KYC/AML checks, investor eligibility verification, and regulatory reporting cannot execute within the gas limit of a single Ethereum transaction. These processes need a window between request submission and settlement.

Figure 1: Why ERC-4626 breaks for real-world assets, and how ERC-7540 addresses each limitation

ERC-7540 was developed to address exactly these constraints. Co-authored by teams from Centrifuge, Superform, and Maple Finance, it went through over nine months of community review before being finalized as an Ethereum standard in June 2024.

How ERC-7540 Works: The Request-Claim Pattern

The core innovation of ERC-7540 is simple: it separates the request from the fulfillment. Instead of a single atomic transaction, every deposit and redemption goes through a two-step lifecycle.

The Three States

Every request in an ERC-7540 vault moves through three states:

• Pending. The user submits a deposit or redemption request. Assets (for deposits) or shares (for redemptions) are locked in the vault, but no shares are minted or assets returned yet. The request is waiting for processing.

• Claimable. The vault's settlement process completes: a valuation is accepted, NAV is updated, pending requests are processed at the settlement price. The request is now ready to be claimed.

• Claimed. The user calls the standard ERC-4626 claim function (deposit/mint for deposits, redeem/withdraw for redemptions) to receive their shares or assets. The transaction is complete.

Figure 2: The ERC-7540 request-claim lifecycle, both deposits and redemptions follow the same three-state pattern

Forward Pricing

A critical difference from ERC-4626: the exchange rate between assets and shares is determined at fulfillment time, not at request time. When you call requestDeposit(), you don't know exactly how many shares you'll receive. The price is calculated when the vault's NAV updates, typically at the next settlement window.

This is called forward pricing, and it's how traditional funds operate. Subscriptions are submitted before the NAV strike, and allocations happen at the next published price. ERC-7540 encodes this into a standard smart contract interface, preventing arbitrage attacks where users could exploit stale pricing data during off-chain settlement windows.

Delegated Management

ERC-7540 introduces a controller parameter that enables institutional custody workflows. A regulated custodian or fund administrator can act as the controller to manage deposit and redemption flows on behalf of investors, handling KYC verification and compliance checks without needing full custody of the underlying tokens. This is essential for regulated entities operating under fiduciary obligations.

ERC-4626 vs. ERC-7540: Side-by-Side Comparison

The two standards are not competitors. ERC-7540 extends ERC-4626: it is a superset, not a replacement. Understanding when to use each is key to choosing the right vault architecture.

Figure 3: Synchronous vs. asynchronous vault flows: ERC-4626's single-transaction model versus ERC-7540's multi-step request-claim pattern

Vaults can also implement hybrid models: synchronous deposits with asynchronous redemptions, or vice versa. This flexibility lets protocols match their vault mechanics to the actual liquidity profile of their underlying assets.

How Lagoon Implements ERC-7540

Lagoon builds its entire vault infrastructure on ERC-7540. Every vault deployed through Lagoon's permissionless Vault Factory is an ERC-7540 contract with built-in governance roles, fee logic, and settlement mechanics.

The Lagoon Deposit Workflow

Here is how a deposit flows through a Lagoon vault:

• Step 1: Request deposit. The investor transfers assets (e.g., USDC) to the vault via requestDeposit(). Funds enter the Pending state, waiting for settlement.

• Step 2: Propose valuation. A designated price oracle submits an updated total asset valuation for the vault. This can be an automated feed or a third-party valuation provider.

• Step 3: Accept valuation and settle. The vault curator reviews and accepts the proposed valuation. This triggers settlement: fees are computed, pending deposit requests are processed, and shares are minted at the settlement price.

• Step 4: Claim shares (optional). Investors claim their newly minted share tokens. If they don't claim, shares remain in the vault and continue to accrue yield.

The Lagoon Redemption Workflow

Redemptions follow the same pattern in reverse. An investor requests redemption by transferring share tokens to the vault. After the next valuation cycle, the curator accepts the updated NAV and settles. If the vault has sufficient underlying assets available, redemption requests are processed and the investor can withdraw their assets.

This design mirrors traditional fund subscription and redemption cycles. Capital calls are submitted, processed at a cut-off, and allocated at a NAV strike. The difference is that the entire workflow is onchain, auditable, and governed by smart contract rules rather than manual administration.

Governance Separation

Lagoon enforces role-based permissions across every ERC-7540 vault. The vault administrator configures the contract. A designated valuation provider submits NAV updates. The curator accepts valuations and executes investment strategy. A whitelist manager controls investor access. These roles are enforced onchain, creating a separation of powers equivalent to institutional internal controls in traditional finance.

This separation is not just a feature; it's a structural requirement of the ERC-7540 pattern. The async settlement window only works when there's a trusted valuation step between request and claim, and when the entity settling requests is distinct from the entity submitting valuations.

Why ERC-7540 Matters for the Future of Onchain Funds

The tokenized asset market is growing rapidly. BlackRock's BUIDL fund has surpassed $2.9 billion in AUM across seven blockchains. Tokenized U.S. Treasuries alone represent over $8.7 billion. The broader RWA tokenization market has reached approximately $24-36 billion in early 2026, with analysts projecting growth toward $100 billion by year-end. Boston Consulting Group projects the total tokenized asset market could reach $16 trillion by 2030.

Every one of these products needs a vault standard that can handle real-world settlement timelines. ERC-4626 cannot do this. ERC-7540 can.

Lagoon's ERC-7540 foundation supports batch settlement at a single valuation point, delayed settlement and external valuation logic, capital calls and subscription cycles that mirror traditional fund operations, and compliance workflows that happen off-chain between the request and claim phases.

As Ethereum's official recognition of ERC-7540 in January 2025 confirmed, this standard is becoming foundational infrastructure for the next generation of onchain finance.