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

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

Abierto
  • ¿Algo no está bien?
#27 0 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
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
backend, distributed-systems

Línea de trabajo

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.

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

Descripción

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

Lenguaje dominante
Python
Estrellas
2
Forks
4
Merge medio
5 h 45 min
PR fusionados (30 d)
25

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

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 QMeshPy/distributed-quantum

Todos los issues de QMeshPy/distributed-quantum

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.