Oracles: add a Pyth Pro entry, fix the Chainlink Data Streams note, link the consumer demos

未关闭
#184 1 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
58/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
markdown
领域
documentation

调研方向

Start with skills/standards/ecosystem.md and inspect its Oracles section and the linked Pyth Pro and Chainlink field notes and comparison. Update the entries with the requested Pyth Pro details, corrected Data Streams note, examples, and oracle selection guidance. Done when the section covers all requested facts and links, with the staleness and source selection rules included.

由索引模型根据 Issue 内容生成。

描述

The Oracles section of skills/standards/ecosystem.md lists Reflector, DIA and Chainlink. Three gaps, checked on 12 November 2026:

  1. No Pyth Pro entry. Pyth Pro (formerly Lazer) is live on Stellar since 8 September 2026. Verifier contracts: mainnet CACZ3GBAKUPIAFRILUFO27J5RUH5GJ2VSJ46LP6GJYSKGDRTQ5MS3HCH, testnet CAYFT5JE3UQTKT4Q6ZOZK4FXVYVT6RE3MFC7STA4UB6WAEGBT65MRU52. Pull model: fetch a signed update from the Pyth Pro REST API, verify it on chain with verify_update(Bytes), crate pyth-lazer-stellar-sdk 0.4.0 (pins soroban-sdk ^26.1). The verifier is stateless, so freshness is the consumer's job. A free Terminal key is a 14-day trial of a sample set; XLM/USD needs the Starter plan. Guide: https://docs.pyth.network/price-feeds/pro/integrate-as-consumer/stellar

  2. Chainlink entry: the Data Streams line is out of date. "Needs an allowlisted account" is wrong. The Stellar verifier has no access controller; anyone can call verify(signed_report, sender). What gates Streams is the API subscription: no free tier since 1 September 2026. Verifier contracts: mainnet CAKA3NBYPC6OBEUEGNIYGNYG3ES2GPQK736B5SR7ASGUXRDAKXI2JCQI, testnet CA7GVHWH4GRHE6GI7MHEKQZAOYO4GE7KRGSU3EOS3HYJRVLX3XEA4ONQ. Two more facts for the Data Feeds lines: a frozen feed reaches callers as Error(Contract, #109), and get_min_decimals is 18 for XAUM Reference Rate and USPC NAV.

  3. No worked consumer examples. Two public repos read these oracles from a Soroban contract on testnet, with unit tests, scripts and a read-only page:

Proposed change: a #### Pyth Pro entry, the Data Streams fix in the Chainlink entry, and an Examples line under the Reflector, Chainlink and Pyth Pro entries that points at the repos and the comparison. I can open the PR.

  1. No guidance on which oracle to pick. An agent that reads this skill cannot tell when to use Reflector, Chainlink Data Feeds or Pyth Pro. The comparison above has the facts; the skill needs the rule. Proposed text for the Oracles section:

    • Reflector (public Pulse oracles): free, SEP-40, 14 decimals, a new price every 5 minutes. Pick it for a Stellar-native asset, for DEX prices, or when SEP-40 compatibility matters. Staleness rule: reject when now - timestamp > 2 x resolution.
    • Chainlink Data Feeds: free, one proxy per network, 18 decimals, a new price on a 0.5 percent move or every 24 hours. Pick it for a shared reference rate on BTC, ETH, XLM, LINK, USDT, USDC, EURC, gold or the NAV feed, and when the protocol already uses Chainlink elsewhere. Staleness rule: reject when now - timestamp > heartbeat, and expect a quiet-day price to be hours old.
    • Pyth Pro: paid API, pull model, sub-second prices with bid and ask, the consumer brings the signed update and the verifier checks only the signatures. Pick it for perps, liquidations and anything that needs the price at execution time. Staleness rule: reject on feedUpdateTimestamp and skip carried-forward feeds.
    • Chainlink Data Streams: the same pull model as Pyth Pro, paid subscription, no free tier. Same staleness rule, on expiresAt and observationsTimestamp.
    • Two sources for funds: anything that liquidates or mints against a price should read two oracles and refuse on divergence. On 12 November Chainlink and Reflector mainnet XLM/USD differed by 6 basis points and 14 minutes at the same moment.
主要语言
TypeScript
星标
57
派生
63
平均合并
20 分钟
30 天内合并 PR
18

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

stellar/stellar-dev-skill 的其他 Issue

查看 stellar/stellar-dev-skill 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。