The public benchmark ships with the public testnet: no calendar month; ledger X33

The owner's ruling, 6 October 2026, the same as the roadmap's: the litepaper said the public benchmark with a leaderboard "is
January 2027" (For miners) and "ships in January 2027" (Questions miners ask). Both now read "The public benchmark with a
leaderboard ships with the public testnet." (the second keeps its tail: its source is public with the repository then, so you
run it on your own card and post the number). One gate the reader already knows from the roadmap's phase 5. docs/fud-ledger.md
gains X33; the 5 October answers that named the month stay as the history of the plan. The ledger page regenerated (179
entries, 0 leaks).

Checks: identity grep 0 hits on every served site file, link check 912 links across 16 pages 0 broken, ledger text 51 of 51,
contrast 32 pairs 0 under 4.5:1, orphan check 0 site headings, api tests 5 pass, no calendar month on the litepaper or the
home page.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

docs/fud-ledger.md

@@ -2237,6 +2237,15 @@ Answer: Dates were the plan of 3 October 2026; the gates are the plan. "Dates sl
 
 Evidence: `site/litepaper.html` Roadmap; `site/journey.json`; X31.
 
+### X33. The public benchmark dated "January 2027"
+"After X31 and X32 the litepaper still said the public benchmark with a leaderboard 'is January 2027' (For miners) and 'ships in January 2027' (Questions miners ask), a calendar month beside a roadmap that names none."
+
+Status: Fixed, stated (6 October 2026, night, the owner's ruling): both sentences read "The public benchmark with a leaderboard ships with the public testnet." (`site/litepaper.html`, For miners and Questions miners ask). The gate is one the reader already knows from the roadmap's phase 5. The 5 October answers in M1, X1 and the overclaims list that name January 2027 are the history of the plan and stay as written.
+
+Answer: The month was the plan of 3 October 2026. The benchmark tool is part of the testnet's go checklist, so it ships with the testnet; no month is given for either.
+
+Evidence: `site/litepaper.html`; `docs/plans/testnet-go.md`; X31, X32.
+
 ## Status updates, 4 October 2026 (round 4)
 
 - **F21** (the long-partition fork). Extended: a side locks alone when its own share of its own table reaches two thirds, at `t = W (2/3 - s) / (1 - s)`: 50/50 at 2,400 DAA s on the devnet (about 40 minutes), 10 days on mainnet; the 60 side of 60/40 at 1,200 DAA s (20 minutes), 5 days; the ledger's measured `W/(3R)` = 200 s is this formula at s = 1/2. At HEAD a second certificate at an index is kept, logged and ignored (`processes/finality.rs:650-655, 661-666`) and `fork_choice_lock` (`:886-901`) pins the node. Public text: `site/litepaper.html:511` says a third of the blocks is needed to split finality in a partition; the partition alone does it. Replacement sentence in `docs/review/round-4-2026-10-04.md` section 1 (b). Review id R4.1.5.

site/ledger.html

@@ -4,13 +4,13 @@
 <meta charset="utf-8">
 <meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover">
 <title>Igneum ledger: every criticism, answered</title>
-<meta name="description" content="Every criticism Igneum expects, in the critic's words, with what was done, the status and the date. 178 entries. Nothing deleted, nothing softened.">
+<meta name="description" content="Every criticism Igneum expects, in the critic's words, with what was done, the status and the date. 179 entries. Nothing deleted, nothing softened.">
 <link rel="canonical" href="https://igneum.network/ledger">
 <meta name="theme-color" content="#0C0C0E">
 <meta property="og:type" content="website">
 <meta property="og:site_name" content="Igneum">
 <meta property="og:title" content="Igneum ledger: every criticism, answered">
-<meta property="og:description" content="178 criticisms in the critic's words, with what was done, the status and the date.">
+<meta property="og:description" content="179 criticisms in the critic's words, with what was done, the status and the date.">
 <meta property="og:url" content="https://igneum.network/ledger">
 <meta property="og:image" content="https://igneum.network/og-small.png?v=3">
 <meta property="og:image:width" content="256">
@@ -18,7 +18,7 @@
 <meta property="og:image:alt" content="Igneum. Mined by GPUs. Proven by fire.">
 <meta name="twitter:card" content="summary">
 <meta name="twitter:title" content="Igneum ledger: every criticism, answered">
-<meta name="twitter:description" content="178 criticisms in the critic's words, with what was done, the status and the date.">
+<meta name="twitter:description" content="179 criticisms in the critic's words, with what was done, the status and the date.">
 <meta name="twitter:image" content="https://igneum.network/og-small.png?v=3">
 <meta name="twitter:image:alt" content="Igneum. Mined by GPUs. Proven by fire.">
 <link rel="icon" href="/favicon.ico" sizes="48x48">
@@ -121,20 +121,20 @@ details{margin-top:8px;font-size:14px;color:var(--ash)}summary{cursor:pointer;co
 <!-- nav:end -->
 <main id="main" class="wrap">
 <header style="padding-block:clamp(40px,6vw,72px) 8px">
-<div class="eyebrow">Ledger · 178 entries · regenerated from the repository</div>
+<div class="eyebrow">Ledger · 179 entries · regenerated from the repository</div>
 <h1>Every criticism, answered or conceded</h1>
-<p class="intro">This is every criticism the project expects, in the critic's words, with what was done about it and the date. 178 entries since 3 October 2026. Entries are never deleted; a status that changes keeps its history on the line. Where the critic was right the entry says Conceded. Where nothing has been done it says Open and names what settles it. The founder mined through the GPU years. Ethereum's move to proof of stake in September 2022 ended that income and the miners' place in that chain. This is one person building, with AI systems doing the engineering, the coin he wanted to exist for miners: GPU-mined, the miners are the provers, no founder allocation, every cost stated. Help is welcome and a team is wanted: cryptographers, node engineers, miners who will test. This ledger is the application form: pick an open row and write to <a href="mailto:hello@igneum.network">hello@igneum.network</a> with its id.</p>
+<p class="intro">This is every criticism the project expects, in the critic's words, with what was done about it and the date. 179 entries since 3 October 2026. Entries are never deleted; a status that changes keeps its history on the line. Where the critic was right the entry says Conceded. Where nothing has been done it says Open and names what settles it. The founder mined through the GPU years. Ethereum's move to proof of stake in September 2022 ended that income and the miners' place in that chain. This is one person building, with AI systems doing the engineering, the coin he wanted to exist for miners: GPU-mined, the miners are the provers, no founder allocation, every cost stated. Help is welcome and a team is wanted: cryptographers, node engineers, miners who will test. This ledger is the application form: pick an open row and write to <a href="mailto:hello@igneum.network">hello@igneum.network</a> with its id.</p>
 </header>
 <div class="tbl"><table>
 <thead><tr><th>Count</th><th>Status</th><th>Meaning</th></tr></thead>
 <tbody>
 <tr><td class="num">7</td><td><button type="button" class="chip" data-filter="Open">Open</button></td><td>Nothing has settled it yet. The entry names what will</td></tr>
 <tr><td class="num">62</td><td><button type="button" class="chip" data-filter="Conceded">Conceded</button></td><td>The critic is right. &quot;Stated&quot; means the public text says so; &quot;not yet stated&quot; means it does not yet</td></tr>
-<tr><td class="num">56</td><td><button type="button" class="chip" data-filter="Fixed or built">Fixed or built</button></td><td>A code, spec or text change answers it, with the commit or the page named</td></tr>
+<tr><td class="num">57</td><td><button type="button" class="chip" data-filter="Fixed or built">Fixed or built</button></td><td>A code, spec or text change answers it, with the commit or the page named</td></tr>
 <tr><td class="num">27</td><td><button type="button" class="chip" data-filter="Closed by rule or decided">Closed by rule or decided</button></td><td>A consensus rule or a decision by the owner answers it, dated</td></tr>
 <tr><td class="num">13</td><td><button type="button" class="chip" data-filter="Answered with evidence">Answered with evidence</button></td><td>A measurement or a simulation exists and is named</td></tr>
 <tr><td class="num">13</td><td><button type="button" class="chip" data-filter="Answered by design">Answered by design</button></td><td>A design rule answers it; no measurement is possible yet</td></tr>
-<tr><td class="num">178</td><td><button type="button" class="chip" data-filter="">All</button></td><td>Every entry. The sections: <a href="#m">Mining and chips</a>, <a href="#f">Finality and attacks</a>, <a href="#p">Proving and the zkEVM</a>, <a href="#e">Economics and the coin</a>, <a href="#g">Governance and the founders</a>, <a href="#c">Comparisons</a>, <a href="#l">Legal and regulatory</a>, <a href="#x">Launch and operations</a>, <a href="#d">Builders</a></td></tr>
+<tr><td class="num">179</td><td><button type="button" class="chip" data-filter="">All</button></td><td>Every entry. The sections: <a href="#m">Mining and chips</a>, <a href="#f">Finality and attacks</a>, <a href="#p">Proving and the zkEVM</a>, <a href="#e">Economics and the coin</a>, <a href="#g">Governance and the founders</a>, <a href="#c">Comparisons</a>, <a href="#l">Legal and regulatory</a>, <a href="#x">Launch and operations</a>, <a href="#d">Builders</a></td></tr>
 </tbody></table></div>
 <div class="toolbar"><input type="search" id="q" placeholder="Search the ledger" aria-label="Search the ledger"><span id="shown"></span></div>
 <h2 id="m">Mining and chips</h2>
@@ -1238,6 +1238,12 @@ details{margin-top:8px;font-size:14px;color:var(--ash)}summary{cursor:pointer;co
 <div class="status"><span class="badge b-fixed-or-built">Fixed, stated</span> <span class="did">6 October 2026, night, the owner's ruling): every calendar month is out of the roadmap. Each phase is worded by its gate in the shape phase 5 has: 1 &quot;Under way; closes when the specification is out for external review&quot;, 2 &quot;Under way; closes at its gate&quot;, 3 &quot;Live since 3 October 2026; closes at its gate&quot;, 4 &quot;Closes when the finality design passes external review and one rollup signs for the testnet&quot;, 5 &quot;Weeks away: when the go checklist closes&quot;, 6 &quot;After the testnet has passed its gate: 1,000 independent miners for 30 days and rollup proofs on time&quot;. The order is unchanged. The roadmap's lead reads &quot;Six phases from specification to a fair launch, with four public gates and no calendar dates: each phase closes at its gate.&quot; (<code>a repository file</code> Roadmap, <code>a repository file</code>, the home page's inlined journey). The 3 October 2026 start of the devnet is a fact, not a target, and stays.</span></div>
 <details><summary>The answer as first written</summary><p>Dates were the plan of 3 October 2026; the gates are the plan. &quot;Dates slip. Gates do not.&quot; was already the roadmap's own sentence, and the roadmap now says only the gates. The owner gives a month if he wants one.</p></details>
 </article>
+<article class="entry" id="X33" data-bucket="Fixed or built">
+<div class="head"><span class="id">X33</span><h3>The public benchmark dated &quot;January 2027&quot;</h3><span class="date">6 October 2026</span></div>
+<blockquote>After X31 and X32 the litepaper still said the public benchmark with a leaderboard 'is January 2027' (For miners) and 'ships in January 2027' (Questions miners ask), a calendar month beside a roadmap that names none.</blockquote>
+<div class="status"><span class="badge b-fixed-or-built">Fixed, stated</span> <span class="did">6 October 2026, night, the owner's ruling): both sentences read &quot;The public benchmark with a leaderboard ships with the public testnet.&quot; (<code>a repository file</code>, For miners and Questions miners ask). The gate is one the reader already knows from the roadmap's phase 5. The 5 October answers in M1, X1 and the overclaims list that name January 2027 are the history of the plan and stay as written.</span></div>
+<details><summary>The answer as first written</summary><p>The month was the plan of 3 October 2026. The benchmark tool is part of the testnet's go checklist, so it ships with the testnet; no month is given for either.</p></details>
+</article>
 <h2 id="p">Proving and the zkEVM</h2>
 <article class="entry" id="P23" data-bucket="Fixed or built">
 <div class="head"><span class="id">P23</span><h3>An unwound transaction leaves the node's view until its sender resends it</h3><span class="date">6 October 2026</span></div>

site/litepaper.html

@@ -624,7 +624,7 @@ body.all .pager{display:none}
       <section id="miners-ask">
         <h2>Questions miners ask</h2>
         <h3>Kaspa was GPU-mined too, and IceRiver shipped a chip within two years.</h3>
-        <p>Kaspa never promised chip resistance, and its hash was one fixed function, simple enough to put on silicon. Igneum's program is different every hour, its dataset grows past any fixed memory, and its program space widens every era, with no human involved. The benchmark tool ships in January 2027, and its source is public with the repository at the public testnet, so you run it on your own card and post the number to a leaderboard by card model. The paid independent cryptanalysis and the public benchmark are where a chip design that beats a GPU by more than 2x would show. And if a chip ever appears, miners are the ones who signal the response.</p>
+        <p>Kaspa never promised chip resistance, and its hash was one fixed function, simple enough to put on silicon. Igneum's program is different every hour, its dataset grows past any fixed memory, and its program space widens every era, with no human involved. The public benchmark with a leaderboard ships with the public testnet, and its source is public with the repository then, so you run it on your own card and post the number. The paid independent cryptanalysis and the public benchmark are where a chip design that beats a GPU by more than 2x would show. And if a chip ever appears, miners are the ones who signal the response.</p>
         <h3>Don't ASICs make a chain safer?</h3>
         <p>Three parts. First, what the chain asks hash to do. Hash picks who makes the next block. It does not protect history. A checkpoint locks when signatures reach two thirds of the weight of the last 30 days of blocks (specification section 3). A locked checkpoint is never reorganised by any amount of hash: fork choice runs among the tips that pass through every certified checkpoint. Rented hash has no weight today. It can mine blocks. It cannot rewrite anything older than a lock. A renter with 60% of the network holds 0.0% of the vote on day one (the finality simulator, table B); one matching the whole honest network reaches a third of the weight on day 20 and never two thirds. The lock is fast: median 1,018 ms behind the checkpoint on the three-node test network (engineering log, the finality harness), and on the live devnet the first lock came two hours after genesis, once the window was full. Reorganisations under the lock are shallow: at 1, 2 and 5 blocks a second the deepest honest reorganisation measured was 2, 3 and 7 blocks against a determination depth of 20 (ledger F7, round 2, the fast-time network with 100-ms links); across five continents blocks reached every node at p50 343 ms and p99 666 ms (the 12-node cloud network, 4 October 2026).</p>
         <p>Second, the cost the ASIC argument skips. Kaspa's hash went to a handful of chip owners within months: the IceRiver KS0 shipped in July 2023, 17 to 20 months after launch; hashrate went from under 100 PH/s to over 700 PH/s in months and the GPU share was negligible by late 2023 (the ASIC history, row 23, approximate for the share). Bitcoin's hash comes from two manufacturers and a few pools (approximate, from memory). The first chip's owner mines in secret with an edge for months: on Monero, 85% of the hashrate vanished at the April 2018 fork, and chips were found at over 85% again four months after the next fork (row 16). A chip does not add security to a chain; it moves the chain's security to whoever owns the chip first.</p>
@@ -645,7 +645,7 @@ body.all .pager{display:none}
         <p>One founder, pseudonymous, working with AI systems. The design, the hostile reviews, the code, the simulators and this document were produced that way, and the commit history says so. The software is shipped by Igneum Labs LTD, Unit IH-00-01-01-OF-01, Level 01, Innovation One, Dubai International Financial Centre. The design remains the work of one founder working with AI systems, reviewed in public through the ledger. What that does and does not mean: the measurements are measurements, reproducible from the commands in the engineering log; the simulators are code anyone can run; the design claims stay design claims until people with names have tried to break them. Every criticism the project expects is kept in a ledger with its honest answer, and the entries that were right are marked conceded; the ledger is published with the repository at the public testnet. No cryptographer is hired yet; the plan budgets one for phases 1 and 2, and external reviewers are named and paid before gate 3.</p>
         <p>The founders mine from genesis with disclosed addresses and the same software as everyone else, and hold no coins before block one. The team is pseudonymous and there is no team page. The mining addresses and the code history are published with the repository at the public testnet.</p>
         <h3>Where is the miner?</h3>
-        <p>On the devnet now. Igneum Ember runs on Windows, macOS and Linux, a HiveOS package exists, and the devnet's coins have no value. The public benchmark with a leaderboard by card model is January 2027. Pools come with the public testnet. The public testnet is weeks away: three seed nodes and the public RPC are up, and it opens when the go checklist closes. All of it before any coin exists. Nothing is asked of a miner before they can run something. The <a href="#ember">Ember section</a> says what is shipped and what is still owed.</p>
+        <p>On the devnet now. Igneum Ember runs on Windows, macOS and Linux, a HiveOS package exists, and the devnet's coins have no value. The public benchmark with a leaderboard ships with the public testnet. Pools come with it. The public testnet is weeks away: three seed nodes and the public RPC are up, and it opens when the go checklist closes. All of it before any coin exists. Nothing is asked of a miner before they can run something. The <a href="#ember">Ember section</a> says what is shipped and what is still owed.</p>
         <h3>Will my card still pay in a bear market?</h3>
         <p>Block reward and in-chain proving move with the price. Proving for other chains is priced in the customer's money, and it is a small market today. What Igneum can promise is that its miners' electricity cost in that market is close to power, because the card is already running on domestic power; the price they must charge is the subsidy they forgo, which falls as one over network hash. That is an edge over data-centre provers at scale and nothing more.</p>
       </section>