V/VAULT EXIT
REALITY
REAL PUBLIC CONTRACT
FICTIONAL REQUEST CONTROLLER
ERC-7540 / ACTUAL ETHEREUM RPC INTERFACE EVIDENCE

Real async vault.
No invented investor.

We inspected a live Ethereum mainnet JTRSY/USDC vault using its official Centrifuge deployment registry. The contract declared ERC-7540 asynchronous redemption support via ERC-165 and returned pending and claimable shares for an explicitly fictional placeholder controller. We did not identify or act for a real investor.

READ-ONLY RPC · ONCHAIN CONTRACT VIEW · NO WALLET CONNECTION · NO SIGNATURE · NO GAS · NO REAL CUSTOMER POSITION

01 Verifiable public contract interface

NetworkEthereum mainnet (chain 1)RPC chain ID validated; view calls pinned to one block
Vault from first-party protocol registry0xfe6920eb6c421f1179ca8c8d4170530cdbdfd77aCentrifuge JTRSY / USDC public vault
ERC-165 0x620ee8e4 · async redemptionTRUE returned by contractContract-declared interface, not an independent code audit
ERC-165 0xe3bc4e65 · common operator methodsTRUE returned by contractERC-7540 shared operator interface
ERC-165 0x2f0a18c5 · ERC-7575 sharesTRUE returned by contractThe share token can differ from the vault
ERC-165 0xffffffff · invalid interface controlFALSE returned by contractRejects broken interfaces claiming all IDs

The raw evidence JSON records the actual Ethereum sampled block, exact request ID, declared support flags, raw share amounts and RPC source. This HTML is a permanently static educational explanation, not a live quote; the JSON's block is authoritative for this example.

02 Do not mistake a dummy for your assets

Public placeholder controller

This is NOT an actual customer's public controller or authenticated request. The evidence sample is not a contract or guaranteed payout.

0x000000000000000000000000000000000000dEaD

Request ID: 0. These were illustrative inputs; they were NOT obtained from a real redeem request or investor. The ERC-7540 standard allows zero as a request ID but does not require it for all real requests.

pendingRedeemRequest(0, placeholder)0 raw sharesOne sampled-block RPC observation for a placeholder; not a real owner's pending balance
claimableRedeemRequest(0, placeholder)0 raw sharesOne sampled-block RPC observation for a placeholder; not a real investor's claimable USDC

Both returned zero for this artificial controller at our sampled block. That says nothing about real customers. Their request ID could differ; their controller could differ; an earlier request could already be claimed. A positive claimable share amount would still not prove the asset amount, ability to execute a withdrawal, or protocol solvency.

ERC-7540 async redemption claims can require a separate authorized transaction after fulfillment. This service never submits requests, claims shares or assets, signs for investors, or recommends transactions. It is not a guarantee of a successful claim or investment return.

03 Check your own PUBLIC request identifiers

The free interactive checker supports Ethereum, Base and Arbitrum. Supply the exact public vault, request controller and request ID from a genuine protocol-provided redemption event; it verifies declared ERC-7540 interfaces before reading pending and claimable shares. Missing or malformed responses display unknown, never fictitious zero amounts.

For complex queues an independent customer may voluntarily inquire about a written, limited 19 native Circle Base USDC technical analysis, which is not a liquidity guarantee or protocol audit. This demo charges nothing. A separately agreed paid brief needs a written scope and written refund terms before any payment; there is no checkout, wallet connection or automatic charge on this page.

Use the free async request checker ↗Optional public technical inquiry ↗

ERC-7540 official standard ↗ · Centrifuge deployment registry ↗ · Reproducible open-source implementation ↗