Choose ERC-4626 when deposits and redemptions can settle in the same transaction — the vault holds liquid on-chain assets. Choose ERC-7540 when they cannot — subscriptions wait for cash and NAV, or redemptions wait for liquidity windows. Most real-world asset funds fall into the second group, which is why ERC-7540 has become the go-to standard for on-chain fund wrappers, while ERC-4626 remains dominant in DeFi.
Key takeaways
- ERC-4626: synchronous
deposit/mint/withdraw/redeemwith exact previews. - ERC-7540: adds
requestDeposit/requestRedeem, pending and claimable states, operators; previews revert for async paths. - ERC-7540 can be async in one direction only — e.g. instant deposits, queued redemptions.
- Integrations differ: DeFi protocols expecting ERC-4626 must be adapted for async behaviour.
Comparison table
| Criterion | ERC-4626 | ERC-7540 |
|---|---|---|
| Settlement | Same transaction | Request → fulfilment → claim |
| Pricing | Known at execution | Determined at fulfilment (NAV strike) |
| Previews | Exact | Revert for async flows |
| Liquidity need | Must hold or access instant liquidity | Can match fund settlement cycles |
| Operator model | Standard ERC-20 approvals | Operators manage requests for controllers |
| Share token | Vault itself | Can be separate (via ERC-7575) |
| DeFi composability | Very high | Growing; needs async-aware integrations |
| Typical assets | Lending markets, LP strategies, liquid wrappers | T-bill funds, private credit, real estate funds |
Decision guide
- Can you always honour redemptions instantly? If yes, ERC-4626. If not without a large buffer, ERC-7540.
- Is NAV computed off-chain at a cut-off? ERC-7540 fits.
- Do subscriptions require KYC or cash settlement first? ERC-7540.
- Is DeFi collateral use the main goal? ERC-4626 shares integrate more easily — some issuers offer an ERC-4626 wrapper over an ERC-7540 fund with a liquidity buffer.
Hybrid patterns
- Async redemptions, sync deposits — common for credit pools.
- Liquidity buffer + ERC-4626 front-end — small redemptions instant, large ones queued via a separate path.
- Multi-asset entry points with a shared share token via ERC-7575.
Compliance
Both standards treat shares as ERC-20 tokens; neither restricts holders. For regulated funds, gate requests and share transfers with identity checks, or make shares a permissioned token. See tokenized treasuries and money-market funds.
Investor experience compared
ERC-4626 (synchronous)
1. Investor approves USDC.
2. Investor calls deposit; shares arrive in the same transaction at the current price.
3. Later, investor calls redeem; USDC arrives immediately.
ERC-7540 (asynchronous)
1. Investor calls requestDeposit; USDC moves into the vault and the request shows as pending.
2. At the next NAV strike, the fund fulfils the request; it becomes claimable.
3. Investor (or custodian/relayer) claims shares.
4. For redemption: requestRedeem → pending until the next window → claimable → claim USDC.
The asynchronous journey needs clear status displays and notifications in the investor portal, but it accurately reflects how the underlying fund operates — avoiding hidden liquidity mismatches.
Liquidity buffer design for “mostly instant” redemptions
Some issuers want ERC-4626-like UX on an RWA fund. A buffer approach:
- Keep, say, 5–10% of assets in on-chain cash.
- Serve small redemptions instantly from the buffer.
- Route large redemptions through an ERC-7540 request path.
- Replenish the buffer from fund dealing cycles.
This gives investors speed for typical sizes while protecting the fund from runs.
Frequently asked questions
It extends ERC-4626; synchronous parts behave the same, but async parts require integrators to handle requests and reverting previews.
Usually ERC-7540, because subscriptions and redemptions follow fund settlement cycles.
Yes, with an upgrade or migration, but integrations and user flows change, so plan it with holders and partners.
ERC-7540 builds on ERC-7575’s share-separation model, though a vault can still be its own share token.
Increasingly, but some aggregators assume ERC-4626 behaviour. Confirm integration support before relying on it for distribution.
Neither is inherently safer; ERC-7540 avoids pretending illiquid assets are instantly redeemable, which reduces a key economic risk.
NUVZ is the RWA and Web3 engineering brand of ESS ENN Associates (est. 1993). Our team has designed and shipped tokenization platforms for real estate, education loans, solar PPAs, energy, carbon credits, bank deposits and trade documents. About us · Case studies
This article is for general information only and is not legal, tax or investment advice. Token standards evolve — always confirm the current status of an ERC at eips.ethereum.org and take advice from qualified counsel in each jurisdiction before issuing tokens.
