Real World Asset Oracle

Identify the asset and its representation

A real world asset oracle reports information associated with an offchain asset or claim. The data may concern value, physical quantity, reserves, custody or a lifecycle event. Begin by identifying what the digital instrument represents and which fact the application needs to establish.

The relationship between a token and underlying rights depends on the instrument and its governing arrangements. Data delivery does not itself establish every ownership or redemption claim. The tokenisation context note provides conceptual background.

Keep evidence categories separate

A valuation report describes value under a methodology. A reserve statement describes specified backing assets within a scope. A custody statement concerns a different set of facts. Do not convert any one of them into a universal “asset verified” label.

The SmartData note identifies documented examples of asset-related data interfaces. Those examples do not establish that a feed proves complete solvency, unencumbered title or immediate redemption for every instrument.

Preserve scope and effective dates

Record the issuer or attestor, report identity, observation period, effective date, units and relevant limitations. A delivery timestamp is not a fresh appraisal. Republishing an old statement does not update the underlying evidence.

Use stable mappings among the represented token, underlying instrument and report identifier. Treat a change in that mapping as a reviewed configuration change. A correct signature cannot compensate for linking a report to the wrong asset.

Connect evidence to a specific action

Decide which information supports valuation, issuance, public reporting or redemption processing. Different actions can require different sources and freshness policies. Plan for corrections and unresolved discrepancies instead of hiding them behind the latest numeric value.

Use RWA Oracles for the operational checklist and Tokenization Oracles for the full asset lifecycle.