Report Schema: RWA Standard (v8)

RWA streams adhere to the report schema outlined below.

Schema Fields

FieldTypeDescription
feedIdbytes32Unique identifier for the Data Streams feed
validFromTimestampuint32Earliest timestamp when the price is valid (seconds)
observationsTimestampuint32Latest timestamp when the price is valid (seconds)
nativeFeeuint192Legacy onchain verification fee field
linkFeeuint192Legacy onchain verification fee field; not used for subscription billing
expiresAtuint32Expiration date of the report (seconds)
lastUpdateTimestampuint64Timestamp of the last valid price update (nanoseconds)
midPriceint192DON's consensus median price
marketStatusuint32Market status. See schema docs for value mappings. — Status values

Notes

lastUpdateTimestamp is not guaranteed to be monotonic

Do not assume lastUpdateTimestamp strictly increases from one report to the next. Use marketStatus to determine whether a market is open.

lastUpdateTimestamp is not guaranteed to be monotonic (that is, it does not always increase from one report to the next); the value can vary between reports. Reasons for this include:

  • A provider dropping in or out between reports can shift the median.
  • The fewer providers contribute to a report, the more a single provider's inclusion or exclusion can move the result. For example, if a provider is excluded from one report (due to a timeout) and included in the next, the median can shift to an earlier value than the previous report.

Under normal circumstances, expect this value to advance with each report. A single occurrence of non-monotonic movement is not by itself cause for concern: treat it as a potential issue only if the behavior persists across multiple consecutive reports.

Market Status Values

v8 streams use a three-value mapping:

ValueStatusDescription
0UnknownMarket status cannot be determined
1ClosedMarket is closed
2OpenMarket is open

For trading schedules by asset class, see Market Hours. For integration guidance during market transitions, see Handling Market Events.

Additional Notes

  • Users are responsible for handling market status changes in their applications.
  • Future RWA streams may use different report schemas.

Get the latest Chainlink content straight to your inbox.