igneum-network/igneum
1
0
Fork 0
Code Issues Pull requests Releases Activity

Counter ASIC 2.0 status 04:17: proving v1 active with 0 segments proven (C47), the morning line

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs 2026-10-06 04:16:32 +00:00
parent 6cca0c4cab
commit 0678ae05d5
1 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/plans/counter-asic-2-status.md
View file

@ -782,3 +782,7 @@ PC 2's prover: off from 00:49Z (the repro job) to 01:24:09Z (job 6's finally blo
## 03:56 THE CROSSING HELD: epoch 43 is class v3 (generator 3) from DAA 154,814 at 03:51:42Z; the chain continued
The watcher (pid 49195, /tmp/igneum-devnet/crossing-154800.out): epoch 42 read "next v3" from 02:51:53Z (DAA 151,212); the first template of epoch 43 at 03:51:42Z: class v3, generator 3, era 0, seed edc4fa84 (the genesis stand-in), boundary 158,400, DAA 154,814. The consequences reviewer's own watcher read DAA 154,808 at 03:51:38Z. The chain after the crossing: DAA 154,943 at 03:54:06Z (block time 1.22 s, 4 miners, 137 MH/s unchanged, the reviewer's read); the observer at 03:55Z: DAA 155,004, blocks 109,467, sink moving; 61 to 62 blocks per minute before, the after-rate and the verdict (PASS if the after-rate holds a quarter of the before-rate with no 10-minute gap) land at about 05:21Z in the same file. The block count fell from 153,857 to 108,621 between 03:35:41Z and 03:40:41Z: the observer's pruning at 03:39:45Z ("SMT root was rebuilt successfully following pruning"), not a reorg (the DAA rose through it); it sits inside the before-window only, so the verdict's before-rate (the last 10 minutes before the crossing) is clean. Still to read in the morning: each machine's STATUS rate after the swap and the intake's "pack refused", "need" and "mismatch" counts (the reviewer takes them at 04:02Z into the ledger), PC 1's relaunch (it crosses at its relaunch through the manifest), and the laptop's return. C46 (the reviewer, 03:54Z): /api/stats still prints "generator v2" from a literal in site/api/stats.mjs line 39, so the public API misdescribes the chain from the first v3 epoch; next cut: the handler names the class and generator the observer records from the epoch line.
## 04:17 proving v1 active with nothing proven (C47): the morning summary says so
The consequences reviewer at 04:16Z: node 1's igneum_getProvingStatus.v1 reads active, segmentsInWindow pending 54, proven 0, unproven 21, paidSegments 0, no segment record carried; PC 2's upload shows no proving line since 03:44Z while v0 shards still paid at 13 per 10 minutes. So the honest line for the morning is "class v3 crossed and held; proving v1 active since 03:51:42Z with 0 segments proven in its first 25 minutes (cause pending from the proving agent)", not "0.3.11 activated". Consequence per tier while it lasts: no segment pays and no aggregator share (10%) is earned, v0 shards keep paying; the fee switch at H = 210,000 (about 18:56Z) is unaffected but C1 (every prover on 0.3.11 by 16:00Z) now has a second condition, that a prover proves v1 segments at all. The proving agent has the ask (PC 2's prover state after the crossing, the app's v1 segment path, aggregate_once); any PC 2 job it needs is one job on my go; a 0.3.11 app cause joins the 0.3.12 list at the top beside 6714a45.