Skip to content
This repository was archived by the owner on Nov 28, 2025. It is now read-only.

Commit 093d3ea

Browse files
docs: simplify documentation - remove example and focus on price field only
- Removed third price feed example from JSON - Removed info callout that explained the example - Simplified warning callout to only mention price field - Removed mention of related optional fields (bestBidPrice, bestAskPrice, confidence) Co-Authored-By: Nidhi Singh <[email protected]>
1 parent 0f9b6b5 commit 093d3ea

File tree

1 file changed

+4
-17
lines changed

1 file changed

+4
-17
lines changed

pages/lazer/payload-reference.mdx

Lines changed: 4 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -77,11 +77,6 @@ Here's what a typical StreamUpdated response that contains a PriceFeed looks lik
7777
"publisherCount": 12,
7878
"exponent": -8,
7979
"confidence": 106965585
80-
},
81-
{
82-
"priceFeedId": 3,
83-
"publisherCount": 5,
84-
"exponent": -8
8580
}
8681
]
8782
},
@@ -92,13 +87,6 @@ Here's what a typical StreamUpdated response that contains a PriceFeed looks lik
9287
}
9388
```
9489

95-
<Callout type="info">
96-
In the example above, the third price feed has the `price`, `bestBidPrice`,
97-
`bestAskPrice`, and `confidence` fields absent, indicating that these values
98-
could not be computed. When you encounter missing price fields, use the last
99-
valid price or wait for the next update.
100-
</Callout>
101-
10290
<Callout type="warning">
10391
**Important**: The price is stored in two parts: an integer mantissa value
10492
(the `price` field) and a power-of-ten `exponent`.
@@ -128,11 +116,10 @@ Main aggregate price calculated from all contributing publishers
128116
- **Invariants**: Non-zero when present (null values filtered out)
129117

130118
<Callout type="warning">
131-
**Missing Price Fields**: In some cases, the `price` field (and related
132-
optional fields like `bestBidPrice`, `bestAskPrice`, and `confidence`) may be
133-
absent from the response. This indicates that the price could not be computed
134-
at that moment. When this occurs, you should either use the last valid price
135-
you received or wait for a fresh update with a valid price.
119+
**Missing Price Field**: In some cases, the `price` field may be absent from
120+
the response. This indicates that the price could not be computed at that
121+
moment. When this occurs, you should either use the last valid price you
122+
received or wait for a fresh update with a valid price.
136123
</Callout>
137124

138125
#### Data Publisher Count - `publisher_count`

0 commit comments

Comments
 (0)