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

Counter ASIC 3.0 node plan 6.7: the 0.3.20 node line's gates on b7cc37e7 and the fallback, with the harness artifacts and the rules the day added

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

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

@ -154,6 +154,22 @@ the project lead's word (15:2x UK, through the coordinator): option A, the load-
**Testing, limited by the project lead's word:** the digest test (the thirteen-field file b18ed271 unchanged, the sixteen-field object re-read on the amended binary; the sub-version is not a params field, so no digest moves), the mixed-version Devnet 2 gate on `node-compat.mjs` (an amended 0.3.20 node mining beside a 5899f603 node for ten minutes on the live file without the v4 fields, the old node accepting every block), and the fresh-join canary the 0.3.20 cut runs anyway; G4 to G6 recorded as owed. The fast-time signal harness (`class-v4-signal.mjs`) now stamps 5 for a signaller and 4 for the non-signaller, so its no-flip case also shows a byte-4 node not counting.
### 6.7 The 0.3.20 node line's gates (7 October 2026, UTC; the box runs CEST and earlier stamps in this section's messages read an hour fast)
The line on the mirror, branch release-0.3.20-node, pairing igneum-pow 8c728ca3: 8097d600 (object 5, isSynced, the weight-table cache, the lazy snapshot, the submit path, the 100 ms template wait, the finality reports with signers), 6b94c823 (test-only: the stale PC 1 test), 6a3432a3 (the key methods, the claims, the settled claim floor, the listener watchdog), 09124180 (N12: a held exec port is a retry), b7cc37e7 (N13: a kept 0.3.17 datadir's virtual-state row read through a v1 mirror and rewritten). Only b7cc37e7 is a pin for the one-box roll: every earlier build since 10db4b61 dies at start on a kept datadir.
| Gate | Binary | Run (UTC) | Line |
|---|---|---|---|
| Digest (thirteen-field base, sixteen-field refusal) | b7cc37e7, sha256 bc28331abf21f4d5 | 12:14:39 to 12:16:18 | PASS: thirteen fields a89be8a7 on both binaries, peers as the gate wants them; sixteen fields db9a85f9, refused, no peer; the live file's own digest eada4bda unmoved |
| Kept-datadir start (the fleet, p12-vast's copy of pool-1's 0.3.17 datadir) | b7cc37e7 | 12:17:12 and 12:18:53 | PASS: the first start reads the v1 row through the mirror and rewrites it ("1 mergeset rewards"), the finality blob converts (1,747 locks), the node up on its ports, no panic; the second start reads first-try, no rewrite line; 6a3432a3 died on the same copy (the known-failed shape) |
| Mixed-version, ten minutes beside the 5899f603 pair | b7cc37e7 | from 12:16:39 | (the line follows) |
| Digest | 6b94c823 (the fallback, sha256 b1b7d47b) | 11:56:45 to 11:57:52 | compat and refusal digests right; the one failed check read n3's peers at 1 with its refusal line present (the refused connection's reconnect in flight; the read is now the minimum of five, 36d3efdc) |
| Mixed-version | 6b94c823 | 11:57:53 to 12:08:05 | one digest b0afb2ee on all five, 146 new and 246 old blocks accepted, 0 rejected, counts equal through both joins and the restart; the one failed check: six "Address already in use" panics in the two OLD nodes' server threads, the gate started the second the digest gate's nodes got SIGTERM on the same ports (a 20 s gap now) |
| Mixed-version on the live sixteen-field file (void: the binary at the path was replaced mid-run) | 8097d600 | 11:42:55 to 11:53:07 | the interop fact: one digest on all five, the 5899f603 hub accepted 235 byte-5 blocks from the new node with 0 rejected, old headers 1026 (byte 4), new 1282 (byte 5), counts equal on all five at 472 before the restart step |
| Digest | 6a3432a3 | 11:53:17 to 11:54:23 | the digests right; three of four nodes exited inside a minute on the shared exec port (N12), the mixed-version run stopped as void |
Rules this day added: a kept-datadir restart gate on a standing box's datadir copy beside the wiped canary, every node cut; no persisted struct gains a field under `#[serde(default)]` without a versioned read (bincode does not default); never rebuild a binary at a path a running gate uses; 20 s between the digest and the mixed-version gates; the harnesses set no exec ports, so a bind failure must never be a death.
## 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.