预言机价格源陈旧度与置信区间披露雷达
已验证事实边界
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.
收起完整分析
决策矩阵
文章表格：可横向滑动，或聚焦表格区域后使用方向键。
| 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 |
来源地图
- 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）
控制说明
1. 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。因此本文不会把未知部分包装成收益承诺、牌照承诺、审批保证、恢复保证、结算保证、可用性保证、价格暗示或平台排名。
2. 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。
操作测试也必须很窄。这就是本节保留边界的原因。
3. 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。
操作测试也必须很窄。这就是本节保留边界的原因。
4. 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。
操作测试也必须很窄。这就是本节保留边界的原因。
5. 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。
操作测试也必须很窄。这就是本节保留边界的原因。
6. 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。
操作测试也必须很窄。这就是本节保留边界的原因。
仍需明确的未知项
- 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
实用结论
预言机价格源选择应从数据质量证据开始，而不是从品牌熟悉度或 TVS 开始。Chainlink 文档要求集成方评估 feed quality 与 category，提示 single-source 与 Proof of Reserve feed 可能带有 provider 或 self-reporting 风险；Pyth 文档则暴露 price、confidence、publisher count 与 feed-update timestamp 等概念，并提示 staleness constraint。实用结论是：协议在把 oracle value 用于抵押品、清算、赎回、会计或用户展示前，应记录 feed category、data-source model、confidence interval、publish time、staleness threshold、circuit breaker 与 fallback route。 本文停在证据边界内，帮助读者决定下一步核验什么，而不是把公开文档改写成私人账户、钱包、回调、政策框架、结算路径或流动性头寸在任何未来条件下都能成功的承诺。