Node lane, plan 6.10: the Devnet 3 join-and-restart PASS on 34a2dbaa, the a099594f digest fix row, the heights commit a4415ab2

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

docs/plans/counter-asic-3-node.md

@@ -234,7 +234,7 @@ The line after 69d1b56e (17:3xZ, main's orders through the shipper): 6ed56f63 re
 |---|---|---|---|
 | Build-1 release build; the five build-2 suites; the canary set | 6ed56f63 | 17:34:46 to 17:37:54 | GREEN: igneumd sha256 91a3fa43...5193; consensus 122, miner 25, exec 36, pow 17, core 152; testnet canary (empty start on igneum-testnet-1, digest 87d103b6, shutdown 627 ms, override refused, two-node handshake, a devnet-3 dialler rejected) |
 | Build-1 release build; the five build-2 suites; the canary set | 34a2dbaa | 17:39:43 to 17:42:51 | GREEN: igneumd sha256 bc25693c...85bb carries 34a2dba (/srv/artefacts/0322-34a2dbaa/node-lane/); consensus 122, exec 37, pow 17, miner 25, core 152; canary set 17:40:34 to 17:41:52, digest 83eb50cd unchanged, shutdown 567 ms |
-| Devnet 3 join from empty, one accepted block, kept-datadir restart with the new continuity line and the hub's tip number (the fleet, a fresh 3060; the control dn3-c1 on 69d1b56e prints the old line) | 34a2dbaa | fleet | (the fleet lane's line) |
+| Devnet 3 join from empty, accepted blocks, kept-datadir restart with the new continuity line and the hub's tip number (the fleet, dn3-c1, a Vast 3060) | 34a2dbaa | 19:01:41 to 19:10:13 | PASS: joined from a wiped datadir (synced 19:03:18Z, 7,262 blocks), 7 accepted blocks by 19:06:30Z; kept restart 19:07:07Z resumed from exec-snapshot.bin (tip 2799) and printed the new line "the 2799 records up to the tip 2799 are continuous with the DAG"; tip 2879 equal to dn3-g1's by hash, and 2850/2860/2870 number the same on both (offset 0). The known-failed control: the same box's 69d1b56e kept restart at 18:15:07Z printed the old form ("the 0 records above the restart pin are continuous") |
 | The three mid-chain crossings on infra/fast-time/switch-crossing.mjs (switch at DAA 240; a late joiner across it; then the known-failed digest-split case per switch) | 34a2dbaa pair | from 17:45 | (below as they land) |
 | Crossing, difficulty v3 | 34a2dbaa pair | pass 17:58:58 to 18:08:16; known-failed 17:54:33 to 17:58:50 | GREEN: crossing at DAA 243, one chain on A and B, no rule error, the late node synced across it, post-crossing rate 1.065 against 1 with the difficulty moving (six bits values); the digest-split case FAIL as expected ("Refusing peer: consensus params digest mismatch", two chains, the joiner on A's) |
 | Crossing, the finality DAA-seconds rule | 34a2dbaa pair | round 2 17:58:58 to 18:08:16; known-failed 17:54:33 to 17:58:50; round 3 from 18:09:31 | the chain's reading green (checkpoint 18 locked at blue score 511 after the crossing at DAA 247, finality active on both miners); the harness's verdict read used {count} for getFinalityCheckpoints' {last} and saw nothing, so the gate line is round 3's |
@@ -244,7 +244,7 @@ The line after 69d1b56e (17:3xZ, main's orders through the shipper): 6ed56f63 re
 | Crossing, the finality leave rule, round 3 | 34a2dbaa pair | 18:12:01 to 18:21:20 | GREEN: crossing at DAA 241; B's clean stop at DAA 299 announced its leave with 2 voters, the count 1 from the next checkpoint on (14 to 16 locked by 1); one chain, no rule error, the joiner synced |
 | Round 3's first start (18:09:32) | 34a2dbaa pair | | both nodes exited at once: the 0.3.22 binary refused the 0.3.23 line's `subsidy_per_block_activation_daa` in the shared 60x file (deny_unknown_fields); the harness now drops null fields at write |
 
-All three crossings green (pass and known-failed) by 18:21:20Z. The 0.3.23 line after 18473645: 0ead4613 (the genesis-forward lane's rebase of daa61847: the sig_scheme byte, the W5 key succession, the ladder's cache rung; digest arms enter only when set: the cache rung's mib and flag with the ladder, sig_scheme_activation_daa then sig_scheme, finality_succession_activation_daa; the devnet digest unchanged, the testnet's moves on this line), merged as a fast-forward at 18:20Z with its gates; the heights commit follows on top once the fleet's lock line fixes the DAA-to-clock offset.
+The 0.3.23 line after 0ead4613: a099594f (the cache rung behind its own switch `latency_ladder_cache_rung_activation_daa`, never on every network, the testnet at 0; Devnet 3 reads 83eb50cd again on the canary, 18:56:38Z; build 18:56Z sha effa5c17…, exec 39 18:55:08Z, pow 17 19:02:25Z, miner 25 19:03:55Z, consensus 125 19:05:48Z, core 145 + the fast-time file's two late fields), then a4415ab2, the HEIGHTS commit cut on the fleet's lock line (checkpoint 235 locked 19:02:46Z at about DAA 7,298): difficulty_v3_activation_daa 72,000 (about 13:01Z, 14:01 BST, 8 October at 1 block/s), finality_daa_rule_activation_daa 79,200 (about 16:01 BST), finality_leave_activation_daa 86,400 (about 18:01 BST), one weight window apart; the digest moves by design. All three crossings green (pass and known-failed) by 18:21:20Z. The 0.3.23 line after 18473645: 0ead4613 (the genesis-forward lane's rebase of daa61847: the sig_scheme byte, the W5 key succession, the ladder's cache rung; digest arms enter only when set: the cache rung's mib and flag with the ladder, sig_scheme_activation_daa then sig_scheme, finality_succession_activation_daa; the devnet digest unchanged, the testnet's moves on this line), merged as a fast-forward at 18:20Z with its gates; the heights commit follows on top once the fleet's lock line fixes the DAA-to-clock offset.
 
 Height arithmetic proposed to main (18:1xZ): the first crossing after every node, the apps' included, runs the commit (apps publish 18:30 BST 8 October), so difficulty v3 at DAA 93,600 (26 h after the first block at 17:06Z 7 October, about 20:06 BST 8 October), the other two 7,200 apart after it, each crossing read on every node before the next; the fleet's lock line fixes the DAA-to-clock offset.