ERC-7540 Alignment¶
ERC-7540 (Asynchronous Tokenized Vault Standard) is an extension of ERC-4626 that formalizes vaults where deposit or redemption is not atomic within a single transaction.
Overview¶
Vault-K-NO is structurally aligned with ERC-7540. The request/pending/cancel/queue-visibility surface maps directly onto the ERC-7540 two-phase pattern. Three aspects diverge from strict compliance due to the vault's yield mechanics — these divergences are intrinsic and cannot be resolved by interface wrapping alone.
Alignment Summary¶
| ERC-7540 Surface | Vault-K-NO | Status |
|---|---|---|
| Request phase | requestWithdraw(shares, receiver) |
✅ Direct |
| Pending state | getRequest(requestId) |
✅ Direct |
| Queue visibility | queueDepth(), getRequest() readable by anyone |
✅ Direct |
| Operator fulfillment | processWithdrawals(maxCount) |
✅ Direct |
| Cancellation | cancelWithdraw(requestId) |
✅ Direct |
| Request identifier | requestId (uint256) |
✅ Direct |
| Fulfillment price | Determined at keeper processing time | ⚠️ Partial |
| Capacity signalling | remainingDailyLiquidity() as proxy |
⚠️ Partial |
| Open claimability | Permissioned keeper only | ⚠️ Partial |
Sections¶
- Why Not ERC-4626 — why synchronous vault standards don't apply
- Structural Alignment — where the two standards match
- Interface Mapping — function-level correspondence table
- Points of Divergence — three specific areas that deviate from strict compliance
- Integrator Guide — how to consume this vault correctly via a 7540-compatible interface