Historical snapshots cannot be compared

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

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

@Lekan101 がすでに取り組んでいます。

2026年10月16日 から。

  • #314 @Lekan101 による — オープン
  • #481 @sparkysolutions10-pixel による — マージされずにクローズ

評価

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

説明

area:api difficulty:easy epic:analytics help wanted points:100 Stellar Wave
Background

With L155 giving a snapshot of now, the obvious next question is what changed since last month, and there is no way to ask it.

What to build
  • Persist snapshots on a schedule with their own retention.
  • GET /snapshot?at=… for a past moment, and a diff between two.
  • Say plainly when a requested moment falls in a gap.
Acceptance criteria
  • Snapshots persisted on a schedule with documented retention
  • A past snapshot is retrievable by time
  • A diff between two moments is available
  • A gap is reported rather than interpolated

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

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

環境構築

はじめの一歩

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

Divinity-Labs/Lens のほかの issue

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

似ている issue

TypeScript の issue をもっと見る

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

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