From a5d7b515d573469cb2c73195d60308b31e7cb325 Mon Sep 17 00:00:00 2001 From: igneum-labs <337424239+igneum-labs@users.noreply.github.com> Date: Thu, 8 Oct 2026 18:25:37 +0000 Subject: [PATCH 1/2] Igneum 2.0 gap table (the standard's profiles against today's values, main's word on the four F0 fields); Counter ASIC 3.0 status: the 19:0x to 19:3x lines (A05 and A03 closed, the chain-path acceptance fault found by lane D, the three object candidates, the batch replay, build-7/8/9, the coverage line, the freeze ruling) Co-Authored-By: Claude Fable 5.1 --- docs/plans/counter-asic-3-status.md | 10 ++++++++++ docs/plans/igneum-2.0-gap-table.md | 25 +++++++++++++++++++++++++ 2 files changed, 35 insertions(+) create mode 100644 docs/plans/igneum-2.0-gap-table.md diff --git a/docs/plans/counter-asic-3-status.md b/docs/plans/counter-asic-3-status.md index db3c40eaa..538e63000 100644 --- a/docs/plans/counter-asic-3-status.md +++ b/docs/plans/counter-asic-3-status.md @@ -473,6 +473,16 @@ THE REGISTRY ON MASTER AND ECO-05's FAIL (18:50 BST). The approved registry land MAIN'S THREE RULINGS (18:5x BST): ECO-05 serves as FAIL now in the standard's words on /acceptance and the economics page, naming the one passing world (10R at USD 0.03 per kWh at the corrected R of USD 31.65 M a year from ETC's era-6 reward 1.6384 ETC, lane 3's second explorer read at 18:49 on the Blockscout stats endpoint and block 25,497,000's record; the first page's 2.56 stale) and the failure regions and what moves it (the specialist ticket, the honest side's efficiency, the dataset floor), nothing softened; the AMD and Intel energy lane is a GPU-suite row under GPU-03's cohort on the hash lane with the fleet lane's rented AMD cards and PC 1's RX 7600 and the Arc tonight, 23:30; the genesis size is the founder's word at 20:00, default 4 GiB, the curve as served. The cube re-ran at the corrected R on both proving efficiencies with the verdict unchanged (0 of 54 cells per specialist on all three lines; db424d20 on counter-asic-4). A SECOND KILL BY NAME ON THE MAC (18:57 BST), THE REVIEW ROWS AND THE FINALITY AMENDMENT. The node lane, stopping its three Mac-side build chains for the shipper's version bump, killed every process matching "build-remote.sh --box" on the Mac, a kill by name against the standing rule (CLAUDE.md since 26a3cbe6), and took the pool seat's igneum-pool check on box 2, the hash lane's export and three hash-bound runs on the edc4fa84 epoch and its fuzz_parsers run on box 2, the enforced-proving lane's two prove-core and prove-host test runs on box 2 and the steward's 291ee6ae verdict runs on build-4 (the kaspa-p2p-flows run survived); every owner re-runs from its own log; the steward's verdict default moved to 19:25; the node lane's chains restart on the bumped sha; the node lane states its kills go by a pid file from now. The class stands as written on 8 October 12:5x: a lane's own convenience is never a reason; ad-hoc shell lines included. Main dispatched nine register rows (105 to 113) for an external source review of the mining algorithm (docs/analysis/review-2026-10-08/, landing; it examined the Mac checkout's older V2 to V4 crate, not class v6, and says so): findings A01 to A09 under the POW suite's cases as they fit, the review's harness the cross-check evidence, owners the hash lane (A02, A04, A06, A07, A08, A09 by 22:30), the census hand (A03 by 22:30), the attack seat (A05 by 23:00), the node lane carrying each verdict into the 23:30 freeze as fixed by construction, not applicable, or known open with a clock; RUNNING tonight, nothing PASS without the native test. The finality lane's amendment finality-boundary 29c8e86d8 (one clause: the two-thirds anchored test at any time, the majority test only past the window with the recovery on; the even split's jitter fact; the harness pass line per variant) given the word to land at 18:5x. Lane 3's registry write-back on class-v6-floor-sram 78a06c33 (ECO-05 FAIL, ECO-08 RUNNING, master's copy with two rows' live fields changed) lands through the research lane's 21:00 landing. The register's coverage at 19:0x: 113 pins, 113 owned; cases under the standard: 10 PASS (EVM-02 to 06; VER-03, 04, 05, 06, 08), ECO-05 FAIL, VER-01 and VER-02 FAIL by design, 62 RUNNING, 52 NOT RUN, 1 DEFERRED. +THE 19:0x LINES (BST). The fifty-eighth landing was refused by rule 26 on the registry (master's copy had taken the enforced-proving lane's 42 lines at 8f4affa80 and the steward's acceptance layer at e704b920: docs/plans/igneum-2.0-test-harness-map.md from tools/ci/test-map.json, 37 of 109 automated cases mapped to 17 cells, tools/ci/test-record.mjs the only writer of the live fields, tools/ci/p01-vectors.py; the evidence rules and the first write-back batch 200-417c4a57-b2 with 31 cases RUNNING landing by 19:15); rebuilt on master with the time strings alone changed to UK and re-sent. The review pack on master at 0ae450bd (evidence.md, results.json, harness.zip; the harness run on build-2 by the steward, all_results.json sha256 075281c3, every asserted anchor agreeing with the tree: the genesis program id 0xbcc1248b10cc90f2, the two closed-form hashes, the three census ids, the eight header-bound vectors; the v5 and v6 vectors outside its model, NOT RUN for that cell); the nine findings in the register as rows 105 to 113 with their case ids (A01 POW-01 the node lane's by construction; A02 POW-02/03, A04 POW-02, A06 POW-01, A07 POW-02, A08 POW-02, A09 POW-04 the hash lane's by 22:30; A03 POW-03 the census hand's by 22:30; A05 POW-05/06 the attack seat's by 23:00). The node lane's 19:10 line: the roll takes 291ee6ae (six suites green on build-1 at 18:50: 74/143/175/30/38/19; the canaries read the devnet-4 digest be5f4068 unchanged) with the shipper's rule 15 bump ef0f2ed8 (workspace version 2.0.1, nothing else) as release-2.0.0-node's tip; the freeze question's default taken (the class v5 freeze tree cbc5bd0a, pow-freeze.txt unchanged; the class-v6 line is the D1 object on class-v6-node, never devnet-4's); the pair placed about 19:12, the heal, fresh-join read and canaries by 19:35; the successor for the pool seat on ef0f2ed8 by 21:00 if the pool opens, 23:30 latest; the pin into prior/ by 21:00; the D1 object with the nine verdicts by 23:30; its pid files named (roll-chain.pid 23595, roll-suites.pid 23605, dn4seed.pid, node1-dn4.pid). build-6 GREEN at 18:57:17 (229 s on 6db270e88, 136 tests): igneum-build-6 = build@2.31.63.81, Cloud ccx53 in nbg1 (server 169417497), A record build-6.igneum.network, the lease tool 82cc0564, slots 2, pool cores 8 to 31; a side effect recorded (the Cloud project's primary-IP limit full; the HELD testnet seed3 briefly stopped to delete its unused IPv6 primary IP and restored to its pre-state); build-6 IPv4-only; the dashboard HOSTS list lacks build-4/5/6. The public mirror git.igneum.network refreshed to af1a2a02 (5,052 commits, 0 secret lines, 0 identity lines, every cited 2.0 path 200) with igneum-public-sync.timer on build-1 reporting staleness every 5 minutes; the gated rewrite stays Mac-only (the founder-strings list and the secret-rule files live on the Mac by rule; build holds no Forgejo key): main asked to rule, default (b) on demand, runs at 21:15 and 23:45. The fleet: no AMD retail card on any provider tonight (Vast with every filter lifted, RunPod none), GPU-03 on PC 1's RX 7600 and the Arc with the 9070 XT as the morning's reading; the layer-8-off stock rows done on the one-shot 5090 and 4090 (USD 0.44) with RunPod containers refusing the clock lock (knee rows to PC 1 by 20:30); the 3060 pod re-rented on a 570+ driver. The hash lane's layer-8-off read: nowin against its pair 5090 class v5 3.73 against 3.67 microjoules (+1.7 percent), class v6 6.19 against 6.07 (+1.9); 4090 4.94 against 4.82 (+2.5), 8.68 against 8.59 (+1.0); within one run's noise, under P03's 5 percent; the chip side minus 4 at the mean and minus 11 at the tail (1.85x and 2.27x against 1.93x and 2.40x). The family gate's acceptance read landed e77d9585d section 6.10: PASS (r 0.18 against 0.27 at width 4; the (c''') cost at width 4 from 13 to 2 percent; 0 hot sets, 0 over 1.2x at 2^20, worst 1.053x against 1.103x). The D2 row reads PASS at stock; the default to main: "+nowin" into the 23:30 D1 object if PC 1's knee rows read under 5 percent by 20:30. The hash lane's kill losses restarted (the suite green by 20:30; the P01 vectors on box 2 under nohup, the first pack by 19:40, all four by 20:20; the fuzz verdict 20:45; the paired 2 GiB read 20:15; the P01 first backend 21:45). The adversary lane's clocks: ADV-01/03/04 placed 32-lane core 21:00 (adv-f, 393,000 cells, six macros); ADV-07 the genesis comparator on adv-g 21:30; ADV-02 the memory model 21:30; ADV-08 and POW-03/04 restated 21:30; the review's harness as cross-check 23:00 if A05 lands by 22:30; its eight cases written back at 94f7ba7e0. The enforced-proving lane's seven rows on master at 8f4affa80 with the dependency field; its stages design docs/design/consensus-proof-stages.md (9549c42d5) in the gate; the key-succession fast-time case's first attempt stopped on the 60x file naming proving_payment_activation_daa (unknown to the succession line), the harness now drops keys a line lacks, rerun from 18:56. The finality amendment on master at 4b423dad8 (6.2 item 1 the two-thirds anchored test never lapses; 7 item 4 the even split's jitter; 6.7 the pass line per variant with the split50 recovery criterion). +MAIN'S TWO RULINGS (19:0x BST): the public mirror rewrite is (b), the founder-strings list and the secret-rule files on the Mac by rule and never on a box, on demand from the Mac after any landing a 2.0 page cites as a short job, never a loop (tonight 21:15, 23:45 and once after the 23:30 object), the build-1 timer reporting staleness to the build-server lane, which asks main for a run; the HELD testnet seeds are not to be touched again for any Cloud housekeeping without a line to main first. The D2 default taken: layer 8 off ("+nowin", class-v6 542cd7028) goes into the 23:30 D1 object and the served class string if PC 1's knee rows at the 1,300 lock read under P03's 5 percent by 20:30, with the three parts as its evidence record on the POW and ADV cases; else the layer stays, the row FAIL at the lock with the stock rows published; the acceptance page row shows the three parts and the rule either way. The site lane's landing on master at 93c52a27 (19:03; the first gate refused by rule 26 on the standard's text, the branch taking master's copies): /acceptance from the approved registry (the header, the counts bar, the gate cards, the sixteen suites, /api/acceptance reading the public git host every 60 seconds), ECO-05 FAIL on /economics, the litepaper and the facts row, /tuning, the dataset policy PROPOSED with the curve, the 2.0.1 note, the case ids on the facts rows. +THE P02 COHORT'S FIRST PASS (19:0x BST, the fleet, GPU-01's evidence), at stock on the class v6 kit's worker, every fingerprint as expected (hl-v6-all 59e6708e, hl-v5-win 84bfe258), check PASS: RTX 2080 Ti 13.96 / 27.96 MH/s at 239 W; RTX 3070 8 GB 18.57 / 37.16 at 187 W; RTX 4060 8 GB 9.57 / 19.11 (watts unmeasurable, power.draw 0.0, the 4060-tier fault); RTX 4070 Ti 12 GB 15.66 / 31.30 at 126 W; the 3060 (driver 550) and the 4070 (560) re-rented on 580-series hosts (the only 570+ 4070 on Vast at reliability 0.949 under the 0.97 floor, named on its row); the 1080 Ti booting; the second pass (foldrw and all at stock and the lock where the container allows it; the 1, 2 and 4 GiB packs on the 8 and 12 GB cards) running on every pod, the evidence under /srv/artefacts/tas// and the registry cells (GPU-01, GPU-03, POW-08; GPU-05 for the sizes) written after. The build-6 lane's open items with the build-server lane: the push.mjs HOSTS rows, the provision.sh step_lease_tool root-against-build read that left the lease tool uninstalled until placed by hand. + +THE FIFTY-EIGHTH LANDING AND THE 19:1x LINES (BST). The fifty-eighth landing on master at 52589a394 (the nine review rows with titles and case ids, the registry's times reading UK on master's copy, the record). A05 "Header binding and final digest deserve independent cryptographic review" closed by the attack seat at 19:04 on master ad5a54c5 (docs/analysis/binding-review-2026-10.md section 5a): the header and nonce binding FIXED BY CONSTRUCTION (a BLAKE2b-256 prehash over every header field plus 32 free bits of nonce_hi as the FNV input; the nonce entering every lane register once at initialisation; the lane hash a function of (H, nonce, program, dataset) alone), the ProgPoW-style final digest NOT APPLICABLE (the linear fold follows a per-epoch random program tested for output bias at 6 sigma, F8 uniform at 2^24 nonces, no fixed inner structure for a period); measured on the spec-exact replica: avalanche 128.02 of 256 bits per flipped nonce_hi bit (min 94, max 160) and 128.01 per flipped H bit, 0 collisions over 2^18 nonce_hi, a chosen byte of I[7] at 0.640 against the random 0.633; native tests 6 of 6 in bind plus the stateless-hasher test; no consensus change for 2.0 (the ProgPoW shape would be a class version with every vector moved, 2 to 5 percent of hash rate, not recommended); POW-05 written back. The hash lane's review fixes by construction on class-v6 (6d602859f plus a path fix, suite running, green by 20:20): A02 five non-load slots as shuffles over the five lane dimensions in a drawn order (all 32 lanes connected by construction; A09 not applicable as no rejection pass exists; 64 seeds x 4 classes under test); A08 a v6 mad never names its destination as its second source; A06 program.json authenticates every kernel text by BLAKE2b-256; A07 group alignment, tails and the low-32 rollover under test; A04 the acceptance executes the shadow (sub-version 3). The consequence: the v6 draw changes and hl-v6-all's id moves; main asked which tree freezes at 23:30 with the default (the post-review object only if green, re-exported, the census and the family gate's acceptance PASS on the new packs and the fingerprints paired by the freeze; else c245d50b9 with the five findings known open at "the next class cut"); lane D told to read the new packs as section 6.11 by 22:30. The fuzz verdicts (POW-01 and POW-02's malformed half, 19:06): the pack reader 10,000 mutated files through pf_load, 911 refused, 0 crashes, PASS; the Rust parsers 10,000 each, class strings and IGSD1 clean, the hex and era parser panicking on a multi-byte character (bind::unhex sliced a char boundary), fixed on class-v6. The steward's P01 part B done at 19:07, two hours inside 21:00: three parsers of external bytes, 10,000 seeded malformed cases each on build-2 (parser-malformed f0204947 over 417c4a57): igneum-exec DayStream::from_bytes 9,854 refused, 146 accepted as still-valid, 0 panics, slowest 37 microseconds; rpc::dispatch over nineteen igneum_ methods 7,957 refused, 2,043 accepted, 0 panics, slowest 152; igneum-miner pool::job_seeds 3,159 refused, 6,841 accepted, 0 panics, slowest 32; evidence build-1:/srv/artefacts/tas/p01-partb-20261008-01/; POW-06 RUNNING with that coverage. The enforced-proving lane's docs/design/consensus-proof-stages.md on master at d43c94c6c (stage 1 in code, the guest side green on build-2 at 19:06 with the inputs-commitment vector 0x911a87e4... pinned; stage 2 the payouts derived in the guest with BLS-in-guest the costed step; stage 3 the rewards from consensus data with two header commitments deciding its clock; every stage through a key succession); the both-pairs case found a 0.3.16 start check refusing the embedded prior pair, fixed (one daemon line on key-succession-node), rerunning from 19:07. The build-server lane: a lease-pool class on build-2 (seven GHOST waiters with dead processes up to 2 h old, one adv-class ghost ahead of every live release waiter), pruned and fixed in lease.sh (dead waiters pruned at every status and priority read; sha 74cab4eb on build-1, 2, 4, 5 and 6; 247b61de on build-server with build-6's provision.sh lease-step fix 05401922); the AX162 recipe staged ($S/build7/stage-box.sh , rescue to first gate in one run inside 30 minutes, waiting on IPs from main). The devnet-4 window at 19:05: DAA 7,016 of 7,200 (blocks 7,009, peers 4), finality not active by design, about 60 DAA a minute, the fill about 19:08; past DAA 7,800 without a lock is the incident. +MAIN'S FREEZE RULING (19:1x BST): the post-review object is the 23:30 D1 object only if its suite is green, the packs re-exported, the census (c''') read and the family gate's acceptance PASS on the new packs and the fingerprints pair on every platform; otherwise c245d50b9 freezes and the five findings ride as known open with "the next class cut"; one slide under ship-on-green: if at 23:30 the post-review object is inside thirty minutes of that full green the freeze slides once to 00:30 and no further; "layer 8 off" rides on its own 20:30 default either way. A03 closed by the census hand at 19:10 ahead of 22:30 (class-v6-census-all b10fe1351, census-packs.md section 6, the addrsite harness edit 2c76893e on build-4): the review's class v2 case reproduced (SHA256("igneum-review/139"), instruction 51, 0x0fffffff in 15.15 percent of the site's reads); the current class v5 object, the freeze's v5 seeds, hl-v6-all and two chain seeds under each class on the live dataset: worst address at any site 4 of 2 million and 8 to 9 of 33 million reads (2.7e-7), worst cell 3 of 262,144 and 5 of 4 million (1.2e-6), the Poisson maxima of a uniform stream, five orders under A03's class; cache-hit rates the era windows' by design and equal on v5 and v6 (1 GiB 100 percent; 256 MiB 39 / 42 / 36 percent; 64 MiB a quarter), the adversary's 72 percent the Devnet 3 program's window draw (0.719); verdict PASS on the address axis for both, v6 equal at the address and better on the stride bit, no generator cause (A03's v2 cause the saturated source, closed by (c') and (a')); the x16 rows and an LRU-trace figure owed. + +THE 19:2x LINES AND THE 19:30 COVERAGE (BST). Capacity: the founder's three AX162-1 dedicated servers assigned (188.40.146.44/.45/.46, FSN1-DC24) as build-7, build-8, build-9, staging in parallel since 19:18:44 on the build-server lane's recipe (rescue to first gate in one run inside 30 minutes); the lease classes mapped so the P01 campaign, the object matrix, the census, the family gate, the review and the fast-time case take every freed core first; main's order that every row waiting on cores re-clocks to the new boxes as they go green. The build-server lane's rolling site deploy stopped by its pid file at 19:16:27 (ad5a54c5's Vercel upload hung nine minutes, the fault; 0ae450bd reached the edge at 19:05:29); the site lane deploys its own landings; the node sha ef0f2ed8 embeds proving/igneum-prove/elf/prior, a path on key-succession-pin and not on master, so its pair builds only beside that branch's tree. The node lane at 19:17: two object candidates cut and gating, (a) class-v6-node dab9259f (the generator at c245d50b9, a65e4c5a; the default literal on every network: the v6 floor never, class_v6_dataset_steps [(0, 4096 MiB)], class_v6_family_flags 0xf; the dataset-policy digest 70a6c703; the harness tree b3528574 at v5-fasttime 92bf6a7f0; on build-2) and (c) class-v6-node-review 50589749 (dab9259f plus the post-review generator; on build-1); "+nowin" as a fifth family flag 1 << 4 by default; the D1 record drafted on d1-record e0c8ec7f8 (docs/spec/01-lottery-hash.md version 0.3: 1.0 the frozen object by digest, 1.4.8 generator 6, 1.8.7 and 1.13.4 the dataset policy, 1.16 the parameters the freeze fixes, 1.17 the class v6 vectors open to 01:00); the rule v4 rows on fin-v4-rows 63dc9de2f (the four bee41b5e runs into sim/results_v2.md with the criterion per variant; v3.mjs's split50 pass line keyed on finality_v4_recovery), the HEAL=400 reruns on the successor pair on build-2 (about 20:10); the successor 12424341 placed on both boxes with canaries green and named to the pool seat. The hash lane at 19:2x: the post-review sha moved to class-v6 04442d9ca (6d602859f did not compile, a private import, fixed by 9b687f631; the suite queued on box 2, verdict by 20:00); A FAULT FOUND BY LANE D ON THE PRE-REVIEW OBJECT: accept::is_class_v4_shape set fold and rw aside but not nowin, reg64 or reg64_chain, so on the chain's own path a +nowin or +reg64c program was judged by the class v2 parts alone (no fresh-source rule, no saturated-source check, no index floors, no 32-attempt cap); the family harness's own predicate hid it from every census so far (the census PASS lines were the harness's full rule, which is the rule wanted and now the crate's); fixed in 04442d9ca with the test that every v6 flag keeps the class v4 shape and the attempt cap; the default sent to main: a third candidate (b) = (a) plus that one fix, gated beside the two; never (a) as it stands. The steward at 19:23: the evidence rules on master at e2adc2c1 (a PASS needs existing evidence, evidence moves with its row, a stale manifest never PASS, no run_status without the approval); the write-back batches lost rule 26's race three times (the registry a hot file), the fix 5877760c landing 19:35 (a landing carries its batches as tools/ci/batches/.json and merge-to-master.sh replays them onto master's copy at the merge, self-tested where both sides add rows); the three batches riding it (200-417c4a57-b2 with 30 cases RUNNING, the review harness cross-check on POW-01, part B on POW-06); the P01 pods run hl-v5-win first (reference by 19:45) and hold the v6 packs for the re-export (about 20:10). The update-return lane at 19:21: PC 2 (1ccfe586) started the 2.0.0 install at 19:19:42 through its own OTA path (no administrator prompt; the window host away at 19:19:47); PC 1 (ae432dc7) fetched and verified the Setup exe at 18:58:48 ("installs at the next safe moment"), the install pushed through the signed-jobs channel at 19:11 (its relay agent silent since 17:58, the logon task's takeover by a signed job); UX-01 RUNNING. The attack seat's POW-05 row on master at 3555af7a. The census lane's A03 landed on master at cdbdda05 (19:18) by the landing hand. The research lane's landing hand: twenty-seven landings. Lane D's 6.11 read: the class-string port built and proven on 542cd7028 (the class's own 83-point table, nowin, fold, rw and reg64c composed from the string), the chain-predicate mode in the diff, the run staged on build-4 (five minutes to rebuild, 25 to run), 22:00 with the ids and sha by 20:30, 22:30 plus the delay after 21:00, the default a run on the latest mirror sha at 21:30. The coverage line at 19:2x to main: 113 pins, 113 owned, 30 open, 44 in flight, 34 landed, 5 passed; cases 10 PASS team-run, 3 FAIL, 62 RUNNING, 52 NOT RUN, 1 DEFERRED; profiles P12 FAIL, P04 FAIL, P03 PASS at stock with the lock at 20:30, P01/P06/P08/P09/P10 RUNNING, P00/P02/P05/P07/P11/P14/P15/P16 NOT RUN, P13 DEFERRED; four BLOCKED fields for the founder's word in F0 (the workload W, the fault model's thresholds, the 30-participant study, the second and third AMD configurations); the gap table docs/plans/igneum-2.0-gap-table.md written; the rows waiting on cores re-clocked (the post-review suite 20:00 to 19:50 on build-7, the P01 references 20:20 to 20:05, the fast-time case to the first 16 free cores, the census re-run 22:30 to 22:00 on build-8). +MAIN'S WORD ON THE FOUR BLOCKED F0 FIELDS (19:3x BST), written into F0 by the steward as "main's word, 19:3x": the workload W (P07) the pilot plan's shape (one SP1 program pinned by vk, the shard fixture's size class, compressed proofs, one job an hour the floor and the fleet's measured rate the ceiling, requests/hour from the pipeline record's day); P00 and P08's fault model and thresholds the finality spec's own (two thirds of the sliding table, the anchored table under rule v4, the recovery variant as the founder's default, the 40/40/20 fixture, the spec's expiry cases); P10's 30-participant study NOT RUN ("unaffiliated participants not yet recruited"), kept open, never a staff run; P02's second and third AMD configurations the 9070 XT and the RX 7600 on PC 1 as the two retail AMD cells, rented AMD cells added when a provider lists one, the row PARTIAL until then. The freeze default confirmed by main: the fallback is (a) with the acceptance fix and its census re-read, cut now as the third candidate; if neither (c) nor the fixed (a) is fully green by 00:30 the freeze holds for the fixed (a)'s green with the clock named, never a known fault frozen. The gap table docs/plans/igneum-2.0-gap-table.md (one row per profile P00 to P16: the cases governed, today's value, the verdict today, the first confirmatory run) landed with this entry, ahead of the 20:30 ask. + A SHARED-DEVNET FACT FROM THE FLEET (not this lane's, with the shipper and the infra lane): the Hetzner live seed 188.245.5.161:26611 is still on the old override object (digest eada4bda) 1 h 40 min after the 0.3.20 sweep (the fleet never touches Hetzner nodes, so it was outside the sweep); the 0.3.21 wipe canary c22-1 took five digest-mismatch rejects from it; an app with the packaged peers is refused at the seed and syncs through node1 and the hub only, a fresh joiner with only the seed cannot join, the 14 voters and the hub are unaffected; the owner puts the floor file ov16-floor-900000.json (sha 294f1f80) and the c4459193 pin on it. 0.3.21's STAGING (the node lane): the order dry-merges onto 55768f88 with nothing moving to 0.3.22; the late-join fix is 52e96c94 (70e4601e rebased onto 55768f88, exec suite 33 green with both new tests); f067f7c1, b0444f51 and 437f0438 merge clean in order; 2e32d5f6's one conflict (DST_ADDRESS beside pool-finish's DST_BINDING in consensus/core/src/finality.rs) kept both; the live-file digest eada4bda after each (every switch at never); the staging waits on the shipper's sweep-end word; the re-pin held. PC 2 DOWN AGAIN (main, 16:5x UK): the founder takes PC 2 down for cable work (PC 1 back but his desk); both PCs out of the sweep's waves, each updates on its poller on return; no PC job to PC 1; the Windows G1 completed before the outage, nothing reruns. 0.3.21's SECOND GATE LINE on 55768f88 (sha256 279b1b690e854fc9): the ten-minute mixed-version gate beside the 5899f603 pair, 13:37:40Z to 13:47:52Z, SUMMARY PASS (one digest b0afb2ee on five nodes; 223 new and 381 old blocks accepted by the old hub, 0 rejected; counts equal at 319, 486 and 604 through both clean joins and the restart step at 13:45:22Z; no panic); the node lane's two lines on 0.3.21's first candidate complete, in plan 6.9 on ca3-v4-node; the fleet's set on it (the bare-child 12 GB line, the wipe, the kept read, the cases) is the fleet's. 0.3.21's FIRST GATE LINE on 55768f88 (sha256 279b1b690e854fc9, the string read back; pairing igneum-pow 8c728ca3 at byte 5): the digest gate 13:35:41Z to 13:37:19Z SUMMARY PASS (a89be8a7 on both binaries with the peers; db9a85f9 refused, no peer; the live file's eada4bda unmoved); the ten-minute mixed-version gate from 13:37:40Z, line about 13:50Z. The 0.3.21 order as the shipper sent it: 55768f88; f067f7c1 and 70e4601e; b0444f51; 6eb21fc9; db28d331; then the re-pin from 8bdcbdd8 on the coordinator's word; suites between, the digest read after every one; the mirror's release-0.3.20-node back at the pin c4459193, release-0.3.21-node open at 55768f88. THE LATE-JOIN COMMIT (N9's second half, the node lane): 70e4601e on the box mirror as branch proof-hold-fix, from c4459193, two files (igneum/exec/src/proving.rs, protocol/flows/src/v10/proving.rs); the gap was the fetch side on the joiner (the served record ran the native check against the joiner's trailing exec state before anything was stored, the check refused it, the proof was never held, the body rule read "not held" for 20 s and failed the IBD); the fix holds the proof by hash before the checks (the pool entry still needs them) and the serve side says when it holds fewer than asked; the exec suite 32 passed at 13:26Z with the known-failed shape first, the flows check green 13:28Z, igneumd on build-1 at the 0321 worktree path built 13:32Z, sha256 17649eeb2f7d1290, string read back; with the testnet lane (the resume form, B alone); it joins the 0.3.21 staging as its own commit. THE WIPE CANARY ON c19-1, c4459193 (sha 45be9b02d1b002f5, string read back): FORM END rc 0 at 13:50:53Z. Wipe synced 13:35:50Z (57 minutes, inside the 98-minute class); mining 13:36:00Z to 13:47:07Z, 66 mined, 66 accepted, 0 rejected, isSynced true at the tip throughout; the hub holds 41 of its blocks in its last 700 with 0 rejects (13:47:09Z); the restart on its kept datadir at 13:47:15Z: the old process stopped at once (the new process's first lock line seven seconds after the marker; the watchdog held nothing, the b7cc37e7 fault closed), synced again at 13:48:39Z after 84 s, 109 templates read with max 3,432 ms and 0 timeouts; the kept read on pool-1's 0.3.17 copy on the same pod passed at 13:38Z (the rewrite line once, a clean second start). The pin's set on c4459193: the digest gate PASS, the mixed-version gate PASS, the wipe canary PASS, the kept read PASS, the restart PASS, the 12 GB line proves and verifies (paid is a race, not a gate); CASES END from c20-1 (about 14:50Z) is the last pin line. THE INTEROP FACT stands from the void run: the 5899f603 hub accepted 235 object-byte-5 blocks from the 8097d600 node with 0 rejected, one digest on all five nodes on the live sixteen-field file. The gates: the digest test and the kaspa-pow vector test (the amended devnet epoch-0 id 1a4230699a6b9c60 must equal, c120d7963abdcd96 must differ, the v3 control unchanged) on the box; the mixed-version Devnet 2 gate (the amended 0.3.20 node beside a 5899f603 node for ten minutes on the live file without the v4 fields) after the Mac build; the fresh-join canary the 0.3.20 cut's | | Main's rulings (7 October, morning) | no generator change to v4 on the live devnet; the record's null is the window model with numbers, sent by the hash lane to the attack-pass lane so AP-F8-1 re-gates against it; a fault beyond the model (a low-entropy source at site 15) stops at the coordinator with the two options priced (a 0.3.19 class amendment before the flip, or the flip held at the floor), nothing shipping without the founder's word; the tighter tail, an acceptance bound on the hot-set share, is a CLASS V5 item (sent to the v5 lane a6410f3b8abefb762 with the 64-seed census as its gate; the bound's number follows from the model) | diff --git a/docs/plans/igneum-2.0-gap-table.md b/docs/plans/igneum-2.0-gap-table.md new file mode 100644 index 000000000..9eebab8ca --- /dev/null +++ b/docs/plans/igneum-2.0-gap-table.md @@ -0,0 +1,25 @@ +# Igneum 2.0 gap table (the Test and Acceptance Standard's profiles against today's values) + +Built by the coordinator for main's 20:30 ask on 8 October 2026 (19:2x UK). One row per profile: the cases it governs (from the registry on master), today's value in the team's own words, the verdict today against the profile as approved, and the clock of the first confirmatory run under the standard's procedure. "Team-run" means a run with evidence before the procedure; nothing reads PASS under the standard until the steward's test-record writes it. + +| Profile | Title | Cases governed | Today's value | Today against the profile | First confirmatory run | +|---|---|---|---|---|---| +| P00 | Frozen scope and approval | 14: GOV-01 GOV-02 GOV-03 GOV-04 GOV-06 GOV-08 POW-07 POW-08 ROT-03 ROT-04 VER-04 OPS-08 LEAD-07 LEAD-08 | The standard approved as proposed at 18:2x (P13 deferred); the registry on master with an owner on every case; F0 (the release manifest) not yet signed: the steward's test-map (37 of 109 automated cases mapped to 17 cells) is on master at e704b920; the genesis identity frozen (devnet-4 4cdcc488, digest be5f4068, chain id 4465); the workload W, the fault model and the claim inventory open | NOT RUN (BLOCKED fields: W, the fault model's thresholds in F0) | F0 signed by the steward: 23:30 tonight (GOV-01), the claim inventory with it | +| P01 | Correctness and negative-test depth | 69: GOV-05 GPU-04 GPU-05 GPU-07 POW-01 POW-02 POW-05 POW-06 POW-07 ADV-01 ROT-01 ROT-02 ROT-03 ROT-04 ROT-05 ROT-06 EVM-01 EVM-02 EVM-03 EVM-04 EVM-05 EVM-06 EVM-07 EVM-08 ZKP-01 ZKP-02 ZKP-03 ZKP-04 ZKP-05 ZKP-06 ZKP-07 ZKP-08 CAP-02 CAP-05 CAP-07 CAP-08 INC-01 INC-02 INC-05 INC-06 INC-07 FIN-01 FIN-02 FIN-03 FIN-04 FIN-05 FIN-06 FIN-07 FIN-08 VER-01 VER-02 VER-03 VER-04 VER-05 VER-06 VER-07 VER-08 OPS-02 OPS-03 OPS-04 OPS-05 OPS-06 UX-02 UX-03 UX-04 UX-05 UX-06 COM-04 LEAD-06 | P01 part B done (19:07): three parsers, 10,000 seeded malformed cases each, 0 panics, every case under the bound; the pack reader 10,000 mutated files, 911 refused, 0 crashes; the Rust parsers 10,000 each, one real fault found and fixed (bind::unhex on a multi-byte character); the one-million full-hash vectors per backend generating on box 2 (four packs by 20:20), the CUDA backend on the P01 pods from 21:45, all backends by 23:30 (AMD and Arc on PC 1 and PC 2); EVM-02 to 06 and VER-03 to 06, 08 PASS on devnet-4 at 18:45 (team-run, not yet under the procedure); VER-01 and VER-02 FAIL by design and disclosed | RUNNING; 10 PASS team-run, 2 FAIL by design (VER-01 voter table as trust anchor, VER-02 no SP1 verifier in the client), no invalid acceptance observed | P01 part A (the vectors) first backend 21:45, all 23:30; the parser half PASS tonight on the steward's write-back by 19:25 | +| P02 | Hardware coverage and reproducibility | 12: GOV-03 GPU-01 GPU-02 GPU-03 GPU-04 GPU-05 GPU-06 GPU-07 GPU-08 CAP-01 UX-08 LEAD-02 | The cohort tonight: NVIDIA 2080 Ti, 3070 8 GB, 4060 8 GB, 4070 Ti 12 GB read at stock (fingerprints as expected); 3060 and 4070 re-rented on 580 drivers, 1080 Ti booting, 5090/4090/3090 on P01; AMD: no rentable retail card on any provider, PC 1's RX 7600 and the morning's 9070 XT only; Apple: the Macs; Intel Arc B580 on PC 2; three unaffiliated operators and the seven-day soak not started | NOT RUN against the profile (3 AMD configurations impossible tonight; 2 Apple pending; the soak not started); the NVIDIA rows RUNNING | the full NVIDIA cohort rows 23:30; the AMD gap stated to the founder (a second AMD card needs a purchase or a loan); the soak starts on the v2.0.1 entry | +| P03 | Candidate improvement and honest-card budget | 8: GPU-02 GPU-03 POW-03 POW-04 POW-07 POW-08 ROT-02 ROT-07 | Layer 8 off against its pair at stock: +1.7 and +1.9 percent per hash on the 5090, +2.5 and +1.0 on the 4090 (within one run's noise, under 5 percent); the knee rows at the 1,300 lock on PC 1 by 20:30 (RunPod containers refuse the lock); the genesis dataset size is the baseline, not a P03 cost (main's ruling) | RUNNING; PASS at stock, the lock pending | 20:30 (the knee rows); the D1 object decision on them | +| P04 | Scoped specialist-competition target | 14: POW-03 POW-04 POW-05 ADV-01 ADV-02 ADV-03 ADV-04 ADV-05 ADV-06 ADV-07 ADV-08 ROT-07 ROT-08 LEAD-03 | Placed rows today: the multi-family adversary at hit 0.50 reads 1.85x same node and 2.27x a node ahead without layer 8 (1.93x and 2.40x with it); the bracket 1.5x to 2.1x same-node is a FAIL to work against; the 32-lane placed full core (adv-f, 393,000 cells) lands 21:00, the genesis comparator (adv-g) 21:30 | FAIL (R_E above 1.5 same-node on every placed row today) | 21:00 (ADV-01/03/04 placed 32-lane), 21:30 (ADV-07, ADV-02); the chain's value stays FAIL until a change moves the placed row | +| P05 | Measurement and inference protocol | 0: | Pre-registration exists for ECO-05 (the register frozen before results) and the census harness (sub-version 3); the standard-wide pre-registration (metrics, cohorts, holdout seeds, run order) is not yet a document | NOT RUN (no case bound to P05 in the registry; the protocol document owed) | the steward writes the protocol into the harness map by 23:30; first use on the P01 confirmatory runs | +| P06 | Memory and support policy | 4: GPU-05 ROT-06 ECO-07 CAP-02 | Measured today: the 12 GB tier mines and proves together at 4 GiB (12.0 of 12.3 GB on the 3060) and loses co-residence at 5.5 GiB (13.6 GB); the 8 GB tier refuses 5.5 GiB by VRAM; the component memory budget not yet published | RUNNING (GPU-05 size cells on the 8 and 12 GB pods tonight); the budget NOT RUN | GPU-05 rows 23:30; the budget document with the dataset decision at 20:00 | +| P07 | Proof service capacity and fairness | 15: ZKP-08 CAP-01 CAP-02 CAP-03 CAP-04 CAP-05 CAP-06 CAP-07 CAP-08 INC-03 INC-04 INC-05 OPS-01 COM-01 COM-04 | W not frozen; the proving benchmark per stage (CAP-01 to CAP-08) starts on devnet-4's first paid segment after the first lock (the window fills about 19:08); the 72-hour run at W not started | NOT RUN (W BLOCKED until frozen) | CAP rows by 15:00 tomorrow as set; W frozen by the founder's word (asked with the F0 fields) | +| P08 | Fault assumptions and recovery | 25: ROT-01 ROT-02 ROT-03 ROT-04 ROT-05 EVM-08 ZKP-08 CAP-07 INC-04 INC-06 INC-08 FIN-01 FIN-02 FIN-03 FIN-04 FIN-05 FIN-06 FIN-07 FIN-08 VER-05 VER-06 OPS-01 OPS-02 OPS-04 OPS-08 | Rule v4 (the anchored table, majority-continuity recovery) in the spec at 4b423dad8 and in the node at acd9d067, not in any live path (devnet-4 has rule v4 at never); the harness: the recovery run as designed (side A 51.26 percent recovered at index 11, side B paused, 0 conflicts, 0 disagreement), the pause-only fault found and fixed; the real-network partition case open | RUNNING (FIN-07, FIN-08 harness rows; ROT rows on 417c4a57 green); the live-network case NOT RUN | the HEAL=400 reruns on the successor pair tonight (about 20:10 tables); the first live partition drill after the roll | +| P09 | Security and bounded resource requirements | 30: GOV-07 POW-06 EVM-01 EVM-03 EVM-04 EVM-05 EVM-06 EVM-07 EVM-08 ZKP-01 ZKP-02 ZKP-06 ZKP-07 INC-05 VER-01 VER-02 VER-03 VER-04 VER-05 VER-06 VER-07 VER-08 OPS-02 OPS-03 OPS-05 OPS-06 OPS-07 UX-05 UX-07 COM-08 | The internal attack pass F1 to F10, the binding review (A05 closed at ad5a54c5), the review's nine findings (five fixed by construction on class-v6, A03 and A05 closed, A01 by construction, A09 not applicable); key succession green on 291ee6ae; no external scope by the in-house rule; the disclosure prize the only outside check | RUNNING (zero unresolved critical findings known; the resource bounds measured on the parsers) | the review verdicts by 22:30, the D1 object 23:30; the prize page 23:00 | +| P10 | Ordinary-operator product targets | 11: GPU-06 GPU-07 OPS-07 UX-01 UX-02 UX-03 UX-04 UX-06 UX-07 UX-08 LEAD-02 | UX-01: the Windows 2.0.0 entry live 18:44, both PCs' MINING-ON read-back by 19:25; the Mac fresh install on the mini at 11.0 MH/s (18:13); 30 unaffiliated participants not recruited | RUNNING (UX-01 to UX-03, UX-07 tonight on the canary); the 30-participant study NOT RUN | UX rows 21:30 to 22:00; the study is a founder decision (recruitment) | +| P11 | No-founder exercise and independence | 4: INC-08 OPS-01 OPS-08 LEAD-05 | 92 devnet boxes are the fleet's own; 27 distinct miner keys in ten minutes at 18:40 are the team's; no unaffiliated operator yet | NOT RUN | after launch; the builder programme's first outside node | +| P12 | Five-year coexistence envelope | 24: ADV-04 ADV-06 ADV-07 ROT-08 ECO-01 ECO-02 ECO-03 ECO-04 ECO-05 ECO-06 ECO-07 ECO-08 CAP-06 INC-01 INC-02 INC-03 INC-04 INC-06 INC-07 INC-08 UX-03 COM-03 LEAD-03 LEAD-04 | ECO-05 run on a register frozen before results, R corrected to USD 31.65 M: FAIL (one of sixteen worlds sustainable under the two-vendor rule at 10R and USD 0.03; in it the GDDR7 machine's best core cell 1.46 to 1.70, cohort median 2.9 to 3.2; p90 fails everywhere); served as FAIL | FAIL | the AMD and Intel energy rows (GPU-03) 23:30 move the honest side's efficiency; the cube re-run on them tomorrow | +| P13 | Maintenance continuity | 1: COM-07 | DEFERRED by the founder | DEFERRED | none | +| P14 | Genuine commercial and developer proof | 10: CAP-08 INC-02 INC-07 COM-01 COM-02 COM-03 COM-04 COM-05 COM-06 COM-08 | no paying buyer, no external jobs; the reference apps and the DEX serve on devnet-4 | NOT RUN | after launch | +| P15 | Comparative contention threshold | 5: COM-05 LEAD-01 LEAD-02 LEAD-03 LEAD-07 | no peer set pre-registered | NOT RUN | the steward's F0 names the three peers by 23:30 (LEAD-01) | +| P16 | Observed durability and claim freshness | 5: LEAD-04 LEAD-05 LEAD-06 LEAD-07 LEAD-08 | devnet-4 born 17:14 today; 0 elapsed days on the release family | NOT RUN | 90 days from the final compatible release | + +Counts at 19:2x UK: P12 FAIL; P04 FAIL; P03 RUNNING (PASS at stock, the lock at 20:30); P01, P06, P08, P09, P10 RUNNING; P00, P02, P05, P07, P11, P14, P15, P16 NOT RUN; P13 DEFERRED. Four fields BLOCKED confirmatory runs until main's word at 19:3x UK, now given and written into F0 by the steward: (1) the workload W (P07) = the pilot plan's shape (one SP1 program pinned by vk, the shard fixture's size class, compressed proofs, one job an hour as the floor and the fleet's measured rate as the ceiling, requests/hour declared from the pipeline record's day); (2) the fault model and thresholds (P00, P08) = the finality spec's own (two thirds of the sliding table, the anchored table under rule v4, the recovery variant as the founder's default, the 40/40/20 fixture, the expiry cases as the spec lists them); (3) the 30-participant study (P10) = NOT RUN, "unaffiliated participants not yet recruited", the row kept open, never a staff run; (4) the second and third AMD configurations (P02) = the 9070 XT and the RX 7600 on PC 1 as the two retail AMD cells tonight, rented AMD cells added when any provider lists one, the row PARTIAL until then. From 721afe162f78b70be8fba0a0b2febd840fbbc8bb Mon Sep 17 00:00:00 2001 From: igneum-labs <337424239+igneum-labs@users.noreply.github.com> Date: Thu, 8 Oct 2026 18:30:31 +0000 Subject: [PATCH 2/2] The window audit records F6: a node with no peers holds the worker, never a worker fault (the founder, 19:25 BST, v2.0.2) Co-Authored-By: Claude Fable 5.1 --- docs/design/app-audit-2026-10-08.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/design/app-audit-2026-10-08.md b/docs/design/app-audit-2026-10-08.md index 0ee224f67..6dc72ed0e 100644 --- a/docs/design/app-audit-2026-10-08.md +++ b/docs/design/app-audit-2026-10-08.md @@ -358,4 +358,5 @@ Recorded as the founder's call, read through the shipper; they override section | F3 | The four interface words on the wallet and the window | included, executed, proven, finalised (docs/spec/finality-guarantees.md section 9); a locked block is finalised even in a pause, the pause sits on the status strip, no block reads "finality not active" | the window's block inspector and the scene's words (cards-201); the wallet's History row (`app/igneum-wallet/ui/app.js` stateWord, branch wallet-words-20 on master) | | F4 | One positioning line | the hero keeps it; `#s-positioning` under Updates is gone | cards-201 | | F5 | The watchdog's words while the node serves no epoch state stream | "waiting for the node's execution state for this epoch", never "the worker did not load its program" | `app/igneum-app/src/watchdog.rs` on cards-201 | +| F6 | A node with no peers holds the worker, never a worker fault (19:25 BST on the mini: the worker idled for lack of templates and the watchdog blamed it, "did not come back within 180 s of the miner restarting it") | whenever the node reports zero peers or no template for the window, every watchdog clock holds (the restart grace included) and the card reads "no block templates: the node has no peers" (or "…answers none for the window"); the node line reads "Node: no peers, dialling the seeds" | `app/igneum-app/src/watchdog.rs` (`tick(now, node_ready, no_peers)`, `held_by_node`), `engine.rs`, `ui/app.js` on branch peers-202 for v2.0.2 |