Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

The best route ignores multi-hop paths

Chiusa
  • Qualcosa non va?
#295 3 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 3 giorni

@dmoonventure070-art ci sta già lavorando.

Dal 16/10/2026.

  • #474 di @sparkysolutions10-pixel — aperta
  • #585 di @dmoonventure070-art — aperta

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

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

Lingua principale
TypeScript
Stelle
4
Fork
71
Merge medio
3g 6h
PR unite (30g)
144

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Divinity-Labs/Lens

Tutte le issue di Divinity-Labs/Lens

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.