# Report Schema: RWA Standard (v8)
Source: https://docs.chain.link/data-streams/reference/report-schema-v8

> For the complete documentation index, see [llms.txt](/llms.txt).

> **NOTE: Get started**
>
> Data Streams is self-serve, no sales call required. [Sign up](https://app.chain.link) to get started, or follow the
> [sign-up guide](/data-streams/sign-up).

RWA streams adhere to the report schema outlined below.

### Schema Fields

| Field                   | Type      | Description                                                                                                                         |
| ----------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| `feedId`                | `bytes32` | Unique identifier for the Data Streams feed                                                                                         |
| `validFromTimestamp`    | `uint32`  | Earliest timestamp when the price is valid (seconds)                                                                                |
| `observationsTimestamp` | `uint32`  | Latest timestamp when the price is valid (seconds)                                                                                  |
| `nativeFee`             | `uint192` | Legacy onchain verification fee field                                                                                               |
| `linkFee`               | `uint192` | Legacy onchain verification fee field; not used for subscription billing                                                            |
| `expiresAt`             | `uint32`  | Expiration date of the report (seconds)                                                                                             |
| `lastUpdateTimestamp`   | `uint64`  | Timestamp of the last valid price update (nanoseconds)                                                                              |
| `midPrice`              | `int192`  | DON's consensus median price                                                                                                        |
| `marketStatus`          | `uint32`  | Market status. See schema docs for value mappings. — [Status values](/data-streams/reference/report-schema-v8#market-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

> **CAUTION: Use marketStatus, not timestamps**
>
> Always use  to determine whether a market is open. Do  use
> , , or any other timestamp field — timestamps
> indicate when data was last recorded, not whether the market is currently active.

v8 streams use a three-value mapping:

| Value | Status      | Description                        |
| ----- | ----------- | ---------------------------------- |
| `0`   | **Unknown** | Market status cannot be determined |
| `1`   | **Closed**  | Market is closed                   |
| `2`   | **Open**    | Market is open                     |

For trading schedules by asset class, see [Market Hours](/data-streams/market-hours). For integration guidance during market transitions, see [Handling Market Events](/data-streams/rwa-streams/handling-market-events).

### Additional Notes

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