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

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

Abierto
  • ¿Algo no está bien?
#14 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
api, backend

Línea de trabajo

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.

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

Descripción

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

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

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.