ذرائع کی جانچ پر مبنی تحقیق: Oracle Price FEED Staleness
مضمون کا متن تصدیق شدہ انگریزی اصل میں دکھایا گیا ہے۔ ذریعہ جائزے کے بعد ترجمہ شامل کیا جائے گا.
Verified Fact Boundary
1. Chainlink tells application designers to consider the accuracy, availability and quality of data feeds they consume. 2. Chainlink documentation describes risk categories and single-source feed considerations for data-feed selection. 3. Chainlink SmartData Proof of Reserve documentation warns that feed configurations can vary and self-reported reserves carry issuer-risk considerations. 4. Pyth documentation explains price, confidence, publisher count and feed-update timestamp fields for price data. 5. Pyth best-practice guidance discusses staleness constraints and the need to select acceptable age thresholds when consuming prices. 6. A current oracle response does not by itself prove suitability for collateral, liquidation, redemption, accounting or user-display decisions.
کم دکھائیں
Decision Matrix
مضمون کا جدول: افقی اسکرول کریں، یا جدول کے علاقے پر فوکس کر کے تیر والے بٹن استعمال کریں۔
| Check | What it means | Practical action | Unknown to keep explicit |
|---|---|---|---|
| Feed category | risk category explains intended use and market-data risk, not universal safety | record category and whether the feed is new, high risk, custom or deprecating | how category changes after launch or market stress |
| Data-source model | single-source and reserve feeds can depend on provider or issuer reporting | identify whether the feed is market aggregated, single source or proof-of-reserve | whether the underlying provider changed methodology |
| Confidence interval | confidence expresses publisher agreement or uncertainty around a price | set a confidence threshold before allowing liquidation or accounting use | how confidence behaves during venue outages |
| Publish time | a feed value can be syntactically valid while stale | compare publish time against a written staleness threshold | which component updates the threshold during incidents |
| Circuit breaker | protocol logic should handle unexpected feed movement or missing updates | define pause, cap, fallback and manual-review conditions | how users are notified when the feed path is paused |
| Evidence hygiene | oracle logs can expose positions or liquidation-sensitive timing | store non-secret feed id, timestamp, category and decision label | retention rules for incident traces |
Source Map
- Chainlink Documentation: Selecting Quality Data Feeds (chainlink-quality-feeds)
- Chainlink Documentation: SmartData Feed Addresses (chainlink-smartdata-por)
- Pyth Developer Hub: Understanding Price Data (pyth-understanding-price-data)
- Pyth Developer Hub: Best Practices (pyth-best-practices)
Control Notes
1. Feed category
Feed category is the decision point where public documentation must become an operating rule. In this package, it means risk category explains intended use and market-data risk, not universal safety. The practical action is to record category and whether the feed is new, high risk, custom or deprecating. The unresolved edge is how category changes after launch or market stress, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.
2. Data-source model
Data-source model is the decision point where public documentation must become an operating rule. In this package, it means single-source and reserve feeds can depend on provider or issuer reporting. The practical action is to identify whether the feed is market aggregated, single source or proof-of-reserve. The unresolved edge is whether the underlying provider changed methodology, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.
The operating test is also narrow. A public page can prove public wording.
3. Confidence interval
Confidence interval is the decision point where public documentation must become an operating rule. In this package, it means confidence expresses publisher agreement or uncertainty around a price. The practical action is to set a confidence threshold before allowing liquidation or accounting use. The unresolved edge is how confidence behaves during venue outages, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.
The operating test is also narrow. A public page can prove public wording.
4. Publish time
Publish time is the decision point where public documentation must become an operating rule. In this package, it means a feed value can be syntactically valid while stale. The practical action is to compare publish time against a written staleness threshold. The unresolved edge is which component updates the threshold during incidents, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.
The operating test is also narrow. A public page can prove public wording.
5. Circuit breaker
Circuit breaker is the decision point where public documentation must become an operating rule. In this package, it means protocol logic should handle unexpected feed movement or missing updates. The practical action is to define pause, cap, fallback and manual-review conditions. The unresolved edge is how users are notified when the feed path is paused, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.
The operating test is also narrow. A public page can prove public wording.
6. Evidence hygiene
Evidence hygiene is the decision point where public documentation must become an operating rule. In this package, it means oracle logs can expose positions or liquidation-sensitive timing. The practical action is to store non-secret feed id, timestamp, category and decision label. The unresolved edge is retention rules for incident traces, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.
The operating test is also narrow. A public page can prove public wording.
Known Unknowns
- how category changes after launch or market stress
- whether the underlying provider changed methodology
- how confidence behaves during venue outages
- which component updates the threshold during incidents
- how users are notified when the feed path is paused
- retention rules for incident traces
Practical Takeaway
Oracle feed selection should start with data-quality evidence, not with brand familiarity or total value secured. Chainlink documentation tells integrators to assess feed quality and categories, warns that single-source and Proof of Reserve feeds can carry provider or self-reporting risk, and Pyth documentation exposes price, confidence, publisher count and feed-update timestamp concepts while warning about staleness constraints. The decision outcome is to record feed category, data-source model, confidence interval, publish time, staleness threshold, circuit breaker and fallback route before a protocol uses an oracle value for collateral, liquidation, redemption, accounting or user display. The article stops at the evidence boundary. It helps the reader decide what to inspect next without converting public documentation into a promise that a private account, wallet, callback, policy framework, settlement route or liquidity position will work under every future condition.