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

Counter ASIC 3.0 node plan 6.9: the 0.3.21 order as it stands (the rebased strings, f95178a1, N15 last; the sub-version 2 re-pin dropped, sub-version 3 only if green by 19:00Z)

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs 2026-10-07 14:14:29 +00:00
parent 7712e90679
commit bbd3e7fc5b
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/plans/counter-asic-3-node.md
View file

@ -183,7 +183,7 @@ Main's assignment (7 October 2026, 12:3xZ): 0.3.20 ships class v4 sub-version 1
### 6.9 The 0.3.21 node line (opened 7 October 2026, 13:4xZ)
Main's word: the 0.3.20 pin is c4459193; release-0.3.21-node opens at 55768f88 (N14, the program ids from the embedded verifying keys). The order, each with its own gate line, one rebase round or 0.3.22: 55768f88; miner-reliability-20 f067f7c1 and the late-join commit 70e4601e (N9's second half); pool-finish-node b0444f51; horizon-node 6eb21fc9 (the fork gate, its field at never); peer-directory-node db28d331 (its activation at never); then the class v4 sub-version 2 re-pin (igneum-pow 8bdcbdd8, id a788661687db4bb3, byte 7; 6.8) held for the attack-pass census. The staging starts at the shipper's sweep-end word; the suites run on build-2 between merges and the digest is read after every one (eada4bda on the live file, the moved value on the moved file, since every switch is at never); every candidate binary takes every gate from its build (rules 4a and 4b).
Main's word: the 0.3.20 pin is c4459193; release-0.3.21-node opens at 55768f88 (N14, the program ids from the embedded verifying keys). The order as it stands at 15:2xZ, each with its own gate line, one rebase round or 0.3.22: 55768f88; the late-join commit 52e96c94 (70e4601e rebased onto 55768f88; N9's second half); miner-reliability-20 f067f7c1; pool-finish-node b0444f51; horizon-node 437f0438 (6eb21fc9 rebased onto c4459193 by the horizon lane; the fork gate, its field at never); peer-directory-node 2e32d5f6 (db28d331 rebased; its activation at never; one both-add of `DST_ADDRESS` beside pool-finish's `DST_BINDING` in consensus/core/src/finality.rs, kept at the merge); the genesis-forward lane's f95178a1 (the difficulty manager reading `params.pow_epoch_blocks`, the lib-suite flake's fix); then N15 (the chain-path continuity rule and the start-time self-check, branch numbering-fix). The class v4 sub-version 2 re-pin is dropped (sub-version 2 fails the attack-pass lane's 64-seed hot-set gate); a sub-version 3 re-pins on top only if it reads green on both attack-pass gates by 19:00Z, else it is 0.3.22's; 0.3.21 stages on byte 5 as 0.3.20 does. The staging starts at the shipper's sweep-end word; the suites run on build-2 between merges and the digest is read after every one (eada4bda on the live file, the moved value on the moved file, since every switch is at never); every candidate binary takes every gate from its build (rules 4a and 4b).
| Gate | Candidate | Run (UTC) | Line |
|---|---|---|---|