feat(finance): Chainlink Data Feeds as verifiable price inputs
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- python
调研方向
Start by reading application/real_options_pricing.py, risk_engine.py, and financial_portfolio.py, then inspect the registry's EVM adapter and issue #4 for the proposed oracle_refs format. Verify which Chainlink feeds are available on the target testnets, including Robinhood Chain. The work is complete when feed sourced runs record their round inputs, stale or missing feeds fail clearly, and recorded inputs reproduce the same result.
由索引模型根据 Issue 内容生成。
描述
Summary
Use Chainlink Data Feeds as an optional price source for options pricing, risk and portfolio analysis, and record the feed round ids in the provenance bundle so results are reproducible.
Motivation
Today market inputs come from files or a data-library download. On-chain feeds give verifiable, timestamped inputs and pair naturally with provenance.
Current state in this repo
application/real_options_pricing.py,risk_engine.pyandfinancial_portfolio.pytake price/vol inputs from request payloads or data files;yfinanceis a dependency.
Proposal
- A price-source interface with implementations: user-supplied, file, and Chainlink feed (read via the registry's EVM adapter).
- Staleness and deviation checks (reject stale rounds, record decimals).
- Store
{feed, round_id, value, observed_at}inoracle_refs(#4). - Frontend: a 'use live feed' option for supported pairs on the options and risk forms.
Acceptance criteria
- Options pricing run with a feed records the exact round used.
- Stale or missing feeds fail with a clear message and never silently fall back.
- Reproducing a run from its recorded inputs gives the same result.
Out of scope
- Running our own oracle nodes.
Dependencies
- #2
- #4
Verify before implementing
- Which feeds exist on the chosen testnets, including Robinhood Chain.
References
- Chainlink Data Feeds docs: https://docs.chain.link/data-feeds
Part of ##1. Ground rules for all issues in this roadmap are listed there (testnet-first, no secrets in the repo, chain logic behind the registry, tests and docs with every PR).
- 主要语言
- Python
- 星标
- 2
- 派生
- 4
- 平均合并
- 5 小时 19 分钟
- 30 天内合并 PR
- 11
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
QMeshPy/distributed-quantum 的其他 Issue
-
enhancement good first issue helia storage tier-1
难度 2/5 1-3 小时 新手友好度 78/100
QMeshPy/distributed-quantum#53 ·
维护者通常 1 天内回复
-
chain-integration enhancement payments research-spike tier-2
难度 4/5 3-5 天 新手友好度 55/100
QMeshPy/distributed-quantum#78 ·
维护者通常 1 天内回复
-
chain-integration enhancement payments research-spike tier-2
难度 3/5 1-2 天 新手友好度 66/100
QMeshPy/distributed-quantum#77 ·
维护者通常 1 天内回复
-
chain-integration enhancement payments tier-2
难度 5/5 一周以上 新手友好度 35/100
QMeshPy/distributed-quantum#76 ·
维护者通常 1 天内回复
-
documentation good first issue kubo storage tier-1
难度 2/5 1-3 小时 新手友好度 42/100
QMeshPy/distributed-quantum#75 ·
维护者通常 1 天内回复
查看 QMeshPy/distributed-quantum 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 85/100
gramaziokohler/compas_timber#870 ·
-
bug
难度 2/5 1-3 小时 新手友好度 82/100
autowarefoundation/autoware_carla_scenario#500 ·
维护者通常 1 天内回复
-
good first issue priority: low size: XS testing
难度 1/5 1-3 小时 新手友好度 86/100
cubrid-lab/cubrid-mcp-server#385 ·
维护者通常 1 天内回复
-
good first issue priority: low size: S testing
难度 2/5 1-3 小时 新手友好度 85/100
cubrid-lab/cubrid-cookbook-python#447 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100