Async deposits and ERC-7540: why institutional LPs can't use synchronous vaults
Async deposits and ERC-7540: why institutional LPs can't use synchronous vaults
A standard DeFi vault settles instantly: deposit, receive shares, redeem, receive assets, all in one transaction. That works when the underlying assets are liquid and continuously priced. It falls apart the moment the underlying assets are real-world credit, which is exactly why institutional RWA vaults need asynchronous deposits and the ERC-7540 standard that formalizes them.
How it works
The standard vault interface, ERC-4626, is synchronous: every deposit and withdrawal completes immediately, in a single transaction, at a share price the contract can compute on the spot. That requires knowing the vault's exact value at the moment of the transaction, which in turn requires the underlying assets to have a continuous, on-chain-readable price. For a vault holding liquid crypto, that's fine.
Real-world credit breaks the assumption. A vault backed by private credit deals can't compute an exact, up-to-the-second NAV, because its underlying assets don't have continuous market prices, and it can't necessarily honor an instant redemption, because the capital is deployed into loans that only return cash on their own schedules. Forcing real-world-backed capital through a synchronous interface either produces a false NAV or a redemption promise the vault can't actually keep.
ERC-7540 extends the vault standard to handle this with asynchronous, request-based flows. Instead of an instant deposit, an LP submits a deposit request that gets processed at the next valuation and settlement point. Instead of an instant redemption, an LP submits a redemption request that's fulfilled when the vault has the cash and an updated NAV, potentially after a defined notice period. The two-step, request-then-fulfill pattern is what makes it honest: the vault promises to process the request on a real timeline tied to its actual assets, rather than promising an instant settlement it can't back.
Why it matters
Async deposits are what let real-world assets exist inside a vault structure at all without misrepresenting liquidity. An institutional LP allocating to private credit already expects notice periods and periodic valuation, that's normal in traditional private credit funds, and ERC-7540 brings that same honest, request-based rhythm on-chain rather than pretending illiquid assets are instantly redeemable.
The standard also matters because it's a standard. Building async flows ad hoc, every protocol inventing its own request mechanism, would fragment the ecosystem and force every integrator to handle each protocol differently. ERC-7540 gives wallets, dashboards, and other protocols a common interface for async vaults, the same way ERC-4626 did for synchronous ones, which is what makes institutional-grade RWA vaults composable rather than bespoke.
Where this shows up in Rekord
Rekord runs on mature, independently audited third-party vault infrastructure rather than hosting its own vaults, and its LP redemption terms use asynchronous, request-based flows aligned to the actual cash-generation timing of the underlying deals, rather than promising synchronous liquidity the assets can't support. For why that timing mismatch matters in the first place, see Cashflow timing and reward sustainability: why yield isn't the same as cash.