Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
  • 何か問題がありますか？
#166 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
18/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
静か
技術スタック
python, solidity
領域
distributed-systems

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
Python
スター
4
フォーク
7
平均マージ
3日 58分
マージ済み PR（30日）
39

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

InfiniteZeroFoundation/DevNet のほかの issue

InfiniteZeroFoundation/DevNet の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。