Counter ASIC 3.0 node plan 6.9: the 0.3.21 node line opened at 55768f88 with main's order and its first gate line
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
parent
165cdf9e8f
commit
77dee2c87e
1 changed files with 9 additions and 0 deletions
|
|
@ -181,6 +181,15 @@ Rules this day added: a kept-datadir restart gate on a standing box's datadir co
|
|||
|
||||
Main's assignment (7 October 2026, 12:3xZ): 0.3.20 ships class v4 sub-version 1 at object byte 5; class v5 is 6 (class-v5 16afd0a0, class-v5-node 699db5a2, the flip case passed on 6,6,6); class v4 sub-version 2 (the hash lane's dataflow-freshness rule plus the saturated-source count, on ca3-v4-amend after 8c728ca3) takes 7. Sub-version 2 is 0.3.21's and its re-pin is not in the 0.3.20 path. The re-pin on the node side, once the hash lane's commit string and the new devnet epoch-0 id land: archive that commit's igneum-pow beside the fork as the paths-override copy and rsync it to the boxes; `CLASS_SIGNAL_V4` 5 → 7 with its tests (0x0702, 1794; a byte-5 block does not count towards the sub-version-2 flip); the kaspa-pow vector test's pins moved (the sub-version-2 id must-equal, with `PROGRAM_SUBVERSION_V4` 2; sub-version 1's 1a4230699a6b9c60 joining c120d7963abdcd96 as must-differ); the daemon's window line naming object 7 and the two earlier streams; the fast-time signal harness stamping 7 for a signaller and 5 for the non-signaller; then the kaspa-pow and consensus-core suites on build-2. The script that applies the fork side in one run sits in the lane's scratchpad (repin-sub2.py: the commit and the id as arguments); about 20 minutes of edits and 2 minutes of suites. The same split-protection arithmetic as 6.6 applies: a byte-5 node that sees byte 7 counts it as v4 (its rule is at least 5), flips to ITS stream (sub-version 1) at the same epoch and forks alone, every block refused by the sub-version-2 id check; the sweep replaces every 0.3.20 node before the sub-version-2 floor, and the floor sits a week past the 0.3.21 publish as 6.6 sets it.
|
||||
|
||||
### 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).
|
||||
|
||||
| Gate | Candidate | Run (UTC) | Line |
|
||||
|---|---|---|---|
|
||||
| Digest | 55768f88, sha256 279b1b690e854fc9, the string read back | 13:35:41 to 13:37:19 | PASS: thirteen fields a89be8a7 on both binaries, the peers as the gate wants them; sixteen fields db9a85f9 refused, no peer; the live file's digest eada4bda |
|
||||
| Mixed-version, ten minutes beside the 5899f603 pair | 55768f88 | from 13:37:40 | (the line follows) |
|
||||
|
||||
## 7. 0.3.17 node items after the 3.0 lane (Horizon queue, 6 October 2026, evening)
|
||||
|
||||
Numbering (the shipper, 6 October 2026, 22:4xZ): this tree ships as 0.3.17. 0.3.16 became the corrective cut of 0.3.15's tree the same night (the Mac and PC 1 had taken early 0.3.15 builds), node f1ea7a38 unchanged. The branch keeps its name `ca3-v4-0316` and the commit messages their "0.3.16"; every "0.3.16" in the fork's code comments means this tree.
|
||||
|
|
|
|||
Loading…
Reference in a new issue