Testnet readiness: tracking what must be in place before testnet opens
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 18/100
- Issue 类型
- 功能
- 描述清晰度
- 描述清楚
- 活跃度
- 冷清
- 技术栈
- python, solidity
调研方向
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 内容生成。
描述
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
- Discussion No. 132: testnet readiness thread, especially the release-sequencing comment, the requirements checklist and the pre-testnet requirements research comment
- Sep 18, 2026 Testnet-Ready session (kick-off, working session and wrap-up calls)
Developer/ROADMAP.md: P3-T0.2 (validator ops), P3-DOC2/DOC4, OPS-1, P4-FL1
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 天 4 小时
- 30 天内合并 PR
- 34
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
InfiniteZeroFoundation/DevNet 的其他 Issue
-
ROADMAP.md: refresh "What is still open for P3" (several items were fixed in October)可能已有人在做 @umermjd11 于 2 天前认领。 未关闭documentation good first issue
难度 2/5 1-3 小时 新手友好度 74/100
InfiniteZeroFoundation/DevNet#285 · 1 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Update the 25 translated organisation READMEs to match the English version可能已有人在做 @mrCabez 今天认领。 未关闭good first issue help wanted
难度 2/5 1-3 小时 新手友好度 76/100
InfiniteZeroFoundation/DevNet#277 · 2 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Update the client-service guide to explain training and uploading separately可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 76/100
InfiniteZeroFoundation/DevNet#266 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
InfiniteZeroFoundation/DevNet#299 · 1 条评论 ·
维护者通常 1 天内回复
-
Long run
难度 5/5 一周以上 新手友好度 25/100
InfiniteZeroFoundation/DevNet#298 ·
维护者通常 1 天内回复
查看 InfiniteZeroFoundation/DevNet 的全部 Issue
相似的 Issue
-
Support .aac audio uploads可能已有人在做 @julien731 今天认领。 未关闭feature
难度 2/5 1-3 小时 新手友好度 78/100
nimblehq/audio-transcriber#153 ·
-
help wanted
难度 2/5 1-3 小时 新手友好度 68/100
antonyrag/ragleap-core#1062 ·
-
needs-triage
难度 2/5 1-3 小时 新手友好度 76/100
gke-labs/kube-agents#4321 ·
维护者通常 1 天内回复
-
enhancement help wanted
难度 2/5 1-3 小时 新手友好度 76/100
Git-Hospital/githealthcheck#61 ·
维护者通常 1 天内回复
-
changelog investigate
难度 2/5 1-3 小时 新手友好度 67/100
ramnes/notion-sdk-py#433 ·