RWA Infrastructure6 min read
MB
Editorial Team
·October 24, 2026·Updated October 25, 2026

How Do You Detect Which Vault Flows Are Asynchronous?

ERC-7540 interface detection identifies whether a vault advertises asynchronous deposits, asynchronous redemptions or both. These capabilities require different transaction paths and preview handling. An integration should detect each direction independently, then validate the behavior it will use instead of assigning every vault a single synchronous or asynchronous label.

TL;DR — Key Takeaways

  • ✓Check deposit and redemption capabilities independently.
  • ✓Do not interpret a required asynchronous preview revert as proof of an outage.
  • ✓Separate interface discovery, behavioral testing and product approval.

Ready to get started?

Join others who are already using our platform.

How Do You Detect Which Vault Flows Are Asynchronous?

Why is one asynchronous flag insufficient?

ERC-7540 allows asynchronous deposits, asynchronous redemptions or both. A single vault-wide flag cannot describe all supported combinations or determine the correct transaction for each direction.

A fund can accept cash through a synchronous deposit while processing exits through a request queue. Another configuration can queue subscriptions and provide a synchronous redemption path. The integration needs two capability fields before deciding which controls to show and which method to call.

An illustrative three-row configuration matrix is therefore: async deposit with sync redemption, sync deposit with async redemption, and async on both sides. These are permitted patterns, not claims that a named fund offers any particular configuration.

ERC-7540 requires at least one asynchronous direction. The other direction can retain the synchronous ERC-4626 interaction pattern.

ERC-7540 request flows

Which interface identifiers should the adapter inspect?

ERC-7540 assigns separate interface identifiers to deposit requests and redemption requests. Check 0xce3bbe50 for asynchronous deposits and 0x620ee8e4 for asynchronous redemptions after validating ERC-165 detection.

The standard also requires support for the operator interface 0xe3bc4e65 and ERC-7575 interface 0x2f0a18c5. Record the complete query result with the chain, contract and block used. This gives support teams evidence for the route the application selected.

ERC-165 detection includes checking that the contract recognizes 0x01ffc9a7 and rejects 0xffffffff. A contract that returns true for everything fails that discovery procedure. Handle failed calls and malformed responses as explicit integration exceptions rather than automatically classifying the vault as synchronous.

ERC-165 specifies a 30,000-gas detection procedure and requires a false response for 0xffffffff. Testing only the desired capability misses this validity check.

ERC-165 detection procedure

When should a preview revert be expected?

For an asynchronous deposit flow, ERC-7540 requires previewDeposit and previewMint to revert. For an asynchronous redemption flow, previewRedeem and previewWithdraw must revert.

A monitoring service that expects all four previews to succeed will produce false alarms against a conforming asynchronous flow. A wallet that catches the error and shows zero can be worse: zero may be read as a price or entitlement rather than an unavailable operation.

Choose the route from the capability map. For asynchronous directions, display the request state and documented valuation process. For synchronous directions, use the appropriate preview and limits, with the distinctions explained in vault quotes and withdrawal capacity.

What must still be tested after discovery?

Interface responses select an adapter path; they do not prove implementation correctness, fulfillment timing or economic safety. Validate the chosen request and claim sequence against the deployed behavior.

For each asynchronous direction, trace request creation, the associated controller, progression to claimable and the final claim. Because no event marks that progression, poll the claimable request views on a bounded schedule. Confirm that the application distinguishes these states. For the synchronous direction, test the direct operation and the supported previews without accidentally submitting a request.

Test a contract that advertises a capability but violates the expected behavior, a discovery call that fails, and a vault with only one asynchronous side. These proposed acceptance cases prevent a capability badge from becoming the sole approval control. The asynchronous fund settlement overview explains the full lifecycle beyond discovery.

How should a capability change reach operations?

Revalidate the capability map when the approved implementation or route changes. Retain the previous map so an in-flight request remains interpretable after an integration update.

A proxy upgrade or newly configured entry point can require fresh review. The operational response is to compare supported directions and authorization behavior, then update the adapter with evidence. Do not discard historical request records because the latest endpoint presents a different interface set.

This article addresses interface routing for engineers and operations teams, rather than fund valuation or legal eligibility. Place its acceptance record within the RWA token standards review and connect changes to the institution responsible for the underlying product.

Sources: ERC-7540 interfaces and preview behavior; ERC-165 interface detection. Sources checked October 25, 2026. Numerical scenarios and acceptance procedures are editorial analysis, not reports of live fund incidents.

Frequently Asked Questions

Can deposits be synchronous while redemptions are asynchronous?

Yes. ERC-7540 permits one or both directions to use asynchronous requests. An integration should record the capability of each direction separately. Choosing the correct entry flow does not establish the exit flow, so the wallet and monitoring configuration need independent deposit and redemption handling.

Does a preview revert mean the vault has failed?

Not necessarily. ERC-7540 requires the corresponding preview methods to revert for an asynchronous direction. Interpret the result in the context of detected capabilities and the implemented request flow. A revert outside the expected path still needs investigation; do not suppress every error under a generic asynchronous label.

What if supportsInterface returns true for everything?

The ERC-165 detection procedure requires a false response for the invalid identifier 0xffffffff. A contract returning true for every input does not pass that procedure. Treat the result as a discovery exception and investigate the actual implementation before allowing a route to process investor instructions.

Does successful detection certify the fund?

No. Interface detection is a technical routing input. It does not establish lawful distribution, sound valuation, trustworthy administrators or timely redemptions. Test the actual methods and review product-specific controls separately, retaining the implementation and block context used for the integration approval.

Ready to get started?

Join others who are already using our platform.