Oracles: add a Pyth Pro entry, fix the Chainlink Data Streams note, link the consumer demos
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 初心者へのやさしさ
- 58/100
- issue の種類
- ドキュメント
- 明瞭さ
- 明確に書かれている
- 活発さ
- 活発
- 技術スタック
- markdown
調査の方向性
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:
-
No Pyth Pro entry. Pyth Pro (formerly Lazer) is live on Stellar since 8 September 2026. Verifier contracts: mainnet
CACZ3GBAKUPIAFRILUFO27J5RUH5GJ2VSJ46LP6GJYSKGDRTQ5MS3HCH, testnetCAYFT5JE3UQTKT4Q6ZOZK4FXVYVT6RE3MFC7STA4UB6WAEGBT65MRU52. Pull model: fetch a signed update from the Pyth Pro REST API, verify it on chain withverify_update(Bytes), cratepyth-lazer-stellar-sdk0.4.0 (pinssoroban-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 -
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: mainnetCAKA3NBYPC6OBEUEGNIYGNYG3ES2GPQK736B5SR7ASGUXRDAKXI2JCQI, testnetCA7GVHWH4GRHE6GI7MHEKQZAOYO4GE7KRGSU3EOS3HYJRVLX3XEA4ONQ. Two more facts for the Data Feeds lines: a frozen feed reaches callers asError(Contract, #109), andget_min_decimalsis 18 forXAUM Reference RateandUSPC NAV. -
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:
- Pyth Pro: https://github.com/kaankacar/stellar-pyth-pro-demo (field note:
docs/field-note/pyth-pro-field-note.md) - Chainlink Data Feeds: https://github.com/kaankacar/stellar-chainlink-demo (field note:
docs/field-note/chainlink-field-note.md) - Pyth Pro, Chainlink Data Feeds and Reflector side by side, with the staleness rule each one needs: https://github.com/kaankacar/stellar-chainlink-demo/blob/main/docs/field-note/oracle-comparison.md
- Pyth Pro: https://github.com/kaankacar/stellar-pyth-pro-demo (field note:
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.
-
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
feedUpdateTimestampand skip carried-forward feeds. - Chainlink Data Streams: the same pull model as Pyth Pro, paid subscription, no free tier. Same staleness rule, on
expiresAtandobservationsTimestamp. - 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.
- 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
- 主要言語
- TypeScript
- スター
- 57
- フォーク
- 63
- 平均マージ
- 20分
- マージ済み PR(30日)
- 18
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
stellar/stellar-dev-skill のほかの issue
-
難易度 3/5 1〜2日 初心者へのやさしさ 35/100
stellar/stellar-dev-skill#182 · コメント 2 件 · リアクション 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 4/5 3〜5日 初心者へのやさしさ 56/100
stellar/stellar-dev-skill#172 · コメント 2 件 · リアクション 1 件 ·
メンテナーはふだん 1 日以内に返信
stellar/stellar-dev-skill の issue をすべて見る
似ている issue
-
Autocomplete still accepts an option after becoming disabled対応中かも @Xapollon430 が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 67/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
reduxjs/react-redux#2416 · コメント 1 件 ·