From 94fffa79041fd32298229799ed3d2d721cc10f08 Mon Sep 17 00:00:00 2001 From: igneum-labs <337424239+igneum-labs@users.noreply.github.com> Date: Wed, 7 Oct 2026 19:26:55 +0000 Subject: [PATCH] Node lane, plan 6.10: the heights re-cut 2720d8d2 and its gates, the 0.3.23 node pin Co-Authored-By: Claude Fable 5.1 --- docs/plans/counter-asic-3-node.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/plans/counter-asic-3-node.md b/docs/plans/counter-asic-3-node.md index 0c16da53e..2a8d044f7 100644 --- a/docs/plans/counter-asic-3-node.md +++ b/docs/plans/counter-asic-3-node.md @@ -244,7 +244,9 @@ 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 | -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. +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. The shipper's margin ruling (19:1xZ) re-cut the heights: a4415ab2 (72,000 / 79,200 / 86,400) discarded, release-0.3.23-node = **2720d8d2** on a099594f with difficulty_v3_activation_daa 79,200 (about 16:01 BST 8 October), finality_daa_rule_activation_daa 86,400 (about 18:01 BST), finality_leave_activation_daa 93,600 (about 20:01 BST); the testnet keeps the two crossings at never. Gates, UTC: build 19:20:59 (sha df6476ed…), core 153 19:17:07, miner 25 19:18:12, pow 17 19:19:42, exec 39 19:23:27, consensus 123 + 1 + 1 at 19:23:58 (the rerun at gate priority; the first run's one red was the latency test on a box at load 426), canary 19:21:06 to 19:22:25 with the digest ba75bf6f by design. THE 0.3.23 NODE PIN, named 19:26Z; the app side's release-0.3.23 (4cdcab31) takes it. Class v5 and the testnet re-cut ride 0.3.24. Rule from main (19:2xZ): no box run except through the build-server lane's lease tool. + +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.