There is no snapshot anyone can cite
Los mantenedores suelen responder en 1 día
@aliyuHabibu ya está trabajando en esto.
Desde el 16/10/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Background
Ecosystem reports, grant applications and dashboards all need the same thing: one object describing the state of Stellar markets at a moment, with a timestamp, that can be referenced later. Assembling it today means five calls and no guarantee they describe the same instant.
What to build
GET /snapshot— venues, TVL, 24h volume, top pairs, peg status and freshness, as one timestamped object.- Assembled from one consistent read, so every figure in it describes the same moment.
- Cacheable and cheap, because this is the one people will poll.
Acceptance criteria
- One object covering venues, TVL, volume, top pairs and pegs
- A single timestamp that every figure in it honours
- Cacheable, with the policy documented
-
?network=honoured and declared
Drips Wave · Complexity: Easy · 100 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
- Lenguaje dominante
- TypeScript
- Estrellas
- 4
- Forks
- 71
- Merge medio
- 1 d 9 h
- PR fusionados (30 d)
- 34
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Divinity-Labs/Lens
-
Webhook retries have no jitter, so failures synchronisePosiblemente ocupada @Richard-tobi la tomó hace 1 día. Abiertoarea:reliability difficulty:easy help wanted points:100 Stellar Wave
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
Divinity-Labs/Lens#341 · 2 comentarios · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
The MCP server has no metricsPosiblemente ocupada @rupesh-kumar-sah la tomó hoy. Abiertoarea:observability difficulty:easy help wanted points:100 Stellar Wave
Divinity-Labs/Lens#425 · 2 comentarios · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Tool descriptions do not tell an agent when to stopPosiblemente ocupada @rupesh-kumar-sah la tomó hoy. Abiertoarea:mcp difficulty:easy help wanted points:100 Stellar Wave
Divinity-Labs/Lens#424 · 4 comentarios · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
No test drives a real 402 payment loopPosiblemente ocupada @Ugasutun la tomó hoy. Abiertoarea:testing difficulty:advanced help wanted points:200 Stellar Wave
Divinity-Labs/Lens#423 · 6 comentarios · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
The agent example is undocumentedPosiblemente ocupada @GazzyLee la tomó hoy. Abiertoarea:docs difficulty:easy help wanted points:100 Stellar Wave
Divinity-Labs/Lens#422 · 3 comentarios · 1 asignado ·
Los mantenedores suelen responder en 1 día
Todos los issues de Divinity-Labs/Lens
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
jbacalso24/mimry#459 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
architecture help wanted hive/claimed-by-architect origin/architect stage/030-pr-in-progress tech-debt
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
kubestellar/console#24422 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area: backends type: docs
Dificultad 1/5 1-3 horas Aptitud para principiantes 83/100
schlessera/brain-kit#2383 ·
Los mantenedores suelen responder en 1 día
-
agent duplicate providers tool triaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 1 día