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

`agent-pay check`: accept an MCP config file as the registry

Abierto
#47 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
cli, payments

Línea de trabajo

Start with the agent-pay check --registry loader and the existing atomic-units registry format it expects, then read the linked CONTRIBUTING.md and docs/REVIEWING.md. Add a branch for the MCP config shape (a network and merchants object) that converts decimal strings with exact parsing, such as viem's parseUnits, and maps price to pricePin and tolerancePct to toleranceBps. Done means tests cover both file shapes and a clear error for anything else, and the preset question is answered in the issue before coding.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement good first issue

An owner who already runs agent-pay-mcp has their sellers in an MCP config: decimal USDC strings such as "price": "0.003", "maxPerTx": "0.005". agent-pay check --registry expects a different JSON, with atomic units and pricePin. So today they would maintain two files.

What: when the --registry file is an object with network and merchants (the MCP config shape), convert it: decimal strings become atomic units, price becomes pricePin, and tolerancePct becomes toleranceBps. Also accept "preset": "verified" if it's easy to share the preset data. Otherwise report clearly that presets aren't supported there yet.

Acceptance:

  • Tests for both file shapes, and a clear error for anything else.
  • The conversion is exact: no floating point, so use viem's parseUnits or equivalent.

New to the repo? Start with CONTRIBUTING.md. Every outside PR goes through the review gates in docs/REVIEWING.md. Please discuss any new dependency in this issue first. Comment here before starting, so two people don't build the same thing.

Lenguaje dominante
TypeScript
Estrellas
0
Forks
0
Merge medio
3 h 51 min
PR fusionados (30 d)
3

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 DeepFirstHQ/deepfirstsearch

Todos los issues de DeepFirstHQ/deepfirstsearch

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.