Fees are assumed, not read

Cerrado
  • ¿Algo no está bien?
#298 3 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 4 días

@Naajih09 ya está trabajando en esto.

Desde el 16/10/2026.

  • #462 de @Naajih09 — abierto
  • #483 de @sparkysolutions10-pixel — cerrado sin fusionar

Evaluación

Este issue todavía no se ha evaluado.

Descripción

area:ingest difficulty:intermediate epic:data-quality help wanted points:150 Stellar Wave
Background

Slippage and execution arithmetic take a fee in basis points. src/pricing/depth.ts accepts feeBp as a parameter and the callers supply a constant. A pool whose fee differs — and protocols vary theirs per pool — is priced wrongly, consistently, in a direction nobody notices.

What to build
  • Read each pool's own fee from the venue, cache it, and use it everywhere a fee is needed.
  • A pool whose fee cannot be read is excluded from execution estimates rather than estimated with a guess.
Acceptance criteria
  • Per-pool fees are read, not assumed
  • Cached, with the cache tested
  • A pool with an unknown fee is excluded and says so
  • No fee constant remains in the pricing path

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

Lenguaje dominante
TypeScript
Estrellas
4
Forks
71
Merge medio
3 d 22 h
PR fusionados (30 d)
142

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Divinity-Labs/Lens

Todos los issues de Divinity-Labs/Lens

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.