Ondo Integration Console

Live calls against the USDY InstantManager (0xa42613…1f15), its wired oracle and compliance module, and the token contracts. Each read retries across failover nodes, so a single slow node does not fail the check.

Supply from totalSupply(), USDY price from the InstantManager's wired oracle (getAssetPrice()). USDY accrues by price; rUSDY is the rebasing wrapper, so rUSDY and USDY supply are not additive.

On-chain deployment health live eth_getCode

Asset	Chain	Code	Symbol	Decimals	Total supply	Address

TVL by chain DefiLlama

The on-chain table confirms each contract exists and responds per chain (step zero of an integration). The TVL bars show where the assets actually sit, so a partner knows which chains carry real volume.

LIVE

USDY InstantManager config

0xa42613…1f15

FLOW

The calls a partner makes to mint

USDC

→

approve(IM, amt)

→

subscribe(
USDC, amt, minOut)

→

gate: IDRegistry
+ compliance

→

USDY minted

Both directions revert UserNotRegistered() (0x2163950f) for a wallet not allowlisted in OndoIDRegistry. The simulator above runs exactly this subscribe() and reports the result.

What this proves for the role

A real preflight, not a claim. The mint simulator runs Ondo's actual subscribe() as a static call, decodes the revert, and quotes USDY out at the live oracle price. That is the artifact I would hand a partner engineer on day one.
Reliability is built in. Every read retries across four failover nodes, so the tool does not flash "read failed" on a healthy chain. An integration tool that is flaky is worse than none.
Verified vs assumed is labeled. Each value carries a tag: live read, config, derived, DefiLlama. The APY is annualized from real 30-day oracle price movement, not quoted from marketing.
Bilingual, APAC hours. I would run this walkthrough with a partner's engineers in English or Mandarin, then file the friction back to Product.

Stack & sources

Static client on Cloudflare Workers. A /rpc?chain= proxy fails over across public nodes on Ethereum, Arbitrum, BNB and Polygon, with client-side retries on top. A /ext proxy reads DefiLlama for TVL. Hand-rolled ABI encode/decode and revert-selector decoding (no web3 library), selectors verified with cast against the deployed contracts. Source in my application folder. Full written analysis →

Simulate a USDY mint before a partner writes a line of code.

Will this USDY mint succeed?

USDY InstantManager config

The calls a partner makes to mint

What this proves for the role

Stack & sources