Skip to content

docs: recommend RWA Advanced (v11) over v8 for US Equities #4116

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sebastian-lerner-link wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs: recommend RWA Advanced (v11) over v8 for US Equities #4116

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
dad23d1
docs: recommend RWA Advanced (v11) over v8 for US Equities
Aug 28, 2026
b266391
docs: drop volume depth / last traded price from v8 aside
Aug 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions src/content/data-streams/reference/report-schema-overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,6 +163,8 @@ The [RWA Standard (v8)](/data-streams/reference/report-schema-v8) report schema

RWA assets trade on traditional exchanges during [market hours](/data-streams/market-hours). These market hours vary by asset class and can be subject to unexpected halts, pauses and other behaviors affecting traditional markets. For this reason, this schema includes a market hours flag and a staleness measure to equip users to handle these events correctly. It is critical that users implement correct safeguards on their end to pause markets, add more conservative risk caps, or do whatever else is appropriate for their application.

For US Equities specifically, [RWA Advanced (v11)](/data-streams/reference/report-schema-v11) is strongly recommended over v8 — see below.

### RWA Advanced (v11)

The [RWA Advanced (v11)](/data-streams/reference/report-schema-v11) report schema offers enhanced market data capabilities with additional fields: liquidity-weighted mid (`mid`), consensus bid and ask prices (`bid`, `ask`), resting book depth (`bidVolume`, `askVolume`), most recent execution (`lastTradedPrice`), nanosecond precision freshness (`lastSeenTimestampNs`), and expanded market status (`marketStatus`) that distinguishes between pre-market, regular hours, post-market, overnight, and weekend periods.
Expand Down
6 changes: 6 additions & 0 deletions src/content/data-streams/reference/report-schema-v8.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,12 @@ import { Aside } from "@components"

RWA streams adhere to the report schema outlined below.

<Aside type="note" title="Integrating US Equities?">
For US Equities streams, [RWA Advanced (v11)](/data-streams/reference/report-schema-v11) is strongly recommended
over this schema. v11 adds bid/ask prices, nanosecond-precision timestamps, and expanded market status values that
distinguish pre-market, regular hours, post-market, and overnight sessions.
</Aside>

### Schema Fields

<SchemaFieldsTable schema="v8" />
Expand Down
5 changes: 5 additions & 0 deletions src/content/data-streams/rwa-streams/handling-market-events.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,11 @@ import MarketEventsTabs from "@features/data-streams/common/MarketEventsTabs.ast

<MarketEventsTabs />

<Aside type="note" title="Integrating US Equities?">
See the [Handling Market Events (v11)](/data-streams/rwa-streams/handling-market-events-v11) guide instead. RWA
Advanced (v11) is strongly recommended over this schema for US Equities streams.
</Aside>

Apply these best practices when integrating or operating markets that use tokenized real-world assets. Developers and operators are responsible for assessing market integrity, implementing mitigations, and managing application-level risks — see the [Developer Responsibilities](/data-streams/developer-responsibilities) guidance for details.

## Market Hours
Expand Down
Loading