Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

The best route ignores multi-hop paths

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

Los mantenedores suelen responder en 2 días

@dmoonventure070-art ya está trabajando en esto.

Desde el 16/10/2026.

  • #474 de @sparkysolutions10-pixel — abierto
  • #585 de @dmoonventure070-art — abierto

Evaluación

Este issue todavía no se ha evaluado.

Descripción

area:pricing difficulty:advanced epic:routing help wanted points:200 Stellar Wave
Background

src/aggregator/bestRoute.ts compares venues for a direct pair. Stellar's native path payments route through intermediate assets, and for thin pairs the two-hop route through XLM or USDC is routinely better than anything direct. Lens recommends the worse trade and says it is best.

What to build
  • Multi-hop routing through a configurable set of intermediate assets, bounded in depth.
  • The response shows each hop, its venue and its slippage, so the recommendation can be checked.
  • A direct route still wins when it is better, and the comparison is shown.
Acceptance criteria
  • Routes of at least two hops are considered
  • Every hop is named with its venue and slippage
  • Hop depth and intermediates are configurable
  • A test covers a thin pair where two hops beat direct

Drips Wave · Complexity: Advanced · 200 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
2 d 20 h
PR fusionados (30 d)
127

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.