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

Asset metadata is absent, so every client fetches its own

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

Los mantenedores suelen responder en 3 días

@Ingenious-02 ya está trabajando en esto.

Desde el 16/10/2026.

  • #469 de @sparkysolutions10-pixel — cerrado sin fusionar
  • #548 de @Ingenious-02 — abierto

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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

A client showing a price also needs the asset's name, domain and decimals. Lens returns codes and issuers, so every consumer separately fetches stellar.toml files — and the sibling wallet had to proxy those server-side because its content-security policy blocked the reads.

What to build
  • GET /assets and GET /assets/:code with name, issuer, home domain, decimals and verification status.
  • Verification means the issuer's own stellar.toml lists the asset, checked rather than assumed, with the check's date in the response.
  • An issuer serving no toml is reported as unverified, which is a real state and not an error.
Acceptance criteria
  • Asset metadata with verification status and the date checked
  • An absent toml yields unverified, not a failure
  • Results are cached with a documented TTL
  • No issuer address in the response is elided

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

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

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.