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

Counter ASIC 2.0 status 03:56: the crossing held (epoch 43 class v3 at DAA 154,814, 03:51:42Z); C46 on the next-cut list

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs 2026-10-06 03:55:26 +00:00
parent 9632d78921
commit 6cca0c4cab
2 changed files with 7 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

File diff suppressed because one or more lines are too long

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

@ -778,3 +778,7 @@ The ledger-fixes-0311 suites on PC 2 (build-20261006-012543, published by me fro
The job-runner finding (the aggregation-cost agent, 01:30): the app ran three jobs on PC 2 at once from 01:24Z (run-prover-on-pc2 at 01:24:21Z and the suites build at 01:26:15Z landed while nothing else of the queue was expected to run), whereas at 23:40Z PC 2's update-now queued behind the hung sweep ("1 new for this machine, 1 queued"). So the app serialises the jobs it fetches in one poll and runs jobs from different polls side by side; "one job on PC 2 at a time" held tonight by coordination only. Next-cut item (with the update-now item): the runner takes one job at a time per machine whatever the poll, and a `collect` or `update-now` may pre-empt.
PC 2's prover: off from 00:49Z (the repro job) to 01:24:09Z (job 6's finally block), then confirmed on by run-prover-on-pc2 at 01:24:21Z; about 35 minutes of PC 2's shard payouts lost. Every PC 2 job of the night is closed; nothing is queued. The crossing watcher (pid 49195) runs to 08:00Z; the morning reads /tmp/igneum-devnet/crossing-154800.out first. The coordinator's final report to main follows this entry; the status file ends here unless the morning adds to it.
## 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.