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

feat(trust): random re-execution audits of worker fragments (VRF-capable)

Aperta
  • Qualcosa non va?
#27 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
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
backend, distributed-systems

Direzione di ricerca

Start by reading marketplace_service.py for reputation and runtime/executor.py for fallback workers, then inspect the provenance work in issue #4. Define the audit and randomness interfaces, configurable rates and tolerances, and an integration test with a faulty worker. Done means mismatches are detected, audits are recorded in job provenance, and audit costs never double-charge the owner.

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

Descrizione

agents chain-integration enhancement tier-2

Summary

Randomly pick completed fragments and re-run them on a second worker to detect cheating or faulty nodes, with a pluggable randomness source that can be Chainlink VRF.

Motivation

Workers are paid for results the coordinator cannot cheaply verify. Unpredictable audits make cheating unprofitable and feed reputation.

Current state in this repo

  • Workers report observed fidelity; reputation exists in marketplace_service.py; the runtime already supports fallback nodes (runtime/executor.py).

Proposal

  • Audit service: select a fraction of fragments by a randomness source and re-execute on a different eligible worker.
  • Compare results within a tolerance suited to the fragment type; mismatches flag both workers for review and adjust reputation or holds.
  • Randomness interface with a local CSPRNG default and a Chainlink VRF implementation as an option (the audit logic must work with no chain at all).
  • Record audits in the job's provenance (#4).

Acceptance criteria

  • Audit rate and tolerance are configurable.
  • A deliberately faulty test worker is detected in an integration test.
  • Audits never double-charge the job owner (cost is platform-borne or budgeted explicitly).

Out of scope

  • Slashing stakes (no staking exists yet).

Dependencies

  • #4

Testing plan

  • Fault-injection test with a simulated bad worker.

Verify before implementing

  • VRF availability on the chosen testnet if the on-chain option is built.

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 54m
PR unite (30g)
7

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.