From 2214f0f18a9d75fa8f522ed1cc37d44ed834e731 Mon Sep 17 00:00:00 2001 From: igneum-josh Date: Tue, 6 Oct 2026 00:38:49 +0000 Subject: [PATCH] Counter ASIC 2.0 status 00:40: the mine-and-prove reading corrected to the 600 DAA-s deadline rule Co-Authored-By: Claude Fable 5.1 --- docs/plans/counter-asic-2-status.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/plans/counter-asic-2-status.md b/docs/plans/counter-asic-2-status.md index 4d04dd4f0..d1f1aed97 100644 --- a/docs/plans/counter-asic-2-status.md +++ b/docs/plans/counter-asic-2-status.md @@ -744,4 +744,4 @@ floor-sweep-4 (00:34:19 to 00:37:49Z, 210 s, exit 0): the v3 server b37defef bes | 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. +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; that is inside proving v1's 600 DAA-second deadline by 25x, so a 12 GB card that mines and proves at once meets the deadline and simply takes fewer shards per hour (the per-prover throughput share, not a tier exclusion). The prover-floor agent's tier reading, on the 5090's allocation: a 12 GB card (12,288 MiB) mining and proving holds the server's 8.2 GB plus the miner's 1.7 GB plus its display (0.5 to 1 GB, not measured) = 10.4 to 10.9 GB, so it fits with 1.4 to 1.9 GB spare at 2^26 and 24 s a shard; the floor is now the Setup keys and the recursion stage (4.4 GB own after Setup plus about 3.8 GB at the recursion peak), so 2^25 is not a lever; a 16 GB card mines and proves at 2^27 (10.95 GB own plus 1.7) with 2.9 GB spare at 17 s. My earlier sentence here ("proves slower than the chain makes segments") was wrong against the deadline rule and is withdrawn. Not measured: any real 12 GB card (the on-order card runs the same two points). 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.