feat(finance): read-only wallet portfolio analyzer (VaR/CVaR on on-chain holdings)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Read application/risk_engine.py and api/routers/risk.py first, then inspect dependency #2 for the chain adapter registry. The proposal spans wallet balance fetching, price data mapping, risk analysis, and a frontend page; the testing plan calls for fixture wallets with mocked RPC and price data. Done means public-address-only analysis reports unpriceable tokens, data sources, and timestamps.
由索引模型根据 Issue 内容生成。
描述
Summary
Let a user connect or paste a wallet address and run the existing risk engine on its on-chain holdings across supported chains, read-only.
Motivation
It makes the risk engine immediately useful to crypto users and exercises every chain adapter's read path.
Current state in this repo
application/risk_engine.pyandapi/routers/risk.pycompute VaR/CVaR for submitted portfolios.
Proposal
- Add a holdings-fetcher per chain family (EVM first) using the registry adapters (#2).
- Map token balances to price series using a configured price source and feed them to the risk engine.
- Frontend: a page with a wallet field (ENS name accepted once available), per-chain breakdown, and the risk summary.
Acceptance criteria
- Analysis requires only a public address; no signing prompts or approvals.
- Unpriceable tokens are reported, not silently dropped.
- Results include data sources and timestamps.
Out of scope
- Rebalancing or trading actions.
Dependencies
- #2
Testing plan
- Fixture wallets with mocked RPC and price data.
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 小时 新手友好度 67/100
MISP/misp-workbench#496 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 1 天内回复
-
难度 1/5 1-3 小时 新手友好度 88/100
fossasia/visdom-dev#69 ·
维护者通常 3 天内回复
-
[Bug] Parameters named like a property break to_xcal()可能已有人在做 @atharvasalunke1267 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 65/100
collective/icalendar#2018 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复