From 8fa128c137bcb5bf25c194d3a10f042d3f378237 Mon Sep 17 00:00:00 2001 From: igneum-labs <337424239+igneum-labs@users.noreply.github.com> Date: Mon, 5 Oct 2026 23:56:45 +0000 Subject: [PATCH] Counter ASIC 2.0 status 23:57: PC 2 on 0.3.11, publish 2 go, N4 stands Co-Authored-By: Claude Fable 5.1 --- docs/plans/counter-asic-2-status.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/plans/counter-asic-2-status.md b/docs/plans/counter-asic-2-status.md index 82ac54ebb..f5e373303 100644 --- a/docs/plans/counter-asic-2-status.md +++ b/docs/plans/counter-asic-2-status.md @@ -673,3 +673,9 @@ The consequence for PC 2 (the shipper's fact, 23:31): since the hand nodes moved 23:40. "PC 2 clear" given to the shipper. floor-sweep-2 never wrote a point row (three identical 1,139-byte progress uploads at 23:26, 23:31 and 23:36Z: start, gpus, the v2 server fb3165d8, the live server untouched, idle 2,060 MiB, nothing after); the prover-floor agent's reading: rows are written per point and sweep 1's points took 11 to 18 s, so 18 minutes without one means the first proof never returned (hung, not slow). So nothing was in flight to protect and PC 2 updates now; the update's restart kills the job tree, so its finally block (prover on, the patched server's process ended) never runs: the prover-floor agent's restore-and-diagnose job is PC 2's first job after the update, then the aggregation-cost re-run (its parser takes 0.3.11's CardState; the identities step first), then M16, then the repro job. The 12 GB prover-floor rows stay unmeasured until that diagnosis says why the v2 server hangs on point 1; sweep 3 only if it is under 10 minutes tonight. Also the consequences reviewer's C42: the new side had no miner from 23:24Z (the Mac app came back paused from a persisted Pause; the observer read 0 miners), so the new side's DAA clock stood still until the laptop's and the Mac's miners joined; N4 = N5 and H slip by the stall's length, and PC 2's old-side chain wins the reorg when it joins (allowed by the C4 rule). The shipper carries the fix (resume the Mac's miner; "the new side has at least one miner" as a step-1 check next time). 23:47. PC 2's update-now (update-now-0311-1ccfe586, published 23:39:44Z) queues behind the hung sweep: the app fetched it at 23:40:13Z ("1 new for this machine, 1 queued") and runs jobs one after another, so it waits for floor-sweep-2's 30-minute cap (about 23:51:17Z) rather than killing it; PC 2 reads "0.00 MH/s, waiting | 0 peers, syncing" meanwhile (refused by the new side, its miners stopped by the sweep). Decision: let the cap expire, no relay task (the two relay tasks tonight that touched that box both force-restarted it). The new side mines on the Mac at 21 to 23 MH/s; the laptop's 0.3.11 install is 15 minutes silent (its 0.3.10 install took 17). Then: PC 2's 0.3.11 STATUS line, "go PC 2" to floor-restore-1 (40 s, the diagnosis of the hang), the aggregation-cost re-run, M16, the repro job. Publish 2's DAA reading after PC 2 and the laptop show 0.3.11; the floor holds until DAA 144,000 (about 01:00Z after the stall). Next-cut item: an update-now pre-empts a running job, or the STATUS line reports the queue wait. Rollout plan updated (7e63cf5): 7d the step-1 stall (11 minutes, N4 about 03:40Z, H about 18:56Z, the step-1 miner check), the prover memory tiers (16 GB open, 12 GB waiting on patch v2), C41 HiveOS on the next-cut list and the tier line. + +## 23:57 PC 2 on 0.3.11; publish 2 has the go; N4 = N5 = 154,800 stand + +PC 2: the queued update-now ran 23:51:19Z (two seconds after the sweep's cap), the installer verified 23:51:22Z, the quit 23:51:24Z, the new engine 23:51:30Z (run win-1ccfe586-20261005-235130), igneumd 23:51:32Z, the 5090 miner 23:51:43Z with a clean first pack (self-test PASS); its node joined the new side at once (1 peer, DAA tracking the observer's). The hourly boundary at DAA 140,401 (23:52:21Z) fell 40 s after the worker's first pack: the worker refused the new epoch's jobs for 80 s until the app's attempt-aware path prepared it (attempt 0, the worker switched 23:53:42Z), then 113.4 MH/s wall at 23:54:14Z; the Mac's worker crossed the same boundary in 241 ms. The laptop is silent since its update-now at 23:28:28Z (its 0.3.10 install took 55 minutes of silence); publish 2 does not wait on it. + +Step 2a reading (the shipper, 23:55:42Z): tip DAA 140,706, floor 14,094 against the 10,800 minimum, so N4 = N5 = 154,800 stand, the nine-field object is unchanged and the target digest stays 0139ab9d...; a re-pin would only be needed past DAA 144,000 (about 00:55Z). Publish 2 given the go at 23:57: the hand nodes' and the seed's files switched and restarted, the nine-field manifest, update-now to the Mac and the laptop; PC 2's second restart on "PC 2 clear" after floor-restore-1 (its go at 23:56, about 40 s: the hang's diagnosis, the sweep's leftovers killed inside WSL2, the prover back on). Then on PC 2 once on the final state: the aggregation-cost re-run, M16, the repro job, the ledger-fixes-0311 suites (window about 00:50 to 01:10Z).