Merge master 37bcb15f into gpu-ledger under the master-landing lock

This commit is contained in:
igneum-labs 2026-10-09 12:17:35 +00:00
commit 23e419cdba
8 changed files with 256 additions and 18 deletions

View file

@ -375,6 +375,27 @@ flight per warp, a window shape that keeps the page set hot), measured as a pair
bit-exact fingerprint, the gain in MH/s per card and the new nJ per hash; (3) one line to main at the decider, one at the cause,
one at the first fix pair. Recovering the loss halves every card's USD per MH/s at no gain to the chip: it is the phase B lever.
## 8f. The ledger order (the founder, 12:5x UK; binding; the deliverables reordered)
The primary objective within five hours: the statement "Someone can build a chip, but ordinary GPU owners remain competitive,
the supplier cannot obtain a lasting overwhelming advantage, and the network does not depend on emergency intervention to survive"
made true and verifiable. The lab's lanes feed the GPU NETWORK LEDGER (the LEDGER lane a101aa8329d1e82bf assembles; it does not
re-measure) FIRST: (1) every live GPU chain measured the same way on the same rented 4090 and 5090 in one session each (Igneum v6
at 4 GiB, KAWPOW via ProgPoW 0.9.4 at the live DAG, FishHash, Etchash via the pinned chfast hashimoto at ETC's current DAG,
Autolykos2 if the in-house rule and the clock allow), the set v3 board ratio and the ProgPoW-premise ratio per chain, the two-phase
rows with each chain's actual reward split (only Igneum pays provers), and the E9 Pro calibration line (ADVERSARY models the one
real chip against Etchash; the gap to its public rate and power is the model's calibration, stated); (2) the proving row flips
LIVE on the PROVING LIVE lane's on-chain evidence (af561127dc1bc7044, one full epoch of paid rows, by 16:00; today's read: 663 paid
v1 segment records to 30 keys on Devnet 4, payments paused since the hub roll, the cause under fix); (3) the comparative-review row
(what other chains publish about their resistance, verbatim with source) so the ledger's claim is checkable; (4) the hash candidate
search continues fail-closed at lower priority (the 520k-ALU point and the headroom row close their records; no new families).
Clocks: the ledger table on the record 15:30, the kit 16:30, the page 17:30. Every row MEASURED or WITNESS with its source;
"pending" never blank; the BUILD STEWARD a3d365ef4a3a107a4 fills any idle box the lab names. The ledger's registry cell:
ledger:cross-chain beside lab:candidate on R15-09, NOT RUN until the kit's rows reproduce; its paths: the scoreboard table.md and
README.md at the box master's sha at 15:00, the conventions on the ctl-v6 and ctl-progpow-094 rows. Correction to 8c.11: the
32 GB prototype-shard clause is Devnet 1's; on Devnet 4 (fees_v1_activation_daa 0) a 24 GB NVIDIA card proves the v1 shard and
aggregates beside its miner now; the 16 GB tier holds no shard.
## 9. The lane briefs, one line each
- CONTROLS: the four controls as rows of the table: `ctl-v6` from the record and re-measured on the cohort; `ctl-progpow-094`

View file

