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

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

Aperta
#166 2 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
18/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Tranquilla
Stack tecnologico
python, solidity

Direzione di ricerca

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.

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

Descrizione

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.

Lingua principale
Python
Stelle
4
Fork
7
Merge medio
3g 58m
PR unite (30g)
39

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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

Tutte le issue di InfiniteZeroFoundation/DevNet

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.