Evidence for every gate.
A GPU-secured network for Ethereum-compatible applications and verifiable computation. This is an acceptance checklist, not a completion dashboard: twelve gates from the Igneum 2.0 plan (page 25), the evidence each requires, what may never stand in for it, and where each gate stands today, read from the facts page. Nothing on this site stands above team-tested; every chip row is modelled.
| Gate | Evidence required | Do not substitute | Today |
|---|---|---|---|
| Hardware baseline D1 | Pinned code and independently reproduced system-power results. | A favourable isolated benchmark. | TEAM-REPORTED today: the pinned kit and the card rows are the team’s (facts rows 3 and 7); no independent reproduction yet. |
| Specialist competition D2, D3 | Best realistic multi-epoch adversary, complete cost boundaries and uncertainty. | One reference ASIC or a synthesis artefact. | MODELLED today: placed and routed core energies, no chip measured, hardware cost within 2x (facts row 6); the programmable multi-epoch adversary is D3’s open work. |
| Commodity access D1, D4 | Current owners and new entrants across the reference cohort. | The newest flagship alone. | PENDING: the reference cohort (several vendors, memory sizes, generations, used cards) is D1’s open box; the two tests per class are owed. |
| Proof enforcement D5 | Unmodified validators reject invalid, replayed and misbound proofs. | Official producers behaving correctly. | TEAM-REPORTED today: the verifier is on in consensus from block zero on the Igneum 2.0 devnet (facts row 2); the refusals on an unmodified validator against hostile submissions are D5’s exercise, owed. |
| Sustained proving Architecture and product | Declared workload, bounded backlog and tail-latency distribution. | Fast shards with unbounded queues. | PENDING: the earlier devnet’s 24-hour payout reading stands as history on the economics page; the 2.0 devnet’s own reading follows its observer. |
| Finality and recovery D5 | Consistent authority changes and documented partition behaviour. | A timeout labelled irreversible. | PENDING: rule v3 runs from checkpoint DAA 0 (the manifest); partition and recovery behaviour is D5’s exercise, owed. |
| User verification Architecture and product | Authenticated roots, execution outcomes and trust anchors. | Signatures over unauthenticated authority. | TEAM-REPORTED today: the light client, the receipt and the oracle verify certificates, headers and account proofs offline and name what they do not prove (/light, /receipt, /oracle); no independent review yet. |
| Operator control Pools and participation | Pooled payments without hidden transfer of governance or finality control. | A pool protocol name. | PROPOSED: the vote key committed into the member’s work is a pin (docs/design, the pool vote-key design), not yet shipped. |
| Independent operation D5 | No-founder exercise on the real implementation. | A centrally supported demo. | PENDING: the no-rescue network exercise is owed; the devnet is the project’s own machines, its rented fleet and a few outside laptops. |
| Commercial demand Architecture and product | Repeat paid external jobs and workable operator margins. | Devnet payouts or subsidised volume. | EXCLUDED from every revenue figure today: the external proving market is designed, not built; no external job has been paid. |
| Long-term funding D4 | Internal proving and security payments and maintenance runway. | Burn accounting or assumed appreciation. | MODELLED: the proving model on the economics page walks the halvings at today’s shard and key counts; the proving payment’s routing is designed behind its constant, burned in full today. |
| Leadership Leadership tests | Comparative results, adoption, retention and reliability over time. | A roadmap or unsupported rank. | EXCLUDED: no rank is claimed; the comparison set (Ravencoin KAWPOW, Ergo, Firo’s reference miner) is owed work, not a result. |
Source: docs/plans/igneum-2.0-plan.txt, section 23 (the acceptance scorecard) and the pins in docs/plans/igneum-2.0.md; the Today column is the facts page’s label for the rows each gate cites, and moves only with those rows. The five labels: TEAM-REPORTED, MODELLED, PROPOSED, PENDING, EXCLUDED. The public mirror follows master; a link that answers 404 is a file not yet synced.
A finding that moves a gate the other way, a placed or measured adversary that beats the served bracket or a reproduced shortcut in the served kit, earns the disclosure prize; the terms are on that page.
The release evidence packet
A source commit, exact parameters, the test procedure, the raw result, the independent-reproduction status, the review scope and the unresolved limitations accompany every material claim. On this site that packet is the facts page’s row: its Version or commit, Reproducible test, Result and Independent verification cells, with the limitations stated in the row. A claim without a packet is not served.
The wording ladder
What each rung needs before it is served: designed for GPU competitiveness (the objective only); team-tested (a procedure, a version and a result on the record); independently reproduced (an unaffiliated operator’s run); independently reviewed (a scoped review with its unresolved findings); top-tier contender (comparative evidence plus the operator proposition); category leader (never claimed without sustained adoption, and never with a number).
Not legal advice.