Why Did a Claimable Vault Exit Produce No New Event?
ERC-7540 claimable state polling is the indexer practice of reading a vault's claimable request views on a bounded schedule, because the standard does not require any event when a request moves from Pending to Claimable. An exit can become claimable with no log at all, so an event-only indexer keeps showing it as pending.
TL;DR — Key Takeaways
- ✓ERC-7540 requires events on request submission and operator changes, but none for the move from Pending to Claimable.
- ✓Detect claimable exits by reading the pending and claimable views for each open controller at one recorded block.
- ✓Bound the poll set and interval, and treat any custom fulfillment event as a hint to read state, not as evidence.
- ✓Keep this monitoring job separate from interface detection: one answers what a vault supports, the other where a request stands.

Why can a request become Claimable without an event?
ERC-7540 mandates only three events: DepositRequest, RedeemRequest and OperatorSet. The move from Pending to Claimable is left to the vault implementation, so a valid vault can fulfill an exit without writing any log.
The standard is Final and builds on ERC-4626 and ERC-7575. Its lifecycle table shows the user calling requestDeposit for Pending and deposit for Claimed. The middle row, Claimable, has no user action at all. The vault column reads “Internal Request fulfillment”: pending amounts go down and claimable amounts go up inside the contract.
The rationale gives two reasons. Requests may be fulfilled in batches, or the state may change automatically once a timestamp passes. In the second case no transaction happens at the moment of the transition, so there is nothing to emit from. An indexer built only on logs will see the request and, later, the claim. It will miss the period in between, which is the period an investor and an administrator care about most.
“It is impractical to require an event to emit after a Request becomes Claimable at the user or batch level.”
ERC-7540, Rationale: No Event for Claimable State
Which reads reveal the Claimable transition?
Four view functions carry the state: pendingDepositRequest, claimableDepositRequest, pendingRedeemRequest and claimableRedeemRequest. Each takes a requestId and a controller, and the pending and claimable values must never include each other.
The specification adds two rules that make these views safe to poll. They must not vary by caller, so an indexer reading from its own address sees what the investor sees. They must not revert unless an unreasonably large input causes an integer overflow, so a revert on a normal read is itself an exception to log.
The requestId changes what a value means. When a vault returns 0 as the requestId, it must identify state by controller alone, and all requests from that controller are aggregated. A claimable value of 1,000 shares then describes the controller, not one instruction. Your ledger must allocate that total across open instructions under a written allocation rule keyed on controller and request ID, such as oldest first, and record the rule it used.
For deposits, the specification also notes that maxDeposit moves in step with claimableDepositRequest. That gives a cross-check for the deposit side only. The redeem side has no matching statement in the standard, so do not assume one for maxRedeem.
How should bounded polling work?
Bounded polling reads only controllers with open requests, at a fixed interval, at one recorded block number per cycle. The worst-case detection delay equals the interval minus one block, and the poll set shrinks as requests close.
Build the open set from the DepositRequest and RedeemRequest logs, which are required and carry controller, owner and requestId as indexed fields. Remove a controller once both its pending and claimable values return to zero and the claim is matched. Read all four views with eth_call at one explicit block number, not at “latest”. The Ethereum JSON-RPC block parameter accepts a block number or the “safe” and “finalized” tags, which lets the indexer store a snapshot it can reproduce.
Here is an illustrative example, not a measured incident. A controller calls requestRedeem for 1,000 shares at block 100. The indexer polls every 50 blocks. The vault fulfills 400 shares at block 160 and the remaining 600 at block 230, with no event either time. At block 150 the indexer reads 1,000 pending and 0 claimable. At block 200 it reads 600 pending and 400 claimable. At block 250 it reads 0 pending and 1,000 claimable. The first change was visible on-chain from block 160 but recorded at block 200, a 40-block delay.
With a 50-block interval, a claimable change can stay unrecorded for up to 49 blocks. In the 1,000-share example, 400 shares became claimable at block 160 and were first recorded at block 200.
ERC-7540 view functions; editorial calculation
Pick the interval from the fulfillment schedule in the fund documents. A vault that fulfills once per dealing day does not need a poll every block. A vault that fulfills on a timestamp needs one read soon after that time.
Can an implementation-specific event replace polling?
No. A custom fulfillment event is implementation behavior outside the ERC-7540 interface, so it can be renamed, dropped in an upgrade or skipped for a batch. Use it to trigger an immediate read, then record the view result.
Keep three layers apart in the record. The specified interface is what every compliant vault must provide: the four views and the three events. Implementation behavior is what this deployment does, such as a custom event or a timestamp rule. Product terms are what the offering documents promise, such as a dealing cut-off. A missing custom event is an exception against the second layer. A claimable balance that appears after the documented date breaches the third.
The views are not final either. The security section of the standard says they can be outdated. Shares or assets are delivered only when the controller claims through the ERC-4626 deposit, mint, redeem or withdraw call, since the standard says vaults must not push tokens to users. For that reason the claim transaction, not the polled value, closes the investor record.
“The view methods for viewing Pending and Claimable request states (e.g. pendingDepositRequest) are estimates useful for display purposes but can be outdated.”
ERC-7540, Security Considerations
Monitoring is also a different job from discovery. Detecting which vault flows are asynchronous runs once per deployment or upgrade and decides whether these views exist. Polling runs on every open request and decides where each one stands.
What should an operational acceptance test prove?
The test should prove that the indexer records a Claimable change with no log, splits partial fulfillment correctly and matches the final claim. The six cases below are proposed checks, not results from a named vault.
| Case | Setup | Pass condition |
|---|---|---|
| Silent fulfillment | Fulfill a redemption with no custom event | Status changes to Claimable within one poll interval |
| Partial fulfillment | Fulfill 400 of 1,000 shares | Record shows 600 pending and 400 claimable at the same block |
| Aggregated controller | Two requests under requestId 0 | Claimable total is allocated by the written rule and the rule is stored |
| Custom event missing | Vault normally emits one; suppress it for a batch | Polling still records the change and raises an implementation exception |
| View revert | A normal-sized read reverts | Status is held, not set to zero, and an exception is raised |
| Claim match | Controller claims after Claimable | Claim transaction closes the request and the controller leaves the poll set |
Run the suite again after any vault upgrade or change of indexer. A new implementation can keep the same interface and still change when, or whether, it emits a custom event.
What must the investor record explain?
The record must show when the exit became claimable, at which block that was observed and which source proved it. A transaction hash alone cannot explain a Claimable state, because the transition may have no transaction of its own.
For each request, keep the submission log, every polled snapshot with its block number, any custom event and the claim transaction. If an investor asks why a redemption sat as pending in a portal for a day, the issuer, custodian and administrator can then show whether the delay came from the vault, the indexer interval or the product terms.
This guide is for fund administrators, transfer agents and custody integrators that report on ERC-7540 vaults. It does not set dealing terms or say when a fund must fulfill a request. For how this standard fits with permissioned tokens and the ERC-4626 base, see the RWA token standards guide. For how claimed amounts relate to executable limits, see ERC-4626 previews versus maxWithdraw.
Sources: ERC-7540 Asynchronous ERC-4626 Tokenized Vaults; ERC-4626 Tokenized Vaults; Ethereum JSON-RPC API, block parameter. Sources checked October 27, 2026. Numerical scenarios and acceptance procedures are editorial analysis, not reports of live fund incidents.
Frequently Asked Questions
Does ERC-7540 emit an event when a request becomes Claimable?
No event is required. The standard mandates DepositRequest and RedeemRequest when a request is submitted and OperatorSet when operator status changes. Its rationale states that the Pending to Claimable transition happens at the vault implementation level and that requiring an event at the user or batch level is impractical. A vault may add its own event, but the interface does not guarantee one.
Which functions show that a redemption is ready to claim?
claimableRedeemRequest(requestId, controller) returns the shares in Claimable state, and pendingRedeemRequest returns the shares still Pending. The deposit side uses claimableDepositRequest and pendingDepositRequest. The specification says these views must not include the other state, must not vary by caller and must not revert except for overflow from an unreasonably large input.
How often should an indexer poll claimable balances?
ERC-7540 sets no interval. Choose one from the fulfillment schedule in the fund documents and the delay operations can accept. In the illustrative example in this article, a 50-block interval means a claimable exit can stay invisible for up to 49 blocks. Poll only controllers with open requests and read every value at one recorded block number.
Is a vault's custom fulfillment event enough evidence?
Treat it as a prompt to read state, not as the record. A custom event is implementation behavior that can change with an upgrade or be missing for a batch. Confirm it with claimableRedeemRequest or claimableDepositRequest at the same block. The specification also says these views are estimates for display and can be outdated, so the claim transaction remains the final evidence.
Related Articles
Should Tokenized Funds Use ERC-7540 Async Vaults?
ERC-7540 is Final and adds a mandatory Pending to Claimable to Claimed lifecycle that ERC-4626 cannot express. The spec concedes that shares received may not match convertToShares at request time, and defines no mandatory cancellation path.
Can a Fund Investor Revoke an Exit Operator?
ERC-7540 operator revocation removes delegated authority to manage vault requests. It does not itself cancel a pending redemption or move its entitlement to another controller. Fund operations must identify who controls an existing request before replacing a service provider, particularly when the investor, custodian and execution service use different addresses.