Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

feat(zcash): shielded fee payments detected with an incoming viewing key

Aperta
  • Qualcosa non va?
#13 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
blockchain, payments

Direzione di ricerca

Start by checking issue #3 for the common payment event, then verify the recommended Zcash light-wallet server and testnet availability. Research Python or Node libraries for incoming viewing keys and unified-address derivation. Done means testnet payments are detected after configured confirmations, edge cases are visible to admins, and addresses are not reused across jobs.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

chain-integration enhancement payments tier-3

Summary

Accept private job payments in shielded ZEC by generating a payment address per job and detecting payment with an incoming viewing key, using the encrypted memo to carry the job id.

Motivation

Confidential workloads such as drug-discovery pipelines benefit from private payment. Zcash has no smart contracts, so this is a payment-only integration.

Current state in this repo

  • No Zcash support. Payment events (#3) will provide the common record.

Proposal

  • Run or connect to a Zcash light-wallet backend (for example Zebra with a light-wallet server) on testnet.
  • The platform holds only an incoming viewing key, never spending keys; derive a fresh unified address per job.
  • A watcher detects incoming shielded notes, matches the memo/job id, checks the amount against the quote with a confirmation depth, and records a payment event.
  • Document how selective disclosure with a viewing key can support audits.
  • Conversion of ZEC to USDC is out of scope for this issue.

Acceptance criteria

  • Platform configuration contains no spending key.
  • A testnet payment with the job id memo marks the job paid after the configured confirmations.
  • Underpayment, overpayment and missing memo cases are handled and visible to admins.
  • Address reuse across jobs does not occur.

Out of scope

  • Escrow, smart contracts or Aave-style yield (not possible on Zcash).
  • ZEC to stablecoin conversion.

Technical notes and risks

  • Light-wallet infrastructure is evolving; pin versions. Treat the node/light-wallet as an external dependency with health checks.

Dependencies

  • #3

Verify before implementing

  • Current recommended server stack (Zebra, lightwalletd or successors) and testnet availability.
  • Viewing-key and unified-address derivation libraries for Python or Node.

References

Part of ##1. Ground rules for all issues in this roadmap are listed there (testnet-first, no secrets in the repo, chain logic behind the registry, tests and docs with every PR).

Lingua principale
Python
Stelle
2
Fork
4
Merge medio
6h 14m
PR unite (30g)
18

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di QMeshPy/distributed-quantum

Tutte le issue di QMeshPy/distributed-quantum

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.