Nobody can ask what it costs to trade a given size
维护者通常 1 天内回复
评估
这个 Issue 还没有评估数据。
描述
Background
The depth endpoint takes one amount. The question traders and treasuries actually ask is the shape: what does 100, 1,000, 10,000 cost me, and where does it stop being worth it.
What to build
GET /impact/:assetA/:assetBreturning slippage at a ladder of sizes, in one call.- The ladder adapts to the pair's liquidity rather than being fixed, so a thin pair is not described entirely in sizes it cannot fill.
- Name the size at which slippage crosses configurable thresholds — that single number is what most callers want.
Acceptance criteria
- Slippage at a ladder of sizes in one response
- The ladder adapts to available liquidity
- Threshold crossings are reported explicitly
- A pair too thin for the smallest size says so rather than returning 100%
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
- 平均合并
- 1 天 15 小时
- 30 天内合并 PR
- 28
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Divinity-Labs/Lens 的其他 Issue
-
area:reliability difficulty:easy help wanted points:100 Stellar Wave
难度 2/5 1-3 小时 新手友好度 80/100
Divinity-Labs/Lens#341 · 1 条评论 ·
维护者通常 1 天内回复
-
Startup does not verify the database schema matches the code可能已有人在做 @titankrypt-gif 今天认领。 未关闭area:database difficulty:advanced help wanted points:200 Stellar Wave
Divinity-Labs/Lens#352 · 3 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Ingester loops have no upper bound on a single cycle可能已有人在做 @felixumeh 今天认领。 未关闭area:ingest difficulty:intermediate help wanted points:150 Stellar Wave
Divinity-Labs/Lens#351 · 4 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
There is no runbook for the service可能已有人在做 @felixumeh 今天认领。 未关闭area:docs difficulty:easy help wanted points:100 Stellar Wave
Divinity-Labs/Lens#350 · 2 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
The MCP server's upstream call has no deadline and no error handling可能已有人在做 @Wittig18 今天认领。 未关闭area:mcp difficulty:easy help wanted points:100 Stellar Wave
Divinity-Labs/Lens#349 · 2 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 Divinity-Labs/Lens 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 67/100
agilepathway/label-checker#739 · 4 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 68/100
CopilotKit/OpenBot#800 ·
维护者通常 1 天内回复
-
Endpoint links in the tag operations list are below the 24px target size可能已有人在做 @AdzerKI 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 79/100
ehmpathy/rhachet-roles-bhuild#471 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 73/100
维护者通常 1 天内回复