Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#13 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
25/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
python
Bereich
blockchain, payments

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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).

Vorherrschende Sprache
Python
Sterne
2
Forks
4
Ø Merge
5 Std. 19 Min.
Gemergte PRs (30 T.)
11

Entwicklungsumgebung

  • Enthält ein Dockerfile oder eine Docker-Compose-Datei
  • Keine Pull-Request-Vorlage
  • Kein Beitragsleitfaden

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus QMeshPy/distributed-quantum

Alle Issues in QMeshPy/distributed-quantum

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.