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

Testnet readiness: tracking what must be in place before testnet opens

Abierto
  • ¿Algo no está bien?
#166 2 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
18/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Tranquilo
Stack tecnológico
python, solidity
Área
distributed-systems

Línea de trabajo

Read discussion No. 132 and the Sep 18 Testnet-Ready session notes, then review Developer/ROADMAP.md sections P3-T0.2, P3-DOC2/DOC4, OPS-1 and P4-FL1. Track readiness items as sub-issues, linking or opening the technical candidates listed here and assigning owners. Done means the first external cohort can join testnet and every listed sub-issue is closed or explicitly deferred with a recorded reason.

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

Descripción

Long run Umbrella

Why this issue exists

The Sep 18, 2026 Testnet-Ready half-day session set a hard stop of six months (≈ Mar 18, 2027) for a working testnet with a scaled validator set, with an internal target of five months (≈ Feb 18, 2027). The path agreed there is DevNet 2.0 → DevNet 3.0 → DevNet 4.0 → TestNet.

Testnet readiness has so far lived in discussion No. 132, which is good for debate but can't be checked off. This umbrella turns that thread and the Sep 18 session into tracked work: each readiness item becomes a sub-issue with an owner, and this issue closes when testnet opens.

This is a long-running umbrella. Expect sub-issues to be added as items get written up. The session agreed that everything discussed should be on GitHub within two weeks (by about Oct 2, 2026).

Sources

Launch bar agreed on Sep 18

  • Test token first: testnet uses a test token that mimics the eventual real token. There's no real token launch yet.
  • Small cohort first: about 10 validators (the team, one friend each, plus the outside volunteers already interested) running about 10 simultaneous training rounds. No public campaign until this cohort is stable.
  • Lean: little or no infrastructure spend before testnet. Park anything that doesn't serve testnet.

Sub-issues

Non-technical readiness (Umer's list from the Sep 18 session, plus the research comment on No. 132):

  • #167 Incident response runbook and incident communication
  • Fair-launch airdrop: merit-based eligibility with Sybil/uniqueness resistance (see No. 75)
  • Securities-law review of the airdrop path
  • Model IP / copyright / liability terms for model owners
  • Terms of participation / experimental-network disclaimer
  • Onboarding roadmap: website first, then social media

Technical readiness (candidates, to be linked or opened):

  • Tokenomics parameters for testnet (No. 155)
  • Subgraph live before testnet (No. 24)
  • Validator key storage: no plain-text keys (ROADMAP P3-T0.2b)
  • Model 0 hardware requirements, measured and published
  • Validator onboarding docs / CLI walkthrough (ROADMAP P3-DOC4), plus docs No. 157 and No. 158

Items get ticked here when their sub-issue closes.

Definition of done

Testnet opens to the first external cohort, with every sub-issue above either closed or explicitly deferred past testnet with a recorded reason.

Lenguaje dominante
Python
Estrellas
4
Forks
7
Merge medio
3 d 5 h
PR fusionados (30 d)
34

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 InfiniteZeroFoundation/DevNet

Todos los issues de InfiniteZeroFoundation/DevNet

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.