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

Phase 5 (#37): optional feeless Nano (XNO) settle leg for the credit top-up

Abierto
  • ¿Algo no está bien?
#52 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
38/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
blockchain, payments

Línea de trabajo

Start with the Phase 5 credits-ledger design in #37 and the sequencing in epic #31, then review the existing top-up provider-verification entry point. The suggested scope is complete when nano:mainnet is opt-in and per-wallet, proof-of-send verification credits a ledger top-up row, and tests cover the adapter; Phase 6 seller accounting remains separate.

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

Descripción

enhancement

A feeless Nano (XNO) settle leg for the SkillX credits ledger (Phase 5, #37)

Hi, thanks for the skillx marketplace this is shaping into — the Phase 5 credits/orders design (#37) with its append-only buyer credit ledger and atomic debit+entitlement grant is exactly the seam a feeless settlement option could sit beside when you wire in the top-up provider.

Why this fits your roadmap

Your own sequencing in the epic (#31) is deliberate: make packages trustworthy, then installable, then "only then attach money and creator payouts." Phase 5 (#37) adds a buyer credit ledger topped up by "verified provider events" with quote/order/atomic-debit and agent-safe confirmation, and Phase 6 (#38) adds creator settlement. The top-up leg is the one place a network itself does the money movement.

The additive Nano (XNO) rail

A Native (Nano) transfer is a single self-custodied L1 block with:

  • Zero fee on any amount — a 0.0001 XNO top-up costs the same $0 as a large one. If credits are per-skill micro-amounts, every other rail charges more in fees than the value that moves.
  • Single-block deterministic finality. At check time the network's block_count equals cemented (both 224,640,663), so a send is final in the next block with no multi-block confirmation wait.
  • No bridging and no approve step. The buyer signs directly to their own Nano account; the ledger can credit on a confirmed block hash they can verify themselves.
  • Atomic debit that matches your model. A Nano send is one signed intent that either lands or does not — there is no partial state, which maps cleanly to your "atomic debit + entitlement grant" acceptance test and your no-double-debit rule.

Your Phase 6 "seller payable placeholder accounting separate from credits" is untouched: Nano only makes the settlement leg costless; your ledger, quotes, entitlements and refund policy stay exactly as designed.

Live evidence, checked moments ago
  • Nano RPC {"action":"block_count"} returns {"count":"224640663","cemented":"224640663"} — fully cemented frontier (rpc.nano.to).
  • A settled Nano x402 purchase verified earlier this week: block E67FB89426F46E6AE4E0E5750B5F814A699965B8639DA89F38689EA1AFE57FC3, confirmed:true, amount 0.00001292 XNO, settled in a single block.
  • @x402nano/exact on npm (v0.3.0, MIT) already implements the Nano x402 exact scheme if you want a programmatic payer for the CLI/agent path: https://www.npmjs.com/package/@x402nano/exact
  • Nano protocol docs: https://docs.nano.org/
Suggested scope
  • Add nano:mainnet as an accepted top-up asset behind your Phase 5 credit-ledger provider-verification gate.
  • Keep it opt-in and per-wallet; the credits ledger, quotes and entitlements remain your contract of record.
  • If useful, I can open a PR adding a Nano settlement adapter against your Phase 5 spec (proof-of-send verification + ledger top-up row) with tests.

No action is required to test the rail yourself — the evidence block above is live on mainnet and verifiable at rpc.nano.to or nanexplorer.com.

Lenguaje dominante
TypeScript
Estrellas
189
Forks
40
Merge medio
6 h 54 min
PR fusionados (30 d)
24

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 nextlevelbuilder/skillx

Todos los issues de nextlevelbuilder/skillx

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.