Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#166 2 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
18/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Ruhig
Tech-Stack
python, solidity
Bereich
distributed-systems

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Python
Sterne
4
Forks
7
Ø Merge
3 T. 58 Min.
Gemergte PRs (30 T.)
39

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus InfiniteZeroFoundation/DevNet

Alle Issues in InfiniteZeroFoundation/DevNet

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.