Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

The best route ignores multi-hop paths

クローズ
  • 何か問題がありますか？
#295 コメント 3 件 リアクション 0 件 担当者 1 名 GitHub で見る

メンテナーはふだん 2 日以内に返信

@dmoonventure070-art がすでに取り組んでいます。

2026年10月16日 から。

  • #474 @sparkysolutions10-pixel による — オープン
  • #585 @dmoonventure070-art による — オープン

評価

この issue はまだ評価されていません。

説明

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

主要言語
TypeScript
スター
4
フォーク
71
平均マージ
2日 20時間
マージ済み PR（30日）
127

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Divinity-Labs/Lens のほかの issue

Divinity-Labs/Lens の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。