@ -0,0 +1,45 @@
# Proving live on Devnet 4: the on-chain record (9 October 2026)
The 1.5x scoreboard's phase B row reads "a GPU earns the proving share of the block reward and a hash chip cannot". This page is the evidence that the proving share is paid on the live devnet to GPUs proving beside their miners, read from the chain and nothing else. One epoch is 3,600 DAA; Devnet 4's DAA runs at 1.0 per second (63,577 at 11:59:15Z to 63,902 at 12:04:30Z), so an epoch is one hour.
## The rule being exercised, by file and line (node 27f54124, the 2.0.3 line)
| what | where |
|---|---|
| 20 percent of every block subsidy to the proving pool, 80 to the producer | consensus/core/src/igneum.rs:44 (`PROVING_POOL_SHARE_PERCENT`), :87 (`proving_pool_share`) |
| a carried record pays its shard part of the pool credit to the record's payout address when valid, verified and first | igneum/exec/src/proving.rs:551 (`carried_payouts`) |
| a v1 segment (8 chain blocks, 8 shards + one aggregation) pays as one record, 1,000 bps of the credit to the aggregator | consensus/core/src/proving.rs:638 (`split_pool_credit`); igneum/exec/src/proving.rs `segment_status` Proven |
| fees v1 from DAA 0 on the devnet (the shard is the calibrated v1 size, 30,000 pgas, never the prototype) | consensus/core/src/config/params.rs:2307 (`DEVNET_PARAMS.fees_v1_activation_daa: 0`); the node reports `fees.v1ActivationDaa 0`, `shardBudget 0x7530` |
| what a prover reads and submits | `igneum_getProvingStatus`, `igneum_getAssignedShards`, `igneum_submitProofRecord`, `igneum_submitSegmentRecord`, `igneum_getSegmentRecords` (igneum/exec/src/rpc.rs:1342, :1443, :1628) |
## What proves today
The fleet's prover stack on rented RunPod and Vast boxes: `tools/fleet/box-prover.py` (one loop per box, beside the box's kit-2 miner, MINER=none so the miner is never paused) driving the served 0317 prover pair (`igneum-prove-host` sha256 71bc2438…, `igneum-prove-export` 263bf4ce…, SP1 6.8.1, shard program id 0x2b1a81cb…, aggregator id 0x474678f3…, the pair the node pins) and the SP1 GPU server. The same binaries are what the 2.0.3.1 HiveOS package wraps; the Mac and Windows apps carry the same prover, on by default at 23,552 MiB or more (app/igneum-app/src/provedefault.rs:23-24). Cards: RTX 4090 (24,564 MiB), RTX 3090 (24,576), L40S and RTX 6000 Ada (48 GB) as aggregators. Measured on a 4090 beside its miner: one 8-block segment in 117 to 185 s end to end (shards 48 to 52 s, aggregation 57 to 61 s), peak 13,523 to 14,899 MiB; a 16 GB card cannot hold the shard (the LAB's floor rows).
## Baseline before the restart (read 11:50:22Z, lp-4090-02's node, chain id 4465, executed tip 31,719, DAA 62,833)
| counter | value |
|---|---|
| paid v1 segment records since genesis | 663 = 653.93 IGN |
| distinct prover keys paid | 30 (median 4 segments a key, maximum 230) |
| payout addresses | 3 (the fleet's wallets) |
| paid v0 shard records (the pre-segment path) | 6,474 = 7,196 IGN |
| proving pool balance | 27,706 IGN |
| carried records refused as duplicates ("segment already paid") | 952 of 2,199 carried |
| carried records refused as late ("unproven", after the 600 DAA deadline) | 461 |
Evidence file: build-1:/srv/artefacts/proving-live/prov-ledger-4465-tip31719-115022Z.json (sha256 bd3f53c18c3ffa20354ea62ade9fd5e7a5794202a71c3c369a5be71484f7143a), every segment from genesis with its paid row and carried records.
Why payments had stopped at 11:15Z: Devnet 4's finality paused at 11:15:57Z under the hub roll (signing weight 4 to 25 percent of the frozen table), and every fleet prover gates on a finality pause (the 8 October build claims only below the finality-settled block; the V6-08 build holds after 600 s). The gate is the prover's own policy; payment never depended on finality (`carried_payouts`). The provers were restarted as generation 2 at 11:59Z with the gate lifted and the chain paid again from 12:02Z.
## The epoch of evidence (12:02Z to EPOCH_END)
EPOCH_TABLE
## The sentence the row carries
EPOCH_SENTENCE
## Access to proving work (main's question of 13:1x UK)
Segments are allocated by first valid record: 8 assignees per shard drawn from the keys in the record window hold a 10 DAA exclusive window (consensus/core/src/proving.rs:26, :30, :255, :305), after which any key may prove and the first valid record carried is paid; no stake, no queue; leases are off on the live nodes. A newcomer competes equally from its first record; a prover on a synced node claims within one 15-second pass (lp-4090-02 claimed 15 s after its restart). With about 227 segments an hour on this devnet and 120 to 185 s a proof, 8 to 11 provers saturate the work and every prover past that dilutes the fixed 20 percent as 1/N; about a third of carried records today are duplicate proofs. The rule change is docs/design/proving-claim-order.md (node change after 2.0.3; nothing on the chain today).

View file

@ -74,6 +74,124 @@ candidate (build-1:/srv/artefacts/lab/NOT-RUN-amd-intel.md); the hourly provider
| a HiveOS prover beside the miner | a named 2.0.3.1 item beside snapshot sync, with the memory and VRAM rules from this row; no new research | NOT RUN: scheduled by the release lane | the release lane aa4391fd50c62e28f |
| the 4 GiB proving cap defined precisely (8c.10) | which of the mining state, the proof-generation allocation, the verifier requirement or the advertised hardware profile it limits | NOT RUN | CONTROLS (the definition), ADVERSARY (the economics) |
## The read-headroom row (8c.8), answered 12:4x UK (CONTROLS and SEARCH, WITNESS)
| card | achieved sector reads per second on v6 at 4 GiB (rate x 256) | the activation bound (JEDEC-family timing approximations, named so) | nJ per 32 B sector read (stock) | the fold | the ILP lever (SEARCH, in-session ABBA) | reading |
|---|---|---|---|---|---|---|
| RTX 4090 | 7.86 G | at its tFAW form, 7.9 G | 26.4 to 28.4 | the whole-sector load free (a32x = a4); the full fold +1.0 nJ (+3.7 percent) | cand-ilp4 rate +0.00 percent, joules -0.64 (8,560 against 8,615); cand-ilp2 +0.00 / +0.00 | AT the limit: no card-side headroom; the ALU in the reads' shadow |
| RTX 5090 | 17.6 G | within a third of its tRC form | 18.9 to 19.8 | the full fold +1.2 nJ (+6.2 percent) | not yet paired | AT the limit; flat from 1 to 8 GiB (no TLB cliff for a flat stream) |
| RTX 5080 | 8.97 G | CONTROLS owed | | | | |
| RTX 3090 | 7.91 G (capped pods) | CONTROLS owed | | | | |
The miner-side lever "more loads in flight per core" is CLOSED on v6 by these rows; the phase B lever on the card is its memory
system itself. The "2.4x at 4 GiB" reading is WITHDRAWN (a contention fault of the CONTROLS lane: the 4 GiB bench shared the card
with the sector sweep; clean ABAB on a 5090: the 4 GiB object costs 3 percent of rate against the 1 GiB research pack).
## The shipping row's facts (the release lane, 12:5x UK, release-2.0.3 at 034cdad1, app/igneum-app/src)
The Mac and Windows apps carry the prover (SP1 6.8.1 through igneum-prove-host), ON by default on an NVIDIA card of 23,552 MiB or
more (provedefault.rs:23-24; a 24 GB card reports 24,564), mining or not, on Linux or Windows with WSL2; OFF with the reason on 16 to
24 GB, under 16 GB, Windows under 32 GB RAM, Apple silicon, AMD-only; the prover refuses to start under 12 GB (provedefault.rs:31) and
a card under 12 GB holds the prover or the miner, never both (engine.rs:41, :2717). HiveOS: none (h-run.sh has no prover section);
the HiveOS prover is SCHEDULED as a 2.0.3.1 item beside snapshot sync (cut by 18:00 UK, the rule-33 canary on a 24 GB 4090 by
19:00). A 16 GB card proves no shard today: the floor 13,874 MiB for an empty shard and 15,670 beside the miner (provedefault.rs:8);
the v1 shard (30,000 pgas, 4.7 M cycles) 20,434 alone, 22,210 beside the miner; the devnet's prototype shards until the fee switch
at DAA 210,000 need 32 GB (28,307 alone, 30,039 beside; VRAM_MB_PROTOTYPE_SHARD 31,000, provedefault.rs:27, :135); aggregation
16,751 MiB with the miner (24 GB; prover.rs:1122); no smaller instance exists (provedefault.rs:9 open). The Hive package applies the
app's device.rs:63 mode table (Simultaneous at or above 23,552 MiB, ProveOnly, MiningOnly). Phase B therefore reads LIVE today only
on Windows and Mac where a 32 GB NVIDIA card is present, NOT LIVE on the 24 GB tier until DAA 210,000 and on HiveOS until the cut.
## Results of record, 13:0x UK
- THE DECIDER (COHORT, uncapped 5090 pod 55012544, 575 W default, driver 580.173.02, worker f5f3846c, 250 x 2^24, three runs
each, one session; build-1:/srv/artefacts/lab/ctl-v6-decider/vast-55012544/): the 4 GiB signing object 68.63 MH/s at 410.4 W =
5,979.9 nJ per hash, twin 4,806.2, f 0.804, spread 0.46 percent, fp b1f90e91cadb15b6 PASS; the same program at 2^28 (1 GiB)
70.63 MH/s at 414.7 W = 5,871.2 nJ (fp 01f51b9d4805e5e6); the research pack hl-v6-all as staged under tas/same-work-20261008-01
(program id 0x4de7b836cc40a4ea, not the l8off kit's 0x9d40978601a7df2a) 70.63 at 402.2 W = 5,694.8 nJ. VERDICT: the 4 GiB
object costs this worker 2.9 percent of rate and 1.8 percent of joules per hash against its own 1 GiB export; occupancy
identical (96 registers, 20 blocks per SM, 3,400 resident lanes per SM); reads 17.57 G per second at 4 GiB against 18.08 at 1
GiB. The 3.4 against 7.9 G reading was CONTROLS' instrument; withdrawn. The uncapped 5090 ctl-v6 cell: 5,979.9 nJ at stock =
3.88x (3.07 to 4.50) on set v2's same-node board; the 5090 knee stays the record's 2.60x.
- The TLB rows (CONTROLS, both cards, mode a4 at 118 loads, build-1:/srv/artefacts/lab/controls/frozen-v6/tlb/): the 4090 8.02 /
7.92 / 7.87 / 7.84 G reads per second at 1 / 2 / 4 / 8 GiB (26.07 to 26.81 nJ per read), the 5090 18.11 / 17.76 / 17.60 / 17.52
(19.11 to 19.77 nJ): a flat random stream loses 2 to 3 percent of rate from 1 to 8 GiB on either card, no cliff; the layer-8
windows at 2^30 touch the whole 4 GiB as a flat stream does; the live object's cost is the 2 to 3 percent page-walk margin.
- The 4 GiB cap defined (CONTROLS, 8c.10): the MINING DATASET floor and nothing else: docs/spec/01-lottery-hash.md lines 849 to
850 (4,096 MiB from genesis, one step, no later step; the dataset policy 70a6c703, register row 10; the cache 2^26 words, line
434); the proof-generation allocation carries no 4 GiB figure (proving/igneum-prove/host/src/memory_profile.rs TIERS lines 115 to
121: full 26 GiB free, 24gb 20 GiB, 16gb 14 GiB, small 0; the ELF manifest pins no memory line); the verifier is independent of the
dataset size (spec 01 line 702: at most 4,096 item derivations per unit from the 256 MiB cache; the F2 row 10.63 ms per warp);
the advertised hardware profile (docs/design/app-audit-2026-10-08.md row F8) is constrained only through the miner's resident set
pushing a co-resident prover into the small tier (memory_profile.rs line 117).
- ctl-progpow-094 at the live DAG (CONTROLS): the official CUDA kernel's mix digests at Ethereum epoch 871 (block 26,154,532, DAG
8,380,217,984 bytes) equal the CPU reference's on both nonces: F1 holds at the live size; the live rate on the rented 4090 at
stock 58.75 / 58.76 MH/s (0.96 TB/s of coalesced 256-byte entries) against 62.58 at the 1 GiB DAG: the live DAG costs 6 percent;
the by-construction read-only twin gpu/pp_twin built, rows queued; the KAWPOW live size (epoch 609, 6,182,403,712 bytes) queued.
- ctl-coop-arx on the 5090 (CONTROLS, stock, sm_120): 105.3 M units per second at 72 ops (1.72 TB/s, the DRAM ceiling; the twin
103.8), 14.32 at 1,032 and 3.66 at 4,104 (ALU-bound, equal to the 4090's 14.18 / 3.69); five chain lengths F1-complete (CHAIN 86
fingerprint 84f43aecf5d8a8cd on CPU and GPU).
- THE PROVING CORRECTION (PROVING LIVE and the release lane): the prototype-shard 32 GB clause (provedefault.rs) is Devnet 1's
(params.rs:3082 LIVE_13); Devnet 4 runs fees_v1_activation_daa 0 (params.rs:2307 on 27f54124; the node reports shardBudget
30,000 pgas), so a 24 GB NVIDIA card proves the v1 shard and aggregates beside its miner NOW (13,523 to 14,899 MiB peak beside
the miner on the fleet's 4090s, 117 to 120 s per 8-block segment, 0.99 to 1.88 IGN paid); on chain 4465 at tip 31,719 (11:50Z)
663 paid v1 segment records = 653.93 IGN to 30 prover keys; 0 segments proven in the last 600 blocks (payments paused since the
hub roll at about 11:00Z, the cause under fix). The proving row reads NOT LIVE "paid on Devnet 4 to 30 keys, epoch evidence
pending" until docs/analysis/class-v6/1p5x/lab/proving-live.md lands with one full epoch of paid rows (by 16:00). Phase B
therefore reads live today for the 24 GB tier on Mac and Windows once that record lands, and on HiveOS from the prover package's
entry (cut by 18:00); the 16 GB tier holds no shard.
- X10 pairs: the first 4090 pair carried valid v6 rows (8,692 nJ at 30.69 MH/s, f 0.859) and valid X10 rates (x10b 66.1 M
lane-works per second at 118 loads = the v6 pair's 30.69 x 256/118 within 1 percent: memory-bound exactly as v6; the x10b ladder
64 / 96 / 118 / 128 loads 122.1 / 81.3 / 66.1 / 60.9 M scales as 1/loads) but ZERO watts on every X10 row (the 40-batch default
ran a quarter second, under the sampler's 8 s warm-in); kit r3 (sha 323e3970) sizes the batches per variant (45 to 85 s), adds
cand-x10's fixtures and an x10b by-construction twin (-DX10B -DTWIN: the address rule kept, the fold one xor per loaded word,
the mix and shuffles removed; its address stream a dependent chain of the same count and width, named so in twin_addr), and the
driver refuses any row with watts 0.0 at staging; both pairs re-rented on uncapped 4090 and 5090. ADVERSARY's interim: the
Sector card from its rate at the pod's v6 watts, 4,039 nJ per lane-work MODELLED-from-rate (bounded below at about 3,470 by the
twin's ALU share), the cheapest DRAM board (650 nJ) 6.2x on the 4090 at stock.
- THE LEDGER ORDER (the founder, 12:5x UK; the LEDGER lane a101aa8329d1e82bf): the lab's lanes feed the GPU NETWORK LEDGER first:
every live GPU chain measured the same way on the same rented 4090 and 5090 in one session each (Igneum v6 at 4 GiB, KAWPOW via
ProgPoW 0.9.4 at the live DAG, FishHash, Etchash via the pinned chfast hashimoto at ETC's current DAG, Autolykos2 if the in-house
rule and the clock allow), the set v3 board ratio and the ProgPoW-premise ratio per chain, the two-phase rows with each chain's
actual split (only Igneum pays provers), the E9 Pro calibration line (ADVERSARY models the one real chip against Etchash; the gap
to its public rate and power stated as the model's calibration). COHORT's ledger session is renting (v6, FishHash full and twin,
ProgPoW 1 GiB class now; the live-DAG binary pp_harness_26154532 from CONTROLS pulled in if it lands in time, else a second short
session); CONTROLS' Etchash harness is built and F1-checked against chfast at blocks 0 and 12,750,000 (ETC epoch 425). The ledger
table on the record at docs/analysis/class-v6/1p5x/ledger/README.md 15:30, the kit 16:30, the page 17:30; the registry cell
ledger:cross-chain beside lab:candidate on R15-09, NOT RUN until the kit's rows reproduce. The candidate search continues
fail-closed at lower priority (the 520k-ALU point and the headroom row close their records; no new families).
- The 4090 decider CLOSED (CONTROLS, one quiet session, stock, the 4 GiB signing pack): the kit zip 4 worker f5f3846c 30.661 MH/s
at 20 x 2^22 and 30.693 at 50 x 2^24; the build-1 worker 804a6f7f 30.663 and 30.692 on the same pack and shape; the 1 GiB
research pack 31.313: the two builds are the same instrument to four figures, the batch shape moves nothing, the live 4 GiB
object costs the 4090 2.0 percent of rate (3 percent on the 5090); the 13.16 was the shared-card read, withdrawn
(build-1:/srv/artefacts/lab/controls/frozen-v6/decider-4090.log). ctl-progpow-094's by-construction twin on the 4090: 77.42 MH/s
at the 1 GiB DAG and 60.20 at the live 8.38 GB DAG against the full kernel's 62.58 and 58.75: at the live size the card is at
its memory limit (the ALU hidden under the reads). ctl-fishhash on the 5090: F1 PASS (fingerprint f841605125ce375e equal to
the 4090's), 45.37 MH/s full against 39.71 for the twin (19.73 / 17.75 on the 4090). The F2 row re-run on the same pinned core:
10.440 ms per warp for the signing object at 2^30, 5.134 for the class v4 calibration (frozen-v6/f2-verifier-build5.txt).
- CONTROLS' done line (13:0x to 13:1x UK): the four controls and the ledger rows staged under build-1:/srv/artefacts/lab/controls/
with SHA256SUMS (frozen-v6 with tlb/, coop-arx, progpow-094, fishhash, sector-read, etchash, autolykos; 25 MB). Autolykos2 landed
in-house and bit-exact (hashlib reference against the CUDA harness at N = 65,536 and at Ergo's live N = 227,251,815, 7.27 GB;
216.2 / 201.8 MH/s full / twin on the rented 4090; the live-block end-to-end row owed). coop-arx's OpenCL text F1-complete on two
OpenCL platforms at all five chain lengths (the AMD tier runs the moment a card is reachable; Metal owed). Open on that lane: the
knee rows (every rented pod refuses the lock; COHORT's VM-host lock hunt reports by 14:30), the Metal text, the Ergo live-block row.
- ADVERSARY (12:5x to 13:0x): phase B tier rows on the on-chain read (commit 82330b04c; 47f16b86f with Etchash on the mirror): the
24 GB-and-up NVIDIA tier on Windows and Mac LIVE on Devnet 4 and out-earning the board chip in phase B (the GPU's contribution per
TH after electricity 0.341 against the chip's 0.288 after its recurring cost at ten cents on the flat path); HiveOS NOT LIVE until
the 2.0.3.1 package; the 16 GB tier never (mining share only, 0.046 per TH behind the chip). ctl-etchash as a control (64 x 128 B
reads over about 3.3 GB) with the calibration line: the modelled DRAM board 765 nJ per hash against the shipped Antminer E9 Pro's
598 (3,680 MH/s at 2,200 W, the public figure as the ledger lane quotes it): the model 1.28x pessimistic for the chip, a witness.
Phase A and B for Ravencoin, Ethereum Classic and Iron Fish in their own units (commit d7db3e596, README section 14): no fleet
recovers a board chip's spend on any of the three on any path (each chain's 24-month mining emission under one design cost: RVN
about USD 2.9 M, IRON 1.4 M, ETC 83 M at a 10,000-board fleet); phase B with no prover income: on Ravencoin the chip's operating
advantage stands in full at USD 0.123 per TH; on ETC the mining revenue per TH (0.0087) is below the board's recurring cost (0.031)
and the E9 Pro's electricity alone (0.017), a loss on both sides at ten cents. The reading: on every chain in the set the board
chip's phase B advantage is real and its phase A recovery is not at today's emissions; the proving share is the one term that lets
Igneum's live GPU tier out-earn the chip in phase B.
- The boxes (the build steward, 13:1x): the lab's ended box runs' pid files removed as stale after each pid's command line was read
dead; the steward's defaults on build-4, build-5 and build-6 stand until a lane claims with a live pid file.
## Open rows (NOT RUN)
| row | owner | clock |

View file

@ -0,0 +1,44 @@
# Proving claim order (9 October 2026)
How segments are allocated among provers today, what it wastes, and the rule change proposed for the node after 2.0.3. Nothing in this document changes the chain today. Approved as a design item by main at 13:2x UK on 9 October 2026, after the PROVING LIVE lane's on-chain read.
## The rule today, by file and line (node 27f54124, release-2.0.3 line)
| step | rule | where |
|---|---|---|
| assignment | 8 assignees per shard, drawn deterministically from the distinct prover keys seen in the record window (`assign(epoch_seed, block, shard, window)`) | consensus/core/src/proving.rs:26, :255 |
| exclusive window | inside the first 10 DAA after a segment only an assignee's record is paid; after that every key may prove it | consensus/core/src/proving.rs:30, :305 |
| payment | the first valid record carried in a block is paid; every later record for the same segment is refused "segment already paid" | igneum/exec/src/proving.rs:551 to :572 (`carried_payouts`), `segment_status` Proven |
| pool share | 20 percent of every block subsidy, split over the segment's shards with 1,000 bps to the aggregator | consensus/core/src/igneum.rs:44, :87; consensus/core/src/proving.rs:638 (`split_pool_credit`) |
| leases | V6-08 leases (300 DAA, three abandons an hour, 120 DAA penalty) exist in the node but are node-local and OFF on the live nodes (`igneum_getProvingStatus` reports `leases: null`; `IGNEUM_PROVING_LEASES` unset) | igneum/exec/src/proving.rs:110, :129 |
| the prover's pick | every whole, open, unpaid segment of the last 600 chain blocks whose deadline (last DAA + 600) is at least 240 DAA ahead, ranked by FNV-1a(first, key): a per-key random order | tools/fleet/box-prover.py `candidates()` |
No stake, no queue, no price. A new key is not an assignee until its first record is carried (10 seconds of exclusivity it cannot use, nothing more); from then on it competes at first-valid-record-wins with the same random order as every other key.
## What it costs, measured on Devnet 4 (chain id 4465)
Read on 9 October 2026 at 11:50:22Z from lp-4090-02's node (`igneum_getSegmentRecords` for every one of 3,965 v1 segments from genesis to chain block 31,719; the file is build-1:/srv/artefacts/proving-live/prov-ledger-4465-tip31719-115022Z.json, sha256 bd3f53c18c3ffa20354ea62ade9fd5e7a5794202a71c3c369a5be71484f7143a).
| carried segment records | count | share |
|---|---|---|
| paid (first valid record) | 663 | 30 percent |
| refused "segment already paid" (a duplicate proof of a paid segment) | 952 | 43 percent |
| refused "unproven" (carried after the segment's deadline) | 461 | 21 percent |
| refused "block ... is not chain block N on this chain" (proved on a fork) | 77 | 4 percent |
| refused on the chain link ("segment ... does not chain to ...") | 46 | 2 percent |
| total carried | 2,199 | |
In the morning's run alone (chain blocks 28,000 to 30,999, about 06:00 to 11:00Z, 30 to 40 provers on one chain): 148 segments paid, 369 duplicate records refused, 109 late records refused. Two and a half duplicate proofs for every paid one: with 30 to 40 provers over about 22 claimable segments at a time (the margin window is 360 DAA wide at 2 DAA per chain block and 8 blocks per segment), the per-key random order collides by chance, and every collision is a 120-second GPU proof thrown away.
Capacity: 3,600 DAA an epoch = about 1,817 chain blocks = about 227 segments an hour at 0.505 chain blocks per DAA; one 4090 proves a segment in 120 to 185 seconds beside its miner, so the work saturates at 8 to 11 provers and every prover past that dilutes the fixed 20 percent as 1/N. The 663 paid segments went to 30 keys with a median of 4 and a maximum of 230 per key; the skew is uptime (which boxes were on the chain when), not the rule.
## The proposal (node change after 2.0.3; nothing on the chain today)
Two consensus-free changes, both node-local, both deterministic from data every node already holds:
1. Template side (the producer): when a template is built and the pool holds more than one verified record for a segment, carry the record of the key whose FNV-1a(first, key) is smallest, not the first received. A duplicate still costs the prover its proof, but the pick no longer depends on network arrival order, so a prover that ranks itself can predict whether its proof will be the one carried.
2. Prover side (box-prover.py and the app's prover): claim a segment only when the key's rank by FNV-1a(first, key) among the keys in the record window is below ceil(K / M), with K the number of keys in the window and M the number of claimable segments in the margin; otherwise take the next segment in its own order. With the template rule above this makes the carried record and the claimed record the same one in expectation, and the duplicate rate falls to the rate of keys that join or leave inside one margin window.
Default: the prover side ships first (a script change, no node release); the template side rides the first node cut after 2.0.3 with a fast-time case (two provers, one segment, the lower rank carried). Measured target: duplicates under 10 percent of carried records over an epoch, read the same way as the table above.
What this is not: not a lease (leases are node-local and cannot order claims across boxes), not a stake, not a queue a newcomer waits in. A new key's rank is as random as any other's from its first record.

View file

@ -20434,7 +20434,7 @@
"plan_status": "NOT RUN",
"run_id": "lab-20261009-01",
"evidence_path": "docs/analysis/class-v6/1p5x/lab/README.md; docs/analysis/class-v6/1p5x/lab/table.md",
"updated": "2026-10-09T11:45:28.201Z",
"updated": "2026-10-09T12:15:20.071Z",
"evidence_record": {
"requirement_id": "R15-01",
"decision": "NOT RUN",
@ -20455,8 +20455,8 @@
},
"claim_impact": "none",
"reviewer": "",
"at": "2026-10-09T11:45:28.201Z",
"note": "The lab's interface and the candidate table at the fan-out: the frozen v6 control carried from the record (the house 5090 at its knee 4,011 nJ per hash, board power; the X0 amendment 5b rows: the DRAM board 2.35x same node WITNESS, the N2 die 7.8x the worst credible), the cohort rows for the 3090, the 5080 and the AMD and Intel tiers NOT RUN, adversarial set v1 pending; the three other controls (ProgPoW 0.9.4 reference, FishHash, the cooperative ARX candidate) NOT RUN with their clocks. No score is the lab's until the cohort and the adversary rows are in; R15-01, R15-08 and R15-09 stay NOT RUN until read. X10 (cand-x10) joins the table NOT RUN with its per-lane assignments and clocks; COHORT's ctl-v6 denominator set is in flight on eight rented pods. 12:1x UK: adversarial set v1 on the table (the frozen v6's same-node board 2.57x, 2.04 to 3.00, the fused tail CLAIMED until the routed lanes land; the die 11.4x as a coexistence row); the coexistence table (interface section 8b) added as the scoreboard's headline; SEARCH's first screen recorded as SCREEN rejections. Still NOT RUN: no cohort score until COHORT's eight rows are read back. 12:2x UK: set v2 (the routed fused-ARX lanes) makes the v6 board 2.60x a WITNESS; the ctl-v6 coexistence table (the board holds at every price; the N2 die pushes the GPU owner out above 14,300 dies at USD 0.10) is the headline; X10 SCREEN with the card modelled (the board 3.00x at 118 loads). Still NOT RUN: the cohort rows in their timed runs. 12:3x UK: the first cohort cells (ctl-v6 at stock on rented 5090, 5080 and 3090 pods: the worst cell the 3090 at 8,429 nJ = 5.46x on set v2's same-node board, PARTIAL, the dataset size under decision after CONTROLS measured the live 4 GiB object at 2.4x the 1 GiB research pack's rate); X10's first measured cell (cand-x10b on the 4090 at stock 3,653 nJ per lane-work = 5.8x on the board; the fold buys nothing); set v3 (routed 64-register and multiply-xor lanes); the fourth to sixth review rulings (8c); the 4 GiB rule (8e). Every row still NOT RUN until read. 12:4x UK: ctl-v6's first full score over the NVIDIA cohort at stock (the worst cell the RTX 4090 uncapped 8,751 nJ = 5.67x on set v2's same-node board; every cell at 4 GiB, the earlier 2.4x reading an instrument artefact, corrected once); the two-phase rows (ADVERSARY 545f3f8a0, 36d17b15c): phase B NOT LIVE until a shipped package proves, the shipping row open; SEARCH's twenty candidates on set v3 none under 1.5x on any cell (SCREEN). Every row still NOT RUN until read. | The 1.5x adversarial comparison laboratory (the founder's order, 9 October 2026, 11:4x UK): one evaluation for every control and candidate (the measurement recipe with the read-only twin for the memory share, the adversary interface returning the lowest credible specialist energy per design as a complete machine with WITNESS or BOUND labels, the score as the worst comparison over the required cohort same node and one node ahead, the rejection filters F1 to F6, the regression set REG-01 to REG-08 from the 8 and 9 October failures). Every row NOT RUN until the panel reads it; the first measured score (the frozen v6 control on the cohort against adversarial set v1) lands as a later batch under this cell. Amended 11:5x UK: X10, the full-sector fold candidate of the founder's third review, added as cand-x10 with the scoped same-node board claim (the die and node-ahead chips as coexistence rows); the AMD and Intel tiers NOT RUN on every candidate (no rented card; the house rigs unreachable by software) until a card is found."
"at": "2026-10-09T12:15:20.071Z",
"note": "The lab's interface and the candidate table at the fan-out: the frozen v6 control carried from the record (the house 5090 at its knee 4,011 nJ per hash, board power; the X0 amendment 5b rows: the DRAM board 2.35x same node WITNESS, the N2 die 7.8x the worst credible), the cohort rows for the 3090, the 5080 and the AMD and Intel tiers NOT RUN, adversarial set v1 pending; the three other controls (ProgPoW 0.9.4 reference, FishHash, the cooperative ARX candidate) NOT RUN with their clocks. No score is the lab's until the cohort and the adversary rows are in; R15-01, R15-08 and R15-09 stay NOT RUN until read. X10 (cand-x10) joins the table NOT RUN with its per-lane assignments and clocks; COHORT's ctl-v6 denominator set is in flight on eight rented pods. 12:1x UK: adversarial set v1 on the table (the frozen v6's same-node board 2.57x, 2.04 to 3.00, the fused tail CLAIMED until the routed lanes land; the die 11.4x as a coexistence row); the coexistence table (interface section 8b) added as the scoreboard's headline; SEARCH's first screen recorded as SCREEN rejections. Still NOT RUN: no cohort score until COHORT's eight rows are read back. 12:2x UK: set v2 (the routed fused-ARX lanes) makes the v6 board 2.60x a WITNESS; the ctl-v6 coexistence table (the board holds at every price; the N2 die pushes the GPU owner out above 14,300 dies at USD 0.10) is the headline; X10 SCREEN with the card modelled (the board 3.00x at 118 loads). Still NOT RUN: the cohort rows in their timed runs. 12:3x UK: the first cohort cells (ctl-v6 at stock on rented 5090, 5080 and 3090 pods: the worst cell the 3090 at 8,429 nJ = 5.46x on set v2's same-node board, PARTIAL, the dataset size under decision after CONTROLS measured the live 4 GiB object at 2.4x the 1 GiB research pack's rate); X10's first measured cell (cand-x10b on the 4090 at stock 3,653 nJ per lane-work = 5.8x on the board; the fold buys nothing); set v3 (routed 64-register and multiply-xor lanes); the fourth to sixth review rulings (8c); the 4 GiB rule (8e). Every row still NOT RUN until read. 12:4x UK: ctl-v6's first full score over the NVIDIA cohort at stock (the worst cell the RTX 4090 uncapped 8,751 nJ = 5.67x on set v2's same-node board; every cell at 4 GiB, the earlier 2.4x reading an instrument artefact, corrected once); the two-phase rows (ADVERSARY 545f3f8a0, 36d17b15c): phase B NOT LIVE until a shipped package proves, the shipping row open; SEARCH's twenty candidates on set v3 none under 1.5x on any cell (SCREEN). Every row still NOT RUN until read. 13:0x UK: the decider closed on both cards (the 4 GiB object costs 2.0 to 2.9 percent of rate against its 1 GiB export; the 2.4x reading withdrawn as a contention fault); the read-headroom row answered (both cards at their activation limit); the uncapped 5090 cell 5,980 nJ = 3.88x on the board; the shipping row's facts by file and line with the Devnet 4 correction (a 24 GB card proves the v1 shard now; the proving row NOT LIVE until the epoch record by 16:00); the 4 GiB cap defined as the mining dataset floor only; the founder's ledger order (8f) applied. Every row still NOT RUN until read. 13:1x UK: CONTROLS' done line (the four controls, Etchash and Autolykos2 staged bit-exact with SUMS); ADVERSARY's cross-chain phase A and B (no chain's emission recovers a board chip; the proving share the one term) and the E9 Pro calibration (1.28x pessimistic); the first founder bundle 985afee6. Every row still NOT RUN until read. | The 1.5x adversarial comparison laboratory (the founder's order, 9 October 2026, 11:4x UK): one evaluation for every control and candidate (the measurement recipe with the read-only twin for the memory share, the adversary interface returning the lowest credible specialist energy per design as a complete machine with WITNESS or BOUND labels, the score as the worst comparison over the required cohort same node and one node ahead, the rejection filters F1 to F6, the regression set REG-01 to REG-08 from the 8 and 9 October failures). Every row NOT RUN until the panel reads it; the first measured score (the frozen v6 control on the cohort against adversarial set v1) lands as a later batch under this cell. Amended 11:5x UK: X10, the full-sector fold candidate of the founder's third review, added as cand-x10 with the scoped same-node board claim (the die and node-ahead chips as coexistence rows); the AMD and Intel tiers NOT RUN on every candidate (no rented card; the house rigs unreachable by software) until a card is found."
},
"evidence_records": {
"lab:candidate": {
@ -20479,8 +20479,8 @@
},
"claim_impact": "none",
"reviewer": "",
"at": "2026-10-09T11:45:28.201Z",
"note": "The lab's interface and the candidate table at the fan-out: the frozen v6 control carried from the record (the house 5090 at its knee 4,011 nJ per hash, board power; the X0 amendment 5b rows: the DRAM board 2.35x same node WITNESS, the N2 die 7.8x the worst credible), the cohort rows for the 3090, the 5080 and the AMD and Intel tiers NOT RUN, adversarial set v1 pending; the three other controls (ProgPoW 0.9.4 reference, FishHash, the cooperative ARX candidate) NOT RUN with their clocks. No score is the lab's until the cohort and the adversary rows are in; R15-01, R15-08 and R15-09 stay NOT RUN until read. X10 (cand-x10) joins the table NOT RUN with its per-lane assignments and clocks; COHORT's ctl-v6 denominator set is in flight on eight rented pods. 12:1x UK: adversarial set v1 on the table (the frozen v6's same-node board 2.57x, 2.04 to 3.00, the fused tail CLAIMED until the routed lanes land; the die 11.4x as a coexistence row); the coexistence table (interface section 8b) added as the scoreboard's headline; SEARCH's first screen recorded as SCREEN rejections. Still NOT RUN: no cohort score until COHORT's eight rows are read back. 12:2x UK: set v2 (the routed fused-ARX lanes) makes the v6 board 2.60x a WITNESS; the ctl-v6 coexistence table (the board holds at every price; the N2 die pushes the GPU owner out above 14,300 dies at USD 0.10) is the headline; X10 SCREEN with the card modelled (the board 3.00x at 118 loads). Still NOT RUN: the cohort rows in their timed runs. 12:3x UK: the first cohort cells (ctl-v6 at stock on rented 5090, 5080 and 3090 pods: the worst cell the 3090 at 8,429 nJ = 5.46x on set v2's same-node board, PARTIAL, the dataset size under decision after CONTROLS measured the live 4 GiB object at 2.4x the 1 GiB research pack's rate); X10's first measured cell (cand-x10b on the 4090 at stock 3,653 nJ per lane-work = 5.8x on the board; the fold buys nothing); set v3 (routed 64-register and multiply-xor lanes); the fourth to sixth review rulings (8c); the 4 GiB rule (8e). Every row still NOT RUN until read. 12:4x UK: ctl-v6's first full score over the NVIDIA cohort at stock (the worst cell the RTX 4090 uncapped 8,751 nJ = 5.67x on set v2's same-node board; every cell at 4 GiB, the earlier 2.4x reading an instrument artefact, corrected once); the two-phase rows (ADVERSARY 545f3f8a0, 36d17b15c): phase B NOT LIVE until a shipped package proves, the shipping row open; SEARCH's twenty candidates on set v3 none under 1.5x on any cell (SCREEN). Every row still NOT RUN until read. | The 1.5x adversarial comparison laboratory (the founder's order, 9 October 2026, 11:4x UK): one evaluation for every control and candidate (the measurement recipe with the read-only twin for the memory share, the adversary interface returning the lowest credible specialist energy per design as a complete machine with WITNESS or BOUND labels, the score as the worst comparison over the required cohort same node and one node ahead, the rejection filters F1 to F6, the regression set REG-01 to REG-08 from the 8 and 9 October failures). Every row NOT RUN until the panel reads it; the first measured score (the frozen v6 control on the cohort against adversarial set v1) lands as a later batch under this cell. Amended 11:5x UK: X10, the full-sector fold candidate of the founder's third review, added as cand-x10 with the scoped same-node board claim (the die and node-ahead chips as coexistence rows); the AMD and Intel tiers NOT RUN on every candidate (no rented card; the house rigs unreachable by software) until a card is found."
"at": "2026-10-09T12:15:20.071Z",
"note": "The lab's interface and the candidate table at the fan-out: the frozen v6 control carried from the record (the house 5090 at its knee 4,011 nJ per hash, board power; the X0 amendment 5b rows: the DRAM board 2.35x same node WITNESS, the N2 die 7.8x the worst credible), the cohort rows for the 3090, the 5080 and the AMD and Intel tiers NOT RUN, adversarial set v1 pending; the three other controls (ProgPoW 0.9.4 reference, FishHash, the cooperative ARX candidate) NOT RUN with their clocks. No score is the lab's until the cohort and the adversary rows are in; R15-01, R15-08 and R15-09 stay NOT RUN until read. X10 (cand-x10) joins the table NOT RUN with its per-lane assignments and clocks; COHORT's ctl-v6 denominator set is in flight on eight rented pods. 12:1x UK: adversarial set v1 on the table (the frozen v6's same-node board 2.57x, 2.04 to 3.00, the fused tail CLAIMED until the routed lanes land; the die 11.4x as a coexistence row); the coexistence table (interface section 8b) added as the scoreboard's headline; SEARCH's first screen recorded as SCREEN rejections. Still NOT RUN: no cohort score until COHORT's eight rows are read back. 12:2x UK: set v2 (the routed fused-ARX lanes) makes the v6 board 2.60x a WITNESS; the ctl-v6 coexistence table (the board holds at every price; the N2 die pushes the GPU owner out above 14,300 dies at USD 0.10) is the headline; X10 SCREEN with the card modelled (the board 3.00x at 118 loads). Still NOT RUN: the cohort rows in their timed runs. 12:3x UK: the first cohort cells (ctl-v6 at stock on rented 5090, 5080 and 3090 pods: the worst cell the 3090 at 8,429 nJ = 5.46x on set v2's same-node board, PARTIAL, the dataset size under decision after CONTROLS measured the live 4 GiB object at 2.4x the 1 GiB research pack's rate); X10's first measured cell (cand-x10b on the 4090 at stock 3,653 nJ per lane-work = 5.8x on the board; the fold buys nothing); set v3 (routed 64-register and multiply-xor lanes); the fourth to sixth review rulings (8c); the 4 GiB rule (8e). Every row still NOT RUN until read. 12:4x UK: ctl-v6's first full score over the NVIDIA cohort at stock (the worst cell the RTX 4090 uncapped 8,751 nJ = 5.67x on set v2's same-node board; every cell at 4 GiB, the earlier 2.4x reading an instrument artefact, corrected once); the two-phase rows (ADVERSARY 545f3f8a0, 36d17b15c): phase B NOT LIVE until a shipped package proves, the shipping row open; SEARCH's twenty candidates on set v3 none under 1.5x on any cell (SCREEN). Every row still NOT RUN until read. 13:0x UK: the decider closed on both cards (the 4 GiB object costs 2.0 to 2.9 percent of rate against its 1 GiB export; the 2.4x reading withdrawn as a contention fault); the read-headroom row answered (both cards at their activation limit); the uncapped 5090 cell 5,980 nJ = 3.88x on the board; the shipping row's facts by file and line with the Devnet 4 correction (a 24 GB card proves the v1 shard now; the proving row NOT LIVE until the epoch record by 16:00); the 4 GiB cap defined as the mining dataset floor only; the founder's ledger order (8f) applied. Every row still NOT RUN until read. 13:1x UK: CONTROLS' done line (the four controls, Etchash and Autolykos2 staged bit-exact with SUMS); ADVERSARY's cross-chain phase A and B (no chain's emission recovers a board chip; the proving share the one term) and the E9 Pro calibration (1.28x pessimistic); the first founder bundle 985afee6. Every row still NOT RUN until read. | The 1.5x adversarial comparison laboratory (the founder's order, 9 October 2026, 11:4x UK): one evaluation for every control and candidate (the measurement recipe with the read-only twin for the memory share, the adversary interface returning the lowest credible specialist energy per design as a complete machine with WITNESS or BOUND labels, the score as the worst comparison over the required cohort same node and one node ahead, the rejection filters F1 to F6, the regression set REG-01 to REG-08 from the 8 and 9 October failures). Every row NOT RUN until the panel reads it; the first measured score (the frozen v6 control on the cohort against adversarial set v1) lands as a later batch under this cell. Amended 11:5x UK: X10, the full-sector fold candidate of the founder's third review, added as cand-x10 with the scoped same-node board claim (the die and node-ahead chips as coexistence rows); the AMD and Intel tiers NOT RUN on every candidate (no rented card; the house rigs unreachable by software) until a card is found."
}
},
"in_progress_since": "2026-10-09T10:48:54.646Z",
@ -21144,7 +21144,7 @@
"plan_status": "NOT RUN",
"run_id": "lab-20261009-01",
"evidence_path": "docs/analysis/class-v6/1p5x/lab/README.md; docs/analysis/class-v6/1p5x/lab/table.md",
"updated": "2026-10-09T11:45:28.201Z",
"updated": "2026-10-09T12:15:20.071Z",
"evidence_record": {
"requirement_id": "R15-08",
"decision": "NOT RUN",
@ -21165,8 +21165,8 @@
},
"claim_impact": "none",
"reviewer": "",
"at": "2026-10-09T11:45:28.201Z",
"note": "The lab's interface and the candidate table at the fan-out: the frozen v6 control carried from the record (the house 5090 at its knee 4,011 nJ per hash, board power; the X0 amendment 5b rows: the DRAM board 2.35x same node WITNESS, the N2 die 7.8x the worst credible), the cohort rows for the 3090, the 5080 and the AMD and Intel tiers NOT RUN, adversarial set v1 pending; the three other controls (ProgPoW 0.9.4 reference, FishHash, the cooperative ARX candidate) NOT RUN with their clocks. No score is the lab's until the cohort and the adversary rows are in; R15-01, R15-08 and R15-09 stay NOT RUN until read. X10 (cand-x10) joins the table NOT RUN with its per-lane assignments and clocks; COHORT's ctl-v6 denominator set is in flight on eight rented pods. 12:1x UK: adversarial set v1 on the table (the frozen v6's same-node board 2.57x, 2.04 to 3.00, the fused tail CLAIMED until the routed lanes land; the die 11.4x as a coexistence row); the coexistence table (interface section 8b) added as the scoreboard's headline; SEARCH's first screen recorded as SCREEN rejections. Still NOT RUN: no cohort score until COHORT's eight rows are read back. 12:2x UK: set v2 (the routed fused-ARX lanes) makes the v6 board 2.60x a WITNESS; the ctl-v6 coexistence table (the board holds at every price; the N2 die pushes the GPU owner out above 14,300 dies at USD 0.10) is the headline; X10 SCREEN with the card modelled (the board 3.00x at 118 loads). Still NOT RUN: the cohort rows in their timed runs. 12:3x UK: the first cohort cells (ctl-v6 at stock on rented 5090, 5080 and 3090 pods: the worst cell the 3090 at 8,429 nJ = 5.46x on set v2's same-node board, PARTIAL, the dataset size under decision after CONTROLS measured the live 4 GiB object at 2.4x the 1 GiB research pack's rate); X10's first measured cell (cand-x10b on the 4090 at stock 3,653 nJ per lane-work = 5.8x on the board; the fold buys nothing); set v3 (routed 64-register and multiply-xor lanes); the fourth to sixth review rulings (8c); the 4 GiB rule (8e). Every row still NOT RUN until read. 12:4x UK: ctl-v6's first full score over the NVIDIA cohort at stock (the worst cell the RTX 4090 uncapped 8,751 nJ = 5.67x on set v2's same-node board; every cell at 4 GiB, the earlier 2.4x reading an instrument artefact, corrected once); the two-phase rows (ADVERSARY 545f3f8a0, 36d17b15c): phase B NOT LIVE until a shipped package proves, the shipping row open; SEARCH's twenty candidates on set v3 none under 1.5x on any cell (SCREEN). Every row still NOT RUN until read. | The 1.5x adversarial comparison laboratory (the founder's order, 9 October 2026, 11:4x UK): one evaluation for every control and candidate (the measurement recipe with the read-only twin for the memory share, the adversary interface returning the lowest credible specialist energy per design as a complete machine with WITNESS or BOUND labels, the score as the worst comparison over the required cohort same node and one node ahead, the rejection filters F1 to F6, the regression set REG-01 to REG-08 from the 8 and 9 October failures). Every row NOT RUN until the panel reads it; the first measured score (the frozen v6 control on the cohort against adversarial set v1) lands as a later batch under this cell. Amended 11:5x UK: X10, the full-sector fold candidate of the founder's third review, added as cand-x10 with the scoped same-node board claim (the die and node-ahead chips as coexistence rows); the AMD and Intel tiers NOT RUN on every candidate (no rented card; the house rigs unreachable by software) until a card is found."
"at": "2026-10-09T12:15:20.071Z",
"note": "The lab's interface and the candidate table at the fan-out: the frozen v6 control carried from the record (the house 5090 at its knee 4,011 nJ per hash, board power; the X0 amendment 5b rows: the DRAM board 2.35x same node WITNESS, the N2 die 7.8x the worst credible), the cohort rows for the 3090, the 5080 and the AMD and Intel tiers NOT RUN, adversarial set v1 pending; the three other controls (ProgPoW 0.9.4 reference, FishHash, the cooperative ARX candidate) NOT RUN with their clocks. No score is the lab's until the cohort and the adversary rows are in; R15-01, R15-08 and R15-09 stay NOT RUN until read. X10 (cand-x10) joins the table NOT RUN with its per-lane assignments and clocks; COHORT's ctl-v6 denominator set is in flight on eight rented pods. 12:1x UK: adversarial set v1 on the table (the frozen v6's same-node board 2.57x, 2.04 to 3.00, the fused tail CLAIMED until the routed lanes land; the die 11.4x as a coexistence row); the coexistence table (interface section 8b) added as the scoreboard's headline; SEARCH's first screen recorded as SCREEN rejections. Still NOT RUN: no cohort score until COHORT's eight rows are read back. 12:2x UK: set v2 (the routed fused-ARX lanes) makes the v6 board 2.60x a WITNESS; the ctl-v6 coexistence table (the board holds at every price; the N2 die pushes the GPU owner out above 14,300 dies at USD 0.10) is the headline; X10 SCREEN with the card modelled (the board 3.00x at 118 loads). Still NOT RUN: the cohort rows in their timed runs. 12:3x UK: the first cohort cells (ctl-v6 at stock on rented 5090, 5080 and 3090 pods: the worst cell the 3090 at 8,429 nJ = 5.46x on set v2's same-node board, PARTIAL, the dataset size under decision after CONTROLS measured the live 4 GiB object at 2.4x the 1 GiB research pack's rate); X10's first measured cell (cand-x10b on the 4090 at stock 3,653 nJ per lane-work = 5.8x on the board; the fold buys nothing); set v3 (routed 64-register and multiply-xor lanes); the fourth to sixth review rulings (8c); the 4 GiB rule (8e). Every row still NOT RUN until read. 12:4x UK: ctl-v6's first full score over the NVIDIA cohort at stock (the worst cell the RTX 4090 uncapped 8,751 nJ = 5.67x on set v2's same-node board; every cell at 4 GiB, the earlier 2.4x reading an instrument artefact, corrected once); the two-phase rows (ADVERSARY 545f3f8a0, 36d17b15c): phase B NOT LIVE until a shipped package proves, the shipping row open; SEARCH's twenty candidates on set v3 none under 1.5x on any cell (SCREEN). Every row still NOT RUN until read. 13:0x UK: the decider closed on both cards (the 4 GiB object costs 2.0 to 2.9 percent of rate against its 1 GiB export; the 2.4x reading withdrawn as a contention fault); the read-headroom row answered (both cards at their activation limit); the uncapped 5090 cell 5,980 nJ = 3.88x on the board; the shipping row's facts by file and line with the Devnet 4 correction (a 24 GB card proves the v1 shard now; the proving row NOT LIVE until the epoch record by 16:00); the 4 GiB cap defined as the mining dataset floor only; the founder's ledger order (8f) applied. Every row still NOT RUN until read. 13:1x UK: CONTROLS' done line (the four controls, Etchash and Autolykos2 staged bit-exact with SUMS); ADVERSARY's cross-chain phase A and B (no chain's emission recovers a board chip; the proving share the one term) and the E9 Pro calibration (1.28x pessimistic); the first founder bundle 985afee6. Every row still NOT RUN until read. | The 1.5x adversarial comparison laboratory (the founder's order, 9 October 2026, 11:4x UK): one evaluation for every control and candidate (the measurement recipe with the read-only twin for the memory share, the adversary interface returning the lowest credible specialist energy per design as a complete machine with WITNESS or BOUND labels, the score as the worst comparison over the required cohort same node and one node ahead, the rejection filters F1 to F6, the regression set REG-01 to REG-08 from the 8 and 9 October failures). Every row NOT RUN until the panel reads it; the first measured score (the frozen v6 control on the cohort against adversarial set v1) lands as a later batch under this cell. Amended 11:5x UK: X10, the full-sector fold candidate of the founder's third review, added as cand-x10 with the scoped same-node board claim (the die and node-ahead chips as coexistence rows); the AMD and Intel tiers NOT RUN on every candidate (no rented card; the house rigs unreachable by software) until a card is found."
},
"evidence_records": {
"lab:candidate": {
@ -21189,8 +21189,8 @@
},
"claim_impact": "none",
"reviewer": "",
"at": "2026-10-09T11:45:28.201Z",
"note": "The lab's interface and the candidate table at the fan-out: the frozen v6 control carried from the record (the house 5090 at its knee 4,011 nJ per hash, board power; the X0 amendment 5b rows: the DRAM board 2.35x same node WITNESS, the N2 die 7.8x the worst credible), the cohort rows for the 3090, the 5080 and the AMD and Intel tiers NOT RUN, adversarial set v1 pending; the three other controls (ProgPoW 0.9.4 reference, FishHash, the cooperative ARX candidate) NOT RUN with their clocks. No score is the lab's until the cohort and the adversary rows are in; R15-01, R15-08 and R15-09 stay NOT RUN until read. X10 (cand-x10) joins the table NOT RUN with its per-lane assignments and clocks; COHORT's ctl-v6 denominator set is in flight on eight rented pods. 12:1x UK: adversarial set v1 on the table (the frozen v6's same-node board 2.57x, 2.04 to 3.00, the fused tail CLAIMED until the routed lanes land; the die 11.4x as a coexistence row); the coexistence table (interface section 8b) added as the scoreboard's headline; SEARCH's first screen recorded as SCREEN rejections. Still NOT RUN: no cohort score until COHORT's eight rows are read back. 12:2x UK: set v2 (the routed fused-ARX lanes) makes the v6 board 2.60x a WITNESS; the ctl-v6 coexistence table (the board holds at every price; the N2 die pushes the GPU owner out above 14,300 dies at USD 0.10) is the headline; X10 SCREEN with the card modelled (the board 3.00x at 118 loads). Still NOT RUN: the cohort rows in their timed runs. 12:3x UK: the first cohort cells (ctl-v6 at stock on rented 5090, 5080 and 3090 pods: the worst cell the 3090 at 8,429 nJ = 5.46x on set v2's same-node board, PARTIAL, the dataset size under decision after CONTROLS measured the live 4 GiB object at 2.4x the 1 GiB research pack's rate); X10's first measured cell (cand-x10b on the 4090 at stock 3,653 nJ per lane-work = 5.8x on the board; the fold buys nothing); set v3 (routed 64-register and multiply-xor lanes); the fourth to sixth review rulings (8c); the 4 GiB rule (8e). Every row still NOT RUN until read. 12:4x UK: ctl-v6's first full score over the NVIDIA cohort at stock (the worst cell the RTX 4090 uncapped 8,751 nJ = 5.67x on set v2's same-node board; every cell at 4 GiB, the earlier 2.4x reading an instrument artefact, corrected once); the two-phase rows (ADVERSARY 545f3f8a0, 36d17b15c): phase B NOT LIVE until a shipped package proves, the shipping row open; SEARCH's twenty candidates on set v3 none under 1.5x on any cell (SCREEN). Every row still NOT RUN until read. | The 1.5x adversarial comparison laboratory (the founder's order, 9 October 2026, 11:4x UK): one evaluation for every control and candidate (the measurement recipe with the read-only twin for the memory share, the adversary interface returning the lowest credible specialist energy per design as a complete machine with WITNESS or BOUND labels, the score as the worst comparison over the required cohort same node and one node ahead, the rejection filters F1 to F6, the regression set REG-01 to REG-08 from the 8 and 9 October failures). Every row NOT RUN until the panel reads it; the first measured score (the frozen v6 control on the cohort against adversarial set v1) lands as a later batch under this cell. Amended 11:5x UK: X10, the full-sector fold candidate of the founder's third review, added as cand-x10 with the scoped same-node board claim (the die and node-ahead chips as coexistence rows); the AMD and Intel tiers NOT RUN on every candidate (no rented card; the house rigs unreachable by software) until a card is found."
"at": "2026-10-09T12:15:20.071Z",
"note": "The lab's interface and the candidate table at the fan-out: the frozen v6 control carried from the record (the house 5090 at its knee 4,011 nJ per hash, board power; the X0 amendment 5b rows: the DRAM board 2.35x same node WITNESS, the N2 die 7.8x the worst credible), the cohort rows for the 3090, the 5080 and the AMD and Intel tiers NOT RUN, adversarial set v1 pending; the three other controls (ProgPoW 0.9.4 reference, FishHash, the cooperative ARX candidate) NOT RUN with their clocks. No score is the lab's until the cohort and the adversary rows are in; R15-01, R15-08 and R15-09 stay NOT RUN until read. X10 (cand-x10) joins the table NOT RUN with its per-lane assignments and clocks; COHORT's ctl-v6 denominator set is in flight on eight rented pods. 12:1x UK: adversarial set v1 on the table (the frozen v6's same-node board 2.57x, 2.04 to 3.00, the fused tail CLAIMED until the routed lanes land; the die 11.4x as a coexistence row); the coexistence table (interface section 8b) added as the scoreboard's headline; SEARCH's first screen recorded as SCREEN rejections. Still NOT RUN: no cohort score until COHORT's eight rows are read back. 12:2x UK: set v2 (the routed fused-ARX lanes) makes the v6 board 2.60x a WITNESS; the ctl-v6 coexistence table (the board holds at every price; the N2 die pushes the GPU owner out above 14,300 dies at USD 0.10) is the headline; X10 SCREEN with the card modelled (the board 3.00x at 118 loads). Still NOT RUN: the cohort rows in their timed runs. 12:3x UK: the first cohort cells (ctl-v6 at stock on rented 5090, 5080 and 3090 pods: the worst cell the 3090 at 8,429 nJ = 5.46x on set v2's same-node board, PARTIAL, the dataset size under decision after CONTROLS measured the live 4 GiB object at 2.4x the 1 GiB research pack's rate); X10's first measured cell (cand-x10b on the 4090 at stock 3,653 nJ per lane-work = 5.8x on the board; the fold buys nothing); set v3 (routed 64-register and multiply-xor lanes); the fourth to sixth review rulings (8c); the 4 GiB rule (8e). Every row still NOT RUN until read. 12:4x UK: ctl-v6's first full score over the NVIDIA cohort at stock (the worst cell the RTX 4090 uncapped 8,751 nJ = 5.67x on set v2's same-node board; every cell at 4 GiB, the earlier 2.4x reading an instrument artefact, corrected once); the two-phase rows (ADVERSARY 545f3f8a0, 36d17b15c): phase B NOT LIVE until a shipped package proves, the shipping row open; SEARCH's twenty candidates on set v3 none under 1.5x on any cell (SCREEN). Every row still NOT RUN until read. 13:0x UK: the decider closed on both cards (the 4 GiB object costs 2.0 to 2.9 percent of rate against its 1 GiB export; the 2.4x reading withdrawn as a contention fault); the read-headroom row answered (both cards at their activation limit); the uncapped 5090 cell 5,980 nJ = 3.88x on the board; the shipping row's facts by file and line with the Devnet 4 correction (a 24 GB card proves the v1 shard now; the proving row NOT LIVE until the epoch record by 16:00); the 4 GiB cap defined as the mining dataset floor only; the founder's ledger order (8f) applied. Every row still NOT RUN until read. 13:1x UK: CONTROLS' done line (the four controls, Etchash and Autolykos2 staged bit-exact with SUMS); ADVERSARY's cross-chain phase A and B (no chain's emission recovers a board chip; the proving share the one term) and the E9 Pro calibration (1.28x pessimistic); the first founder bundle 985afee6. Every row still NOT RUN until read. | The 1.5x adversarial comparison laboratory (the founder's order, 9 October 2026, 11:4x UK): one evaluation for every control and candidate (the measurement recipe with the read-only twin for the memory share, the adversary interface returning the lowest credible specialist energy per design as a complete machine with WITNESS or BOUND labels, the score as the worst comparison over the required cohort same node and one node ahead, the rejection filters F1 to F6, the regression set REG-01 to REG-08 from the 8 and 9 October failures). Every row NOT RUN until the panel reads it; the first measured score (the frozen v6 control on the cohort against adversarial set v1) lands as a later batch under this cell. Amended 11:5x UK: X10, the full-sector fold candidate of the founder's third review, added as cand-x10 with the scoped same-node board claim (the die and node-ahead chips as coexistence rows); the AMD and Intel tiers NOT RUN on every candidate (no rented card; the house rigs unreachable by software) until a card is found."
}
},
"in_progress_since": "2026-10-09T10:48:54.646Z",
@ -21234,7 +21234,7 @@
"plan_status": "NOT RUN",
"run_id": "lab-20261009-01",
"evidence_path": "docs/analysis/class-v6/1p5x/lab/README.md; docs/analysis/class-v6/1p5x/lab/table.md",
"updated": "2026-10-09T11:45:28.201Z",
"updated": "2026-10-09T12:15:20.071Z",
"evidence_record": {
"requirement_id": "R15-09",
"decision": "NOT RUN",
@ -21255,8 +21255,8 @@
},
"claim_impact": "none",
"reviewer": "",
"at": "2026-10-09T11:45:28.201Z",
"note": "The lab's interface and the candidate table at the fan-out: the frozen v6 control carried from the record (the house 5090 at its knee 4,011 nJ per hash, board power; the X0 amendment 5b rows: the DRAM board 2.35x same node WITNESS, the N2 die 7.8x the worst credible), the cohort rows for the 3090, the 5080 and the AMD and Intel tiers NOT RUN, adversarial set v1 pending; the three other controls (ProgPoW 0.9.4 reference, FishHash, the cooperative ARX candidate) NOT RUN with their clocks. No score is the lab's until the cohort and the adversary rows are in; R15-01, R15-08 and R15-09 stay NOT RUN until read. X10 (cand-x10) joins the table NOT RUN with its per-lane assignments and clocks; COHORT's ctl-v6 denominator set is in flight on eight rented pods. 12:1x UK: adversarial set v1 on the table (the frozen v6's same-node board 2.57x, 2.04 to 3.00, the fused tail CLAIMED until the routed lanes land; the die 11.4x as a coexistence row); the coexistence table (interface section 8b) added as the scoreboard's headline; SEARCH's first screen recorded as SCREEN rejections. Still NOT RUN: no cohort score until COHORT's eight rows are read back. 12:2x UK: set v2 (the routed fused-ARX lanes) makes the v6 board 2.60x a WITNESS; the ctl-v6 coexistence table (the board holds at every price; the N2 die pushes the GPU owner out above 14,300 dies at USD 0.10) is the headline; X10 SCREEN with the card modelled (the board 3.00x at 118 loads). Still NOT RUN: the cohort rows in their timed runs. 12:3x UK: the first cohort cells (ctl-v6 at stock on rented 5090, 5080 and 3090 pods: the worst cell the 3090 at 8,429 nJ = 5.46x on set v2's same-node board, PARTIAL, the dataset size under decision after CONTROLS measured the live 4 GiB object at 2.4x the 1 GiB research pack's rate); X10's first measured cell (cand-x10b on the 4090 at stock 3,653 nJ per lane-work = 5.8x on the board; the fold buys nothing); set v3 (routed 64-register and multiply-xor lanes); the fourth to sixth review rulings (8c); the 4 GiB rule (8e). Every row still NOT RUN until read. 12:4x UK: ctl-v6's first full score over the NVIDIA cohort at stock (the worst cell the RTX 4090 uncapped 8,751 nJ = 5.67x on set v2's same-node board; every cell at 4 GiB, the earlier 2.4x reading an instrument artefact, corrected once); the two-phase rows (ADVERSARY 545f3f8a0, 36d17b15c): phase B NOT LIVE until a shipped package proves, the shipping row open; SEARCH's twenty candidates on set v3 none under 1.5x on any cell (SCREEN). Every row still NOT RUN until read. | The 1.5x adversarial comparison laboratory (the founder's order, 9 October 2026, 11:4x UK): one evaluation for every control and candidate (the measurement recipe with the read-only twin for the memory share, the adversary interface returning the lowest credible specialist energy per design as a complete machine with WITNESS or BOUND labels, the score as the worst comparison over the required cohort same node and one node ahead, the rejection filters F1 to F6, the regression set REG-01 to REG-08 from the 8 and 9 October failures). Every row NOT RUN until the panel reads it; the first measured score (the frozen v6 control on the cohort against adversarial set v1) lands as a later batch under this cell. Amended 11:5x UK: X10, the full-sector fold candidate of the founder's third review, added as cand-x10 with the scoped same-node board claim (the die and node-ahead chips as coexistence rows); the AMD and Intel tiers NOT RUN on every candidate (no rented card; the house rigs unreachable by software) until a card is found."
"at": "2026-10-09T12:15:20.071Z",
"note": "The lab's interface and the candidate table at the fan-out: the frozen v6 control carried from the record (the house 5090 at its knee 4,011 nJ per hash, board power; the X0 amendment 5b rows: the DRAM board 2.35x same node WITNESS, the N2 die 7.8x the worst credible), the cohort rows for the 3090, the 5080 and the AMD and Intel tiers NOT RUN, adversarial set v1 pending; the three other controls (ProgPoW 0.9.4 reference, FishHash, the cooperative ARX candidate) NOT RUN with their clocks. No score is the lab's until the cohort and the adversary rows are in; R15-01, R15-08 and R15-09 stay NOT RUN until read. X10 (cand-x10) joins the table NOT RUN with its per-lane assignments and clocks; COHORT's ctl-v6 denominator set is in flight on eight rented pods. 12:1x UK: adversarial set v1 on the table (the frozen v6's same-node board 2.57x, 2.04 to 3.00, the fused tail CLAIMED until the routed lanes land; the die 11.4x as a coexistence row); the coexistence table (interface section 8b) added as the scoreboard's headline; SEARCH's first screen recorded as SCREEN rejections. Still NOT RUN: no cohort score until COHORT's eight rows are read back. 12:2x UK: set v2 (the routed fused-ARX lanes) makes the v6 board 2.60x a WITNESS; the ctl-v6 coexistence table (the board holds at every price; the N2 die pushes the GPU owner out above 14,300 dies at USD 0.10) is the headline; X10 SCREEN with the card modelled (the board 3.00x at 118 loads). Still NOT RUN: the cohort rows in their timed runs. 12:3x UK: the first cohort cells (ctl-v6 at stock on rented 5090, 5080 and 3090 pods: the worst cell the 3090 at 8,429 nJ = 5.46x on set v2's same-node board, PARTIAL, the dataset size under decision after CONTROLS measured the live 4 GiB object at 2.4x the 1 GiB research pack's rate); X10's first measured cell (cand-x10b on the 4090 at stock 3,653 nJ per lane-work = 5.8x on the board; the fold buys nothing); set v3 (routed 64-register and multiply-xor lanes); the fourth to sixth review rulings (8c); the 4 GiB rule (8e). Every row still NOT RUN until read. 12:4x UK: ctl-v6's first full score over the NVIDIA cohort at stock (the worst cell the RTX 4090 uncapped 8,751 nJ = 5.67x on set v2's same-node board; every cell at 4 GiB, the earlier 2.4x reading an instrument artefact, corrected once); the two-phase rows (ADVERSARY 545f3f8a0, 36d17b15c): phase B NOT LIVE until a shipped package proves, the shipping row open; SEARCH's twenty candidates on set v3 none under 1.5x on any cell (SCREEN). Every row still NOT RUN until read. 13:0x UK: the decider closed on both cards (the 4 GiB object costs 2.0 to 2.9 percent of rate against its 1 GiB export; the 2.4x reading withdrawn as a contention fault); the read-headroom row answered (both cards at their activation limit); the uncapped 5090 cell 5,980 nJ = 3.88x on the board; the shipping row's facts by file and line with the Devnet 4 correction (a 24 GB card proves the v1 shard now; the proving row NOT LIVE until the epoch record by 16:00); the 4 GiB cap defined as the mining dataset floor only; the founder's ledger order (8f) applied. Every row still NOT RUN until read. 13:1x UK: CONTROLS' done line (the four controls, Etchash and Autolykos2 staged bit-exact with SUMS); ADVERSARY's cross-chain phase A and B (no chain's emission recovers a board chip; the proving share the one term) and the E9 Pro calibration (1.28x pessimistic); the first founder bundle 985afee6. Every row still NOT RUN until read. | The 1.5x adversarial comparison laboratory (the founder's order, 9 October 2026, 11:4x UK): one evaluation for every control and candidate (the measurement recipe with the read-only twin for the memory share, the adversary interface returning the lowest credible specialist energy per design as a complete machine with WITNESS or BOUND labels, the score as the worst comparison over the required cohort same node and one node ahead, the rejection filters F1 to F6, the regression set REG-01 to REG-08 from the 8 and 9 October failures). Every row NOT RUN until the panel reads it; the first measured score (the frozen v6 control on the cohort against adversarial set v1) lands as a later batch under this cell. Amended 11:5x UK: X10, the full-sector fold candidate of the founder's third review, added as cand-x10 with the scoped same-node board claim (the die and node-ahead chips as coexistence rows); the AMD and Intel tiers NOT RUN on every candidate (no rented card; the house rigs unreachable by software) until a card is found."
},
"evidence_records": {
"lab:candidate": {
@ -21279,8 +21279,8 @@
},
"claim_impact": "none",
"reviewer": "",
"at": "2026-10-09T11:45:28.201Z",
"note": "The lab's interface and the candidate table at the fan-out: the frozen v6 control carried from the record (the house 5090 at its knee 4,011 nJ per hash, board power; the X0 amendment 5b rows: the DRAM board 2.35x same node WITNESS, the N2 die 7.8x the worst credible), the cohort rows for the 3090, the 5080 and the AMD and Intel tiers NOT RUN, adversarial set v1 pending; the three other controls (ProgPoW 0.9.4 reference, FishHash, the cooperative ARX candidate) NOT RUN with their clocks. No score is the lab's until the cohort and the adversary rows are in; R15-01, R15-08 and R15-09 stay NOT RUN until read. X10 (cand-x10) joins the table NOT RUN with its per-lane assignments and clocks; COHORT's ctl-v6 denominator set is in flight on eight rented pods. 12:1x UK: adversarial set v1 on the table (the frozen v6's same-node board 2.57x, 2.04 to 3.00, the fused tail CLAIMED until the routed lanes land; the die 11.4x as a coexistence row); the coexistence table (interface section 8b) added as the scoreboard's headline; SEARCH's first screen recorded as SCREEN rejections. Still NOT RUN: no cohort score until COHORT's eight rows are read back. 12:2x UK: set v2 (the routed fused-ARX lanes) makes the v6 board 2.60x a WITNESS; the ctl-v6 coexistence table (the board holds at every price; the N2 die pushes the GPU owner out above 14,300 dies at USD 0.10) is the headline; X10 SCREEN with the card modelled (the board 3.00x at 118 loads). Still NOT RUN: the cohort rows in their timed runs. 12:3x UK: the first cohort cells (ctl-v6 at stock on rented 5090, 5080 and 3090 pods: the worst cell the 3090 at 8,429 nJ = 5.46x on set v2's same-node board, PARTIAL, the dataset size under decision after CONTROLS measured the live 4 GiB object at 2.4x the 1 GiB research pack's rate); X10's first measured cell (cand-x10b on the 4090 at stock 3,653 nJ per lane-work = 5.8x on the board; the fold buys nothing); set v3 (routed 64-register and multiply-xor lanes); the fourth to sixth review rulings (8c); the 4 GiB rule (8e). Every row still NOT RUN until read. 12:4x UK: ctl-v6's first full score over the NVIDIA cohort at stock (the worst cell the RTX 4090 uncapped 8,751 nJ = 5.67x on set v2's same-node board; every cell at 4 GiB, the earlier 2.4x reading an instrument artefact, corrected once); the two-phase rows (ADVERSARY 545f3f8a0, 36d17b15c): phase B NOT LIVE until a shipped package proves, the shipping row open; SEARCH's twenty candidates on set v3 none under 1.5x on any cell (SCREEN). Every row still NOT RUN until read. | The 1.5x adversarial comparison laboratory (the founder's order, 9 October 2026, 11:4x UK): one evaluation for every control and candidate (the measurement recipe with the read-only twin for the memory share, the adversary interface returning the lowest credible specialist energy per design as a complete machine with WITNESS or BOUND labels, the score as the worst comparison over the required cohort same node and one node ahead, the rejection filters F1 to F6, the regression set REG-01 to REG-08 from the 8 and 9 October failures). Every row NOT RUN until the panel reads it; the first measured score (the frozen v6 control on the cohort against adversarial set v1) lands as a later batch under this cell. Amended 11:5x UK: X10, the full-sector fold candidate of the founder's third review, added as cand-x10 with the scoped same-node board claim (the die and node-ahead chips as coexistence rows); the AMD and Intel tiers NOT RUN on every candidate (no rented card; the house rigs unreachable by software) until a card is found."
"at": "2026-10-09T12:15:20.071Z",
"note": "The lab's interface and the candidate table at the fan-out: the frozen v6 control carried from the record (the house 5090 at its knee 4,011 nJ per hash, board power; the X0 amendment 5b rows: the DRAM board 2.35x same node WITNESS, the N2 die 7.8x the worst credible), the cohort rows for the 3090, the 5080 and the AMD and Intel tiers NOT RUN, adversarial set v1 pending; the three other controls (ProgPoW 0.9.4 reference, FishHash, the cooperative ARX candidate) NOT RUN with their clocks. No score is the lab's until the cohort and the adversary rows are in; R15-01, R15-08 and R15-09 stay NOT RUN until read. X10 (cand-x10) joins the table NOT RUN with its per-lane assignments and clocks; COHORT's ctl-v6 denominator set is in flight on eight rented pods. 12:1x UK: adversarial set v1 on the table (the frozen v6's same-node board 2.57x, 2.04 to 3.00, the fused tail CLAIMED until the routed lanes land; the die 11.4x as a coexistence row); the coexistence table (interface section 8b) added as the scoreboard's headline; SEARCH's first screen recorded as SCREEN rejections. Still NOT RUN: no cohort score until COHORT's eight rows are read back. 12:2x UK: set v2 (the routed fused-ARX lanes) makes the v6 board 2.60x a WITNESS; the ctl-v6 coexistence table (the board holds at every price; the N2 die pushes the GPU owner out above 14,300 dies at USD 0.10) is the headline; X10 SCREEN with the card modelled (the board 3.00x at 118 loads). Still NOT RUN: the cohort rows in their timed runs. 12:3x UK: the first cohort cells (ctl-v6 at stock on rented 5090, 5080 and 3090 pods: the worst cell the 3090 at 8,429 nJ = 5.46x on set v2's same-node board, PARTIAL, the dataset size under decision after CONTROLS measured the live 4 GiB object at 2.4x the 1 GiB research pack's rate); X10's first measured cell (cand-x10b on the 4090 at stock 3,653 nJ per lane-work = 5.8x on the board; the fold buys nothing); set v3 (routed 64-register and multiply-xor lanes); the fourth to sixth review rulings (8c); the 4 GiB rule (8e). Every row still NOT RUN until read. 12:4x UK: ctl-v6's first full score over the NVIDIA cohort at stock (the worst cell the RTX 4090 uncapped 8,751 nJ = 5.67x on set v2's same-node board; every cell at 4 GiB, the earlier 2.4x reading an instrument artefact, corrected once); the two-phase rows (ADVERSARY 545f3f8a0, 36d17b15c): phase B NOT LIVE until a shipped package proves, the shipping row open; SEARCH's twenty candidates on set v3 none under 1.5x on any cell (SCREEN). Every row still NOT RUN until read. 13:0x UK: the decider closed on both cards (the 4 GiB object costs 2.0 to 2.9 percent of rate against its 1 GiB export; the 2.4x reading withdrawn as a contention fault); the read-headroom row answered (both cards at their activation limit); the uncapped 5090 cell 5,980 nJ = 3.88x on the board; the shipping row's facts by file and line with the Devnet 4 correction (a 24 GB card proves the v1 shard now; the proving row NOT LIVE until the epoch record by 16:00); the 4 GiB cap defined as the mining dataset floor only; the founder's ledger order (8f) applied. Every row still NOT RUN until read. 13:1x UK: CONTROLS' done line (the four controls, Etchash and Autolykos2 staged bit-exact with SUMS); ADVERSARY's cross-chain phase A and B (no chain's emission recovers a board chip; the proving share the one term) and the E9 Pro calibration (1.28x pessimistic); the first founder bundle 985afee6. Every row still NOT RUN until read. | The 1.5x adversarial comparison laboratory (the founder's order, 9 October 2026, 11:4x UK): one evaluation for every control and candidate (the measurement recipe with the read-only twin for the memory share, the adversary interface returning the lowest credible specialist energy per design as a complete machine with WITNESS or BOUND labels, the score as the worst comparison over the required cohort same node and one node ahead, the rejection filters F1 to F6, the regression set REG-01 to REG-08 from the 8 and 9 October failures). Every row NOT RUN until the panel reads it; the first measured score (the frozen v6 control on the cohort against adversarial set v1) lands as a later batch under this cell. Amended 11:5x UK: X10, the full-sector fold candidate of the founder's third review, added as cand-x10 with the scoped same-node board claim (the die and node-ahead chips as coexistence rows); the AMD and Intel tiers NOT RUN on every candidate (no rented card; the house rigs unreachable by software) until a card is found."
}
},
"in_progress_since": "2026-10-09T10:48:54.646Z",

View file

@ -42,10 +42,18 @@ function LabInstall-Refusal($task, [string] $machineName, [string] $engineMachin
return ''
}
function LabInstall-IdOf($st) {
# the engine's machine id as the fleet names it: the first 8 hex of api/state.machine_id (the per-install id; the intake header's
# machine= and the registry's ae432dc7 / 1ccfe586 are that prefix); '' when the field is missing
if ($null -eq $st) { return '' }
$id = [string]$st.machine_id; if (-not $id) { $id = [string]$st.machine }
if ($id -match '^[0-9a-f]{8}') { return $id.Substring(0, 8) }
return ''
}
function LabInstall-EngineMachine() {
$urlFile = Join-Path $env:LOCALAPPDATA 'igneum\app\app.url'
if (-not (Test-Path $urlFile)) { return '' }
try { $u = (Get-Content $urlFile -Raw).Trim(); $st = Invoke-RestMethod -Uri ($u + 'api/state') -TimeoutSec 5 -UseBasicParsing; return [string]$st.machine } catch { return '' }
try { $u = (Get-Content $urlFile -Raw).Trim(); $st = Invoke-RestMethod -Uri ($u + 'api/state') -TimeoutSec 5 -UseBasicParsing; return (LabInstall-IdOf $st) } catch { return '' }
}
function Lab-Install($task, [string] $dlBase) {

View file

@ -25,6 +25,8 @@ Expect 'refusal 3d: no engine answers (nothing installs blind)' (LabInstall-Refu
Expect 'refusal: a public Setup name is not a lab Setup' (LabInstall-Refusal (Mk 'Igneum-Miner-Setup-2.0.3.exe' $sha 'ae432dc7' $sig) 'PC1' 'ae432dc7') 'not a lab Setup file name'
$t = Mk 'Igneum-Miner-Lab-Setup-2.0.3.exe' $sha 'ae432dc7' $sig; $t.body = "# lab-install`nStart-Process evil.exe`n"
Expect 'refusal: a body with a line that is not a pinned value (nothing of a body ever runs)' (LabInstall-Refusal $t 'PC1' 'ae432dc7') 'not the pinned form'
if ((LabInstall-IdOf (@{ machine_id = 'ae432dc7b92c1817' })) -ne 'ae432dc7') { Write-Output 'FAIL id-of: not ae432dc7'; $fails++ } else { Write-Output 'ok id-of ae432dc7b92c1817 -> ae432dc7' }
if ((LabInstall-IdOf (@{ version = '2.0.3' })) -ne '') { Write-Output 'FAIL id-of: a state without machine_id must read empty'; $fails++ } else { Write-Output 'ok id-of: no machine_id -> empty (refused later as no engine)' }
if ($fails -gt 0) { Write-Output ('RESULT lab-install agent test: ' + $fails + ' FAIL'); exit 1 }
Write-Output 'RESULT lab-install agent test: 9 of 9 as expected (1 acceptance, 8 refusals)'
Write-Output 'RESULT lab-install agent test: 11 of 11 as expected (1 acceptance, 8 refusals, 2 id reads)'
exit 0

View file

@ -26,7 +26,7 @@
"in_progress": true,
"method": "model",
"evidence": "docs/analysis/class-v6/1p5x/lab/README.md; docs/analysis/class-v6/1p5x/lab/table.md",
"note": "The lab's interface and the candidate table at the fan-out: the frozen v6 control carried from the record (the house 5090 at its knee 4,011 nJ per hash, board power; the X0 amendment 5b rows: the DRAM board 2.35x same node WITNESS, the N2 die 7.8x the worst credible), the cohort rows for the 3090, the 5080 and the AMD and Intel tiers NOT RUN, adversarial set v1 pending; the three other controls (ProgPoW 0.9.4 reference, FishHash, the cooperative ARX candidate) NOT RUN with their clocks. No score is the lab's until the cohort and the adversary rows are in; R15-01, R15-08 and R15-09 stay NOT RUN until read. X10 (cand-x10) joins the table NOT RUN with its per-lane assignments and clocks; COHORT's ctl-v6 denominator set is in flight on eight rented pods. 12:1x UK: adversarial set v1 on the table (the frozen v6's same-node board 2.57x, 2.04 to 3.00, the fused tail CLAIMED until the routed lanes land; the die 11.4x as a coexistence row); the coexistence table (interface section 8b) added as the scoreboard's headline; SEARCH's first screen recorded as SCREEN rejections. Still NOT RUN: no cohort score until COHORT's eight rows are read back. 12:2x UK: set v2 (the routed fused-ARX lanes) makes the v6 board 2.60x a WITNESS; the ctl-v6 coexistence table (the board holds at every price; the N2 die pushes the GPU owner out above 14,300 dies at USD 0.10) is the headline; X10 SCREEN with the card modelled (the board 3.00x at 118 loads). Still NOT RUN: the cohort rows in their timed runs. 12:3x UK: the first cohort cells (ctl-v6 at stock on rented 5090, 5080 and 3090 pods: the worst cell the 3090 at 8,429 nJ = 5.46x on set v2's same-node board, PARTIAL, the dataset size under decision after CONTROLS measured the live 4 GiB object at 2.4x the 1 GiB research pack's rate); X10's first measured cell (cand-x10b on the 4090 at stock 3,653 nJ per lane-work = 5.8x on the board; the fold buys nothing); set v3 (routed 64-register and multiply-xor lanes); the fourth to sixth review rulings (8c); the 4 GiB rule (8e). Every row still NOT RUN until read. 12:4x UK: ctl-v6's first full score over the NVIDIA cohort at stock (the worst cell the RTX 4090 uncapped 8,751 nJ = 5.67x on set v2's same-node board; every cell at 4 GiB, the earlier 2.4x reading an instrument artefact, corrected once); the two-phase rows (ADVERSARY 545f3f8a0, 36d17b15c): phase B NOT LIVE until a shipped package proves, the shipping row open; SEARCH's twenty candidates on set v3 none under 1.5x on any cell (SCREEN). Every row still NOT RUN until read.",
"note": "The lab's interface and the candidate table at the fan-out: the frozen v6 control carried from the record (the house 5090 at its knee 4,011 nJ per hash, board power; the X0 amendment 5b rows: the DRAM board 2.35x same node WITNESS, the N2 die 7.8x the worst credible), the cohort rows for the 3090, the 5080 and the AMD and Intel tiers NOT RUN, adversarial set v1 pending; the three other controls (ProgPoW 0.9.4 reference, FishHash, the cooperative ARX candidate) NOT RUN with their clocks. No score is the lab's until the cohort and the adversary rows are in; R15-01, R15-08 and R15-09 stay NOT RUN until read. X10 (cand-x10) joins the table NOT RUN with its per-lane assignments and clocks; COHORT's ctl-v6 denominator set is in flight on eight rented pods. 12:1x UK: adversarial set v1 on the table (the frozen v6's same-node board 2.57x, 2.04 to 3.00, the fused tail CLAIMED until the routed lanes land; the die 11.4x as a coexistence row); the coexistence table (interface section 8b) added as the scoreboard's headline; SEARCH's first screen recorded as SCREEN rejections. Still NOT RUN: no cohort score until COHORT's eight rows are read back. 12:2x UK: set v2 (the routed fused-ARX lanes) makes the v6 board 2.60x a WITNESS; the ctl-v6 coexistence table (the board holds at every price; the N2 die pushes the GPU owner out above 14,300 dies at USD 0.10) is the headline; X10 SCREEN with the card modelled (the board 3.00x at 118 loads). Still NOT RUN: the cohort rows in their timed runs. 12:3x UK: the first cohort cells (ctl-v6 at stock on rented 5090, 5080 and 3090 pods: the worst cell the 3090 at 8,429 nJ = 5.46x on set v2's same-node board, PARTIAL, the dataset size under decision after CONTROLS measured the live 4 GiB object at 2.4x the 1 GiB research pack's rate); X10's first measured cell (cand-x10b on the 4090 at stock 3,653 nJ per lane-work = 5.8x on the board; the fold buys nothing); set v3 (routed 64-register and multiply-xor lanes); the fourth to sixth review rulings (8c); the 4 GiB rule (8e). Every row still NOT RUN until read. 12:4x UK: ctl-v6's first full score over the NVIDIA cohort at stock (the worst cell the RTX 4090 uncapped 8,751 nJ = 5.67x on set v2's same-node board; every cell at 4 GiB, the earlier 2.4x reading an instrument artefact, corrected once); the two-phase rows (ADVERSARY 545f3f8a0, 36d17b15c): phase B NOT LIVE until a shipped package proves, the shipping row open; SEARCH's twenty candidates on set v3 none under 1.5x on any cell (SCREEN). Every row still NOT RUN until read. 13:0x UK: the decider closed on both cards (the 4 GiB object costs 2.0 to 2.9 percent of rate against its 1 GiB export; the 2.4x reading withdrawn as a contention fault); the read-headroom row answered (both cards at their activation limit); the uncapped 5090 cell 5,980 nJ = 3.88x on the board; the shipping row's facts by file and line with the Devnet 4 correction (a 24 GB card proves the v1 shard now; the proving row NOT LIVE until the epoch record by 16:00); the 4 GiB cap defined as the mining dataset floor only; the founder's ledger order (8f) applied. Every row still NOT RUN until read. 13:1x UK: CONTROLS' done line (the four controls, Etchash and Autolykos2 staged bit-exact with SUMS); ADVERSARY's cross-chain phase A and B (no chain's emission recovers a board chip; the proving share the one term) and the E9 Pro calibration (1.28x pessimistic); the first founder bundle 985afee6. Every row still NOT RUN until read.",
"claim_impact": "none"
}
],