Skip to content

Commit d419bdd

Browse files
committed
additonal feedback
1 parent c9adb64 commit d419bdd

File tree

4 files changed

+30
-22
lines changed

4 files changed

+30
-22
lines changed

src/content/data-streams/reference/report-schema-v11.mdx

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,8 @@ metadata:
2222
import DataStreams from "@features/data-streams/common/DataStreams.astro"
2323
import ReportSchemaTabs from "@features/data-streams/common/ReportSchemaTabs.astro"
2424

25+
import { Aside } from "@components"
26+
2527
<DataStreams section="dsNotes" />
2628

2729
<ReportSchemaTabs />
@@ -65,7 +67,7 @@ For streams with standard market hours coverage. Unless a feed explicitly states
6567

6668
For streams with 24/5 extended hours coverage (e.g., US Equities):
6769

68-
| Value | Status | Hours (ET) | Description |
70+
| Value | Status | Normal Hours (ET) | Description |
6971
| ----- | ----------------- | ------------------------------------- | ---------------------------------------------- |
7072
| `0` | **Unknown** || Market status cannot be determined |
7173
| `1` | **Pre-market** | 4:00am–9:30am Mon–Fri | Extended hours before regular trading session |
@@ -74,14 +76,20 @@ For streams with 24/5 extended hours coverage (e.g., US Equities):
7476
| `4` | **Overnight** | 8:00pm–4:00am Sun evening–Fri morning | Overnight session with limited liquidity |
7577
| `5` | **Weekend** | 8:00pm Fri–8:00pm Sun | Weekend period when primary markets are closed |
7678

79+
<Aside type="note" title="Holidays">
80+
During public market holidays (e.g., Christmas, Thanksgiving), the `marketStatus` is expected to return `4`
81+
(Overnight) because data providers do not explicitly flag holiday closures. Users should cross-reference major holiday
82+
periods using the [Market Hours](/data-streams/market-hours) guide and implement additional safeguards as needed.
83+
</Aside>
84+
7785
Users should implement appropriate safeguards based on market status, such as pausing trading, adjusting risk parameters, or implementing staleness checks during non-regular hours or closed periods.
7886

7987
### Notes
8088

8189
#### Last Seen Timestamp
8290

83-
- **IMPORTANT**: The `lastSeenTimestampNs` field reflects the timestamp of the last update for the `mid` price only. Do not assume this timestamp applies to `bid`, `ask`, `bidVolume`, `askVolume`, or `lastTradedPrice`. Different fields may have been updated at different times.
8491
- `lastSeenTimestampNs` helps applications detect stale data for the mid price, especially important during market transitions and holidays.
92+
- **IMPORTANT**: The `lastSeenTimestampNs` field reflects the timestamp of the last update for the `mid` price only. Do not assume this timestamp applies to `bid`, `ask`, `bidVolume`, `askVolume`, or `lastTradedPrice`. Different fields may have been updated at different times.
8593

8694
#### Bid/Ask Volume
8795

src/content/data-streams/rwa-streams/24-5-us-equities-user-guide.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -127,7 +127,7 @@ Consumers must treat `marketStatus = 5` (Weekend) as a valid state and define de
127127

128128
#### Stale Data Detection
129129

130-
Markets may stop updating due to exchange outages, circuit breakers, trading halts, or corporate actions. Use the `lastSeenTimestampNs` field (which reflects the timestamp of the last update for the `mid` price only) to detect staleness by comparing it against the current time. When this timestamp stops advancing, it indicates the underlying venue has stopped providing updates.
130+
Markets may stop updating due to exchange outages, circuit breakers, trading halts, or corporate actions. The `marketStatus` field will continue reflecting the status that it normally would. Use the `lastSeenTimestampNs` field (which reflects the timestamp of the last update for the `mid` price only) to detect staleness by comparing it against the current time. When this timestamp stops advancing, it indicates the underlying venue has stopped providing updates.
131131

132132
Phase-specific feeds can introduce unique behavior due to venue-specific operational characteristics and market microstructure. The following are some examples of scenarios that may occur during session transitions or under specific market conditions:
133133

src/content/data-streams/rwa-streams/handling-market-events-v11.mdx

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -18,9 +18,9 @@ import MarketEventsTabs from "@features/data-streams/common/MarketEventsTabs.ast
1818
<MarketEventsTabs />
1919

2020
<Aside type="note" title="24/5 US Equities">
21-
This guide is designed for standard Data Streams operating during regular market hours (9:30am-4pm ET). Users
22-
integrating 24/5 streams with extended and overnight trading sessions should refer to the [24/5 US Equities User
23-
Guide](/data-streams/rwa-streams/24-5-us-equities-user-guide), which addresses continuous trading coverage.
21+
This guide covers standard market hours operation (9:30am-4pm ET). For streams with extended hours coverage including
22+
pre-market, post-market, and overnight sessions, refer to the [24/5 US Equities User
23+
Guide](/data-streams/rwa-streams/24-5-us-equities-user-guide) for additional guidance on handling continuous trading.
2424
</Aside>
2525

