Correlation between Stellar assets is uncomputed
维护者通常 4 天内回复
@samkelly-dev 已经在做这个了。
开始于 2026年10月16日。
评估
这个 Issue 还没有评估数据。
描述
Background
Anyone holding a basket — and /basket exists, so Lens already expects them — needs to know what moves together. The price history is there; nothing correlates it.
What to build
GET /correlation?assets=…returning a matrix over a window, with the sample count per pair.- A pair with too few overlapping samples is reported as insufficient rather than given a meaningless coefficient.
Acceptance criteria
- A correlation matrix over a configurable window
- Sample count per pair in the response
- Insufficient overlap is reported, not computed
- A test against a hand-computed example
Drips Wave · Complexity: Intermediate · 150 points
Repo: Divinity-Labs/Lens. Node + Fastify + Prisma + Postgres. Tests are vitest (npm test), not jest — jest against this repo fails every file and tells you nothing.
?network= is not optional on a new route. Every row carries a network and the indexes lead with it. Read req.network ?? activeNetwork, filter on it, echo it in the response, and declare the parameter in openapi.yaml. tests/openapi.test.ts boots the server and fails if a registered route is missing from the spec.
A number without provenance is not an answer. Every figure this batch adds must carry what it was computed from: which venues, how many samples, how fresh. The point of Lens is that its numbers can be checked.
Never elide a contract id or an issuer. Take addresses from the protocol's own documentation and write them whole. A sibling repo's issue wrote CD2W5LUR…XZ4L and five contributors invented plausible contract ids to fill the gap.
Say when you cannot answer. An asset with no liquidity, a pair with one venue, a window with a gap — each has an honest answer that is not zero and not a 500. Zero is a number people act on.
Required: Before submitting, join the contributor Telegram so your work can be tracked and counted toward the Stellar Wave: https://t.me/+fxHXq8f1SwlkZDBk
- 主要语言
- TypeScript
- 星标
- 4
- 派生
- 71
- 平均合并
- 3 天 22 小时
- 30 天内合并 PR
- 142
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
Divinity-Labs/Lens 的其他 Issue
-
Webhook retries have no jitter, so failures synchronise可能已有人在做 @Richard-tobi 于 16 天前认领。 未关闭area:reliability difficulty:easy help wanted points:100 Stellar Wave
难度 2/5 1-3 小时 新手友好度 80/100
Divinity-Labs/Lens#341 · 2 条评论 · 已指派 1 人 ·
维护者通常 4 天内回复
-
[Wave 10 Attribution] Link merged PRs & resolved issues for @sparkysolutions10-pixel on Drips Wave未关闭
难度 1/5 1 小时以内 新手友好度 5/100
Divinity-Labs/Lens#627 ·
维护者通常 4 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
Divinity-Labs/Lens#626 ·
维护者通常 4 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
Divinity-Labs/Lens#625 ·
维护者通常 4 天内回复
-
area:tests automated live-spec-report
难度 4/5 3-5 天 新手友好度 28/100
Divinity-Labs/Lens#606 · 9 条评论 ·
维护者通常 4 天内回复
查看 Divinity-Labs/Lens 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
oxidecomputer/skepsis#102 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
voidzero-dev/void#677 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
kunchenguid/gh-axi#247 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
lidge-jun/opencodex#8101 · 2 条评论 ·
维护者通常 1 天内回复