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

Counter ASIC 2.0 rollout: 7d the step-1 stall and the slipped times, the prover memory tiers

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-josh 2026-10-05 23:43:36 +00:00
parent 8e4972ee44
commit 7e63cf5ba0
1 changed files with 6 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -71,6 +71,8 @@ AMD RDNA 4 (the RX 9070 XT) sits at about a seventh of an RTX 5090 on this hash
HiveOS rigs (consequences C41, 23:33 UTC): untested on a GPU host tonight, and local mode never worked (the bundled node starts without the override file, so a local-mode rig has been refused by every devnet peer since the first height switch); the fix is the next cut's one HiveOS item (section 8a). The installer path with the hosted node is unaffected.
Prover memory tiers (the proving-methods agent, 23:42 UTC, from the prover-floor agent's patch v1 rows in docs/analysis/proving-methods.md on branch proving-methods, not pushed): the adopted shard falls from 20,516 to 12,708 MiB (idle included) with the 24 GB panic removed and the element threshold budgeted; the next floor is the server's Setup at 9,703 MiB (five recursion keys pre-built at 2^27 capacity). Per tier: the 16 GB tier opens now (prove-only at 2^27, 15.4 GB; mine-and-prove at 2^26 on paper, 14.4 GB, to be measured beside the miner); the 12 GB tier does not yet (12,708 MiB against about 12,288 MiB reported by a 12 GB card) and waits on patch v2, whose first sweep hung on point 1 tonight (floor-sweep-2; the diagnosis comes with floor-restore-1); if v2 misses 11 GB, the 12 GB tier's route is RISC Zero at po2 19 as a second ProofSystem version (its own cut, sized in hours by the agent that takes it, not in days). Recommended, for Josh: provedefault.rs gains the 16 GB tier; the rig installer runs one server per card; a 4070 or 3060 enters the measurement loop, since no 12 GB card has run a prover here (every 12 GB number is a 32 GB card's reading with a budget).
## 7. Gates before any publish (all of them, no exceptions)
| # | Gate | Evidence required | State |
@ -113,6 +115,10 @@ CORRECTION at 23:08 UTC, from the shipper's own finding: the relay machine named
3. The two open faults for a person at the machine: the source of PC 1's 22:31 quit and PC 2's 20:01 quit (the administrator-prompt class; the two-minute test of 4a), and the AMD clock and power sweep rows on the 9070 XT (owed; the card is present).
4. Not on the list any more: the eGPU reseat (the drops were readings of PC 2).
### 7d. The step-1 stall and what it moves (consequences C42, closed 23:39:49Z)
Publish 1 moved the hand nodes and the seed to 0.3.11 at 23:24Z with no miner on the new side: node 1 runs no miner, the Mac app came back from the update with its persisted Pause (paused since at least its 17:45Z run; the 18:xxZ finality restart job had already logged "its miner is paused"), and the fleet's hash was on the old side, refused. The new side made no block from about 23:29 to 23:39:49Z (11 minutes); the shipper resumed the Mac's miner through its API at 23:39:10Z (3.15 MH/s wall at 23:39:48Z, the first new-side blocks at 23:39:49Z). PC 2's old-side chain wins the reorg when it joins (the C4 rule allows it); every DAA-based time tonight slips by about 11 minutes: N4 = N5 = 154,800 about 03:40Z and H = 210,000 about 18:56Z on 6 October. Rule for every future publish: step 1 ends with "every new-side node has a miner, and the first new-side block is seen" before any update-now; no checklist read the fleet's pause state until tonight. The Mac's "compiled inline (not prepared)" line on that resume is the class v2 path only: a `class=v3` job never compiles inline on Metal (proto-metal/main.swift 3253 to 3267), it answers `need` and the miner prepares the current pair for it (fork igneum/miner/src/main.rs 2357, 2390), so a Mac resuming after N4 hashes v3 from the pack after one prepare round trip.
## 7a. A dated constraint from the consequences review (C1)
The fee switch H = 210,000 arrives about 18:45Z on 6 October (DAA 137,041 at 22:32:54Z on 5 October; 1.002 DAA/s averaged since 15:40Z; the 19:50Z in fee-switch-devnet.md is an hour late). The 0.3.10 node's export RPC carries no daaScore and no feesV1ActivationDaa (the proving v1 fork does), so from H every app prover on 0.3.10 has its shards refused and the devnet's proving goes dark. 0.3.11 must be on every prover before 16:00Z on 6 October; if it is not, the fee switch is republished at H = tip + 86,400 by the fee-switch plan's rule (a digest flip, every node in one sweep). The status file carries the timing against H.