Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
  • Algo errado?
#13 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
25/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
python
Domínio
blockchain, payments

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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

Linguagem predominante
Python
Estrelas
2
Forks
4
Merge médio
6h 14min
PRs com merge (30d)
18

Preparar o ambiente

  • Inclui um Dockerfile ou arquivo Docker Compose
  • Sem modelo de pull request
  • Sem guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de QMeshPy/distributed-quantum

Todas as issues de QMeshPy/distributed-quantum

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.