2626
Apply these best practices when integrating or operating markets that use tokenized real-world assets during standard market hours. 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.
@@ -39,29 +39,29 @@ Market gaps occur when there are interruptions in trading or price discovery, le
3939

4040
#### Market close
4141

42-
Large price jumps between trading sessions due to after-hours news.
42+
The following is written from the perspective of someone integrating a v11 schema Data Stream for regular trading hours. For streams with different trading hours, the `marketStatus` field values should be adjusted accordingly.
4343

44-
A large price jump at market open could cause sudden liquidations, potentially leaving the perpetual DEX with bad debt if a trader's collateral is insufficient to cover the losses.
44+
Around market close, large price jumps may occur due to after-hours news. This can create a large pricing gap between the close of the last session and the open of the new session. Such a price jump can cause issues for protocols by triggering sudden liquidations.
4545

46-
| Data Stream behavior | User guidance |
47-
| :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
48-
| <ul><li>`midPrice`: Closing price is repeated until market open.</li><li>`marketStatus`: `1`, `3`, `4`, `5` (Not Regular Hours).</li><li>`lastUpdateTimestamp`: Timestamp of the closing price of the last session.</li></ul> | Keep markets closed while `marketStatus != 2` to prevent users trading at unfair prices.<br/><br/> Leverage available should be set in line with the asset average volatility to avoid bad debt if a trader's collateral is insufficient to cover the losses. |
46+
| Data Stream behavior | User guidance |
47+
| :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
48+
| <ul><li>`midPrice`: Closing price is repeated until market open.</li><li>`marketStatus`: `1`, `3`, `4`, `5` (Not Regular Hours).</li><li>`lastUpdateTimestamp`: Timestamp of the closing price of the last session.</li></ul> | Keep markets closed while `marketStatus != 2` to prevent users trading at unfair prices.<br/><br/> Leverage available should be set in line with the asset average volatility to avoid bad debt if a user's collateral is insufficient to cover the losses. |
4949

5050
#### Price formation at open/close
5151

5252
Certain assets (e.g., FX open on Sunday afternoon) experience gradual price discovery due to fragmented liquidity and delayed trading activity.
5353

54-
The perpetual DEX should avoid opening their market with the last close price.
54+
Integrating protocols should avoid opening their market with the last close price.
5555

5656
| Data Stream behavior | User guidance |
5757
| :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------- |
5858
| <ul><li>`midPrice`: Closing price is repeated until a bid/ask becomes available or a transaction occurs.</li><li>`marketStatus`: `2` (Regular Hours).</li><li>`lastUpdateTimestamp`: Timestamp of the closing price of the last session.</li></ul> | Wait until `lastUpdateTimestamp` is current before opening the market so traders don't execute on stale quotes. |
5959

6060
#### Sudden failures
6161

62-
Unexpected system outages, order execution failures, or data feed disruptions can occur.
62+
Unexpected system outages, order execution failures, or data feed disruptions can occur in traditional data brokers and trading systems.
6363

64-
The price will be flat during that period, meaning if a perp DEX lacks a mechanism to handle halts, it may struggle to determine fair prices thus leading to unpredictable liquidations.
64+
The price will be flat during that period, meaning if an integrating protocol lacks a mechanism to handle halts, it may struggle to determine fair prices thus leading to unpredictable liquidations.
6565

6666
| Data Stream behavior | User guidance |
6767
| :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------- |
@@ -71,7 +71,7 @@ The price will be flat during that period, meaning if a perp DEX lacks a mechani
7171

7272
Stocks can be halted due to extreme volatility (e.g., limit up/down rules) or regulatory actions.
7373

74-
The price will be flat during that period, meaning if a perp DEX lacks a mechanism to handle halts, it may struggle to determine fair prices thus leading to unpredictable liquidations.
74+
The price will be flat during that period, meaning if an integrating protocol lacks a mechanism to handle halts, it may struggle to determine fair prices thus leading to unpredictable liquidations.
7575

7676
| Data Stream behavior | User guidance |
7777
| :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------- |
@@ -123,7 +123,7 @@ Delisting will zero out prices for the asset.
123123

124124
When a company spins off a business unit into a separate publicly traded entity, the parent company's stock may adjust accordingly, while the spun-off company's shares begin trading independently.
125125

126-
Positions may need to be manually adjusted if the DEX doesn't support tracking the new entity.
126+
Positions may need to be manually adjusted if the integrating protocol doesn't support tracking the new entity.
127127

128128
| Data Stream behavior | User guidance |
129129
| :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |

0 commit comments

Comments
 (0)