Documents
Igneum documents
The plan, the standard, the specifications and the evidence files, by their paths on the public repository. The public mirror follows master; a link that answers 404 is a file not yet synced.
| Document | Path | What it is |
|---|---|---|
| The Igneum 2.0 plan | docs/plans/igneum-2.0-plan.pdf | The plan for Igneum 2.0, as a PDF; its section 23 is the acceptance scorecard served on /scorecard. |
| The Igneum 2.0 plan, text | docs/plans/igneum-2.0-plan.txt | The same plan as plain text, the copy the pages cite by section. |
| The Test and Acceptance Standard | docs/plans/igneum-2.0-test-standard.pdf | The cases and suites every claim is tested against, as a PDF; served case by case on /acceptance. |
| The Test and Acceptance Standard, text | docs/plans/igneum-2.0-test-standard.txt | The same standard as plain text. |
| The test registry | docs/plans/igneum-2.0-test-registry.json | Every case of the standard in one machine-readable file. |
| The pins | docs/plans/igneum-2.0.md | The Igneum 2.0 decisions: the objective, the four properties and every pin with its owner and pass condition. |
| The founder’s reference | docs/plans/igneum-2.0-reference.txt | The reference text for Igneum 2.0, as written, that the plan and the pins are read against. |
| The specifications | docs/spec/ | The protocol specification by section: the lottery hash, consensus, finality, seeds and the VDF, fees and economics, execution, client security, the pool protocol, the light client and proving enforcement. |
| The finality guarantees | docs/spec/finality-guarantees.md | What finality guarantees and what it does not; section 9 defines the four words included, executed, proven and finalised. |
| The coexistence model | docs/analysis/class-v6/coexistence-model.md | Whether a specialised supplier can earn a normal return while GPUs stay close enough to compete, and where that fails (MODELLED). |
| The operator simulation | docs/analysis/class-v6/operator-simulation.md | The profit-maximising operator simulation: whether the pricing and capacity rules restore service without an administrator (MODELLED). |
| The connected-state experiment | docs/analysis/class-v6/connected-state.md | The connected-state variant of the class v5 work, its rows and why it was killed as a class (D2(a)). |
| The coexist rows | docs/analysis/class-v6/coexist-rows.md | The measured rows of mining and proving on one card: the miner’s memory, the shard proof’s peak, the time-share (TEAM-REPORTED). |
| The ECO-05 results | docs/analysis/class-v6/eco-05-results.md | The results file of the registry row ECO-05, cited by the facts page. |
| The rotating family design | docs/design/class-v6-rotating-family.md | The class v6 rotating family: layers that change the hash on a schedule no release carries; a design and a gate plan, no consensus code (designed). |
| The proving payment design | docs/design/proving-payment.md | How provers are paid: an explicit user-funded proving payment with congestion pricing, the burn treated separately, and the tip kept whole to the block (designed). |
| The tuning record | docs/build/tuning.md | How Ember reaches a good operating point: the knee rule, the ladders, the safe defaults per class; served on /tuning. |
| The site audit | docs/site/audit-2.0.md | Every served page read against the Igneum 2.0 reset, with what is open; served on /audit. |
| The criticism ledger | docs/fud-ledger-2.0.md | Every criticism in the critic’s words, with its status and pin; served on /ledger. |
Source: the repository at git.igneum.network, branch master. The labels used on this site: TEAM-REPORTED, MODELLED, PROPOSED, PENDING, EXCLUDED.
A GPU-secured network for Ethereum-compatible applications and verifiable computation.
Not legal advice.