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

Counter ASIC 2.0 status 00:40: floor-sweep-4 rows (mine-and-prove beside the miner), M16 go

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs 2026-10-06 00:38:33 +00:00
parent 38a78419ac
commit 43c2951867
1 changed files with 13 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -732,3 +732,16 @@ No further rollout tonight beyond the planned object sweep (done: every live nod
The crossing into class v3 at N4 = 154,800 (epoch 43) lands at about 03:50Z (DAA 143,104 at 00:35:28Z, the observer, about 1.0 DAA per second) with nobody awake. Armed at 00:35:28Z on the Mac, detached (nohup, pid 49195): `infra/devnet/crossing-watch.mjs` (ca2-coord), read-only against the observer's JSON-RPC (ws://127.0.0.1:28640, getBlockDagInfo and getBlockTemplate every 15 s) and the fleet's job lines every 5 minutes, writing to /tmp/igneum-devnet/crossing-154800.out: a RESULT line per epoch change (class, generator, era, seed, activation, boundary, DAA, blocks), the crossing line at the first epoch at or above N4, the chain's blocks per minute on each side, and a verdict (FAIL on a non-v3 first epoch, no block for 10 minutes after the crossing, the observer not answering, or the after-rate under a quarter of the before-rate; PASS otherwise 90 minutes after the crossing; deadline 08:00Z). Dry run at 00:34:32Z read epoch 39, class v2, generator 2, era 0, activation 154,800, boundary 144,000, DAA 143,065. It touches no node, miner or job. The morning reads that file first (`grep RESULT /tmp/igneum-devnet/crossing-154800.out`), PC 1's relaunch second. What it cannot see: a miner's own "pack refused" or "need" lines (those are in each machine's intake; the chain's rate after the crossing is the proxy), and a fork between the hand nodes (the observer's sink only).
floor-sweep-4: the agent's first publish at 00:22:49Z was refused by publish-jobs.sh's kit-path check (added 21:49Z; the measurement template reached the chain job's kit without a Test-Path) and its command showed only the last line, so it waited on a job that did not exist until my repeated go; fixed in the template (the kit tested first; an update that wiped it gives measure_failed rows instead of a killed run), republished 00:33:32Z, 3 to 4 minutes. Next on PC 2 after its close: the ledger M16 job, the repro job, agg-cost-pc2-5, the ledger-fixes-0311 suites.
## 00:40 floor-sweep-4 green: mine-and-prove beside the 5090 miner; the M16 job has its go
floor-sweep-4 (00:34:19 to 00:37:49Z, 210 s, exit 0): the v3 server b37defef beside the 0.3.11 miner at full rate (the card at 95 percent, 338 W, idle-with-miner 3,833 MiB inside every peak), the prover off then back on, the live server untouched, every proof VERIFIED by the unpatched host (1,272,897 bytes, verify 37 to 40 ms):
| cfg | fixture | cycles | peak MiB (miner inside) | prove s | alone (sweep 3) |
|---|---|---|---|---|---|
| element threshold 2^26 | fees-v1-shards2 (the adopted v1 shard) | 4,717,439 | 12,066 | 24.4 | 10,291 MiB, 5.7 s |
| element threshold 2^25 | fees-v1-shards2 | 4,717,439 | 12,066 | 43.5 | |
| element threshold 2^26 | block-83616 (empty) | 280,706 | 11,586 | 13.0 | 9,971 MiB, 3.3 s |
| budget 12 GB (2^27) | fees-v1-shards2 | 4,717,439 | 14,786 | 17.4 | 12,915 MiB, 4.3 s |
Reading (the tier call is the prover-floor agent's write-up): the prover's own share beside the miner is 12,066 minus 3,833 = about 8.2 GB on the v1 shard at 2^26, the same as alone, so a 12 GB card fits mine-and-prove on paper (8.2 GB plus a miner's 1 GiB dataset and working set, about 10.0 GB of 12.3 before the display); 2^25 buys no memory (12,066 either way) and costs 1.8x the time. The cost is time, not memory: 24.4 s per shard beside the miner against 5.7 s alone (4.3x; the miner holds the card), 13.0 s on the empty shard against 3.3 s; with proving v1's 8-block segments at about one block per second, a 12 GB card that mines and proves at once proves slower than the chain makes segments, so the 12 GB tier is prove-only or mine-and-prove at a reduced mining share, which is the proving-methods S_p/2 reading. Not measured: any real 12 GB card. PC 2 released 00:37:49Z; "go PC 2" to m16-inline-pc2-1 at 00:39 (about 8 min), then the repro pair (fetch-repro-pc2-20261006, run-repro-pc2-20261006, about 14 min), then agg-cost-pc2-5 (about 12 min), then the ledger-fixes-0311 suites.