igneum-network/igneum
1
0
Fork 0
Code Issues Pull requests Releases Activity

Litepaper: the five deliverables of Igneum 2.0 on the roadmap (owner, pass condition, today's label, the evidence file on master beside each row), linked from the scorecard

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs 2026-10-08 16:39:54 +00:00
parent 500f507851
commit 3695beff04
1 changed files with 10 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
site/litepaper.html
View file

@ -765,6 +765,16 @@ body.all .pager{display:none}
</tbody>
</table></div>
<p>Dates slip. Gates do not. Phase two decides everything. If consumer GPUs cannot prove shards fast enough, Igneum says so and does not launch on promises.</p>
<h3>The five deliverables of Igneum 2.0</h3>
<div class="tbl"><table><thead><tr><th>Deliverable</th><th>Owner</th><th>Pass condition</th><th>Today</th><th>Evidence</th></tr></thead><tbody>
<tr><td>D1. A frozen, reproducible baseline</td><td>the coordinator with the hash and node lanes</td><td>an independent operator reproduces the baseline within declared tolerances from the served kit alone</td><td>PENDING: the kit is pinned by digest (the release manifest); the reference GPU population, the two tests per class and the cost per accepted unit of work are owed</td><td><a href="https://git.igneum.network/igneum-network/igneum/src/branch/master/docs/plans/igneum-2.0.md">igneum-2.0.md</a></td></tr>
<tr><td>D2. Two architectural experiments</td><td>the class v6 invention lane (a), the multi-family adversary lane (b)</td><td>the candidate improves against re-optimised adversaries within the preset cost and verification limits, or v6 stands and the experiment is published as a failure</td><td>(a) TEAM-REPORTED, killed as a class: only the window width reaches the chip; (b) open</td><td><a href="https://git.igneum.network/igneum-network/igneum/src/branch/master/docs/analysis/class-v6/connected-state.md">connected-state.md</a></td></tr>
<tr><td>D3. A programmable adversary allowed to survive</td><td>the multi-family adversary lane with the k lane</td><td>the best supported cost and energy advantage sits inside the chosen competitiveness envelope, with uncertainty published</td><td>MODELLED: the placed and routed core energies served above; the dataset schedule and the state coupling are under evaluation</td><td><a href="https://git.igneum.network/igneum-network/igneum/src/branch/master/docs/design/class-v6-rotating-family.md">class-v6-rotating-family.md</a></td></tr>
<tr><td>D4. A five-year coexistence model</td><td>the research lane with the k lane’s rows</td><td>the model names credible conditions for sustained commodity participation and names where it fails</td><td>MODELLED, first run served: the DRAM board passes six of seven conditions; the die fails on its machine cost; the thresholds live in the sensitivity workbook</td><td><a href="https://git.igneum.network/igneum-network/igneum/src/branch/master/docs/analysis/class-v6/coexistence-model.md">coexistence-model.md</a></td></tr>
<tr><td>D5. A no-rescue network exercise</td><td>the node lane with the build-server lane</td><td>specified behaviour with no emergency algorithm change and no privileged intervention</td><td>PENDING: the prerequisite (proof verification enforced in consensus) is on from block zero on the Igneum 2.0 devnet; the exercise itself is owed</td><td><a href="https://git.igneum.network/igneum-network/igneum/src/branch/master/docs/spec/finality-guarantees.md">finality-guarantees.md</a></td></tr>
</tbody></table></div>
<p class="src">The pins and their pass conditions are <code>docs/plans/igneum-2.0.md</code>; the Today column carries the served labels (TEAM-REPORTED, MODELLED, PROPOSED, PENDING, EXCLUDED) and moves only with a landed document. The <a href="/scorecard">acceptance scorecard</a> is the checklist across the twelve gates.</p>
</section>
<section id="miners-ask">