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

feat(base): mainnet-readiness safeguards, Basenames and portable reputation attestations

Aperta
  • Qualcosa non va?
#14 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
api, backend

Direzione di ricerca

Start by reading the registry dependency in issue #2 and the shared ENS resolution code referenced by the issue; inspect the current network configuration and worker_pricing reputation storage. Verify the Base Sepolia attestation service deployment and schema registry process before choosing an integration path. Done means mainnet fails fast without the explicit flag and registry entry, wallet and funder lists resolve names with address fallback, and a sample worker attestation can be issued, read back, and revoked on testnet.

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

Descrizione

chain-integration enhancement tier-1

Summary

Prepare the Base integration for a future mainnet decision without enabling it, and add two Base-native features: human-readable names and worker reputation attestations.

Motivation

Base is the existing chain. Safeguards and clear configuration reduce the risk of a mainnet mistake; Basenames and attestations make workers and funders easier to identify and trust.

Current state in this repo

  • Base Sepolia is the only configured network; NETWORK defaults to base-sepolia.
  • Worker reputation_score lives only in MongoDB (worker_pricing).

Proposal

  • Mainnet guard: refuse mainnet unless an explicit env flag and a registry entry (#2) are present; log a startup warning when enabled; add a runbook covering custody, limits and monitoring.
  • Basenames: resolve and display primary names for wallets on Base (see the ENS issue for shared resolution code).
  • Attestations (optional): publish a worker reputation or fidelity attestation on Base Sepolia using a standard attestation service, signed by the platform, so reputation is portable.

Acceptance criteria

  • Starting with a mainnet network configured but the flag unset fails fast with a clear message.
  • Wallet and funder lists show a name when one exists and fall back to the address.
  • An attestation can be issued, read back and revoked on testnet for a sample worker.

Out of scope

  • Actually enabling mainnet.

Dependencies

  • #2

Verify before implementing

  • Current attestation service deployment on Base Sepolia and its schema registry process.

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
5h 19m
PR unite (30g)
11

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.