Hi
Interesting thread , i v been following since the early freeze/unfreeze discussions.
One gap I keep running into building on top of RWA tokens: uRWA standardizes how the token behaves (freeze, force transfer, compliance hooks), but there’s no standard way to query what’s behind the token. Is the custodian solvent? Has the asset been audited recently? What’s the bridge dependency? When Aave lost $196M last week from rsETH, the token interface worked perfectly — the problem was invisible dependencies in the underlying asset.
We ran into this building a quality oracle on Base (120+ RWA assets scored across 7 risk layers — issuance, counterparty, market, contagion, regulatory, smart contract, operational). The scoring works, but every integration is custom because there’s no standard way to expose that data.
Would uRWA consider an optional extension for machine-readable asset metadata beyond compliance , something like a getRiskLayer(uint8 layer) view function? Or is that intentionally out of scope?
Re Context: working on a related ERC for trust infrastructure that could compose with uRWA on this front.
Patrick - Tkanks