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

Node lane, plan 6.11: the nine switches held at never on Devnet 3 (state, owner, gate, earliest height per row) and the 0.3.23 carry list

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs 2026-10-07 17:15:01 +00:00
parent 4d4c06c812
commit 263df893bd
1 changed files with 18 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -230,6 +230,24 @@ Two findings on the 21d8f454 artefact (16:5xZ), both the fleet's: (a) the engine
Not in 0.3.22: the N15 kept-datadir class (ledger N15, third paragraph), 0.3.23: fork branch n15-kept = dfae08e5 on 21d8f454 (the scan from the tip down, once per state generation, the pin's hash, the set-aside; exec suite 37, kaspad check green).
### 6.11 The nine switches held at never on Devnet 3 (main's record, 7 October 2026, 17:2xZ)
Each goes live on igneum-devnet-3 by activation height after its own gate, one at a time, no further reset (main's ruling through the shipper). The rows are the owning lanes' facts as sent; the heights are conditions, not asks.
| Switch | State | Owner | Gate (last green, commit; in 69d1b56e?) | Earliest Devnet 3 height |
|---|---|---|---|---|
| fork_gate_activation_daa (window 600) | built and gated | horizon lane | infra/fast-time/fork-gate-gate.mjs 6 of 6, 12:58Z 7 Oct on build-2 (6eb21fc9 = 437f0438 rebased); finality module 24 of 24 with five fork-gate tests; 437f0438 is in 96161037, so in 69d1b56e | genesis lock DAA + 7,200 (one weight window; inert before), once every node runs 0.3.21+ (the field enters the digest), after a mixed-version ten-minute run and a mid-window restart |
| peer_directory_activation_daa | built and gated as a prototype (no cut gate; no RPC listing, no persistence, no Devnet 2 crossing) | horizon lane | infra/fast-time/peer-directory.mjs 3 of 3, 12:34Z 7 Oct on build-2 (0cad5106); 2e32d5f6 in 96161037, so in 69d1b56e | condition first: two reachable Devnet 3 nodes announcing (--announce ip:port), then one weight window so their keys hold weight; after the fork gate |
| pool_split_activation_daa | built and gated (fast-time) | pool lane | pool/tools/open-gate.mjs, 12:53Z to 13:09Z 7 Oct on build-1 (node b0444f51, pool d48d9dd2): 90 of 90 members paid, 0 withheld; b0444f51 in 96161037, so in 69d1b56e | one open pool of two or more members mining Devnet 3 for an hour with the switch at never (IGNS/IGNP carried, exec roots agree), then the hour's last block + 7,200 |
| exec_restart_number / hash / state_root / trust_daa | built and gated on Devnet 2 (the 27276 pin, 0.3.14 to 0.3.21) | node lane | the digest and mixed-version gates on every 0.3.2x cut; Devnet 3 executes from genesis and needs no pin | never, unless main rules an EVM state reset; then the pin is a chain block at or above every node's pruning point, with a snapshot for nodes below it |
| difficulty_v3_activation_daa | built and gated (from genesis on the testnet object; the mid-chain crossing on the fast-time harness infra/fast-time/difficulty-v3.mjs, node lane) | testnet lane (rule), node lane (crossing) | testnet-object.mjs run 10 (10:12Z 7 Oct, 551 blocks, 0 rejected) and the two-node GPU gate (14:19Z); the 0.3.16 field is in 96161037, so in 69d1b56e | a crossing gate on the 60x harness against the 69d1b56e binary first; then the DAA window boundary after a mixed-version run; no condition from the rule's side |
| finality_daa_rule_activation_daa | built and gated from genesis | testnet lane | run 10 (first lock DAA 142, locks 5 to 18 across 600 s) and the 6,297-DAA late-join chain; in 96161037 | at 1 block/s the 30-s cadence equals the old rule, so the crossing is a no-op; any checkpoint boundary after a mixed-version run |
| signing_bonus_activation_daa (1,000 bps) | built; gated from genesis ONLY with c7ea1e21 (silent_split), which is NOT in 69d1b56e (without it a silent key reads 72 percent on the UTXO side and 80 on the EVM side, the known-failed run 1) | testnet lane (gate), node lane (carry) | run 10 identity for five miners over 551 blocks with the silent key at 72 on both ledgers | not before c7ea1e21 is in the running binary (0.3.23); then any height after the voter table is frozen (min_daa passed); a payout change, not a validity split |
| finality_leave_activation_daa (leave_delay 3,600) | built and gated from genesis | testnet lane | run 10 (a leave accepted at DAA 212, key out of the count at DAA 351; a leaver who keeps mining stays a voter until the delay); in 96161037 (0.3.16) | any height after a mixed-version run; independent of the W5 succession (daa61847, not in 69d1b56e) |
| proving_consensus_verify_daa (manifest ids shard 0x2b1a81cb..., aggregator 0x474678f3...) | built and gated from genesis (the late-join gate 14:36Z: 37 carried verified records through the headers proof; the known-failed side without the proof hold stalled at DAA 1,828); archive, gating and proof hold in 96161037 | testnet lane (gate), node lane (archive), fin-proof lane (re-pin) | the late-join harness and every pod gate with it on | the later of: main's word (the proven share reading one); every node on one pinned id set (the fin-proof re-pin 0x39db9d96 settled; a node with other embedded keys refuses to start); every Windows node with igneum-prove-host beside it; one pruning window (108,000 DAA, 30 h) after the LAST peer started on an archive-carrying binary |
Not in 69d1b56e and owed to 0.3.23 (the testnet lane's content check on 96161037): c7ea1e21 silent_split, d840537b subsidy_per_block_activation_daa, 420f9305 vote-or-burn removal (`vote_or_burn_activation_daa` still in two files), daa61847 W5 succession. Caveat on every testnet-lane row: its gates ran with the switch on from genesis; the mid-chain crossing on Devnet 3 is gated by the node lane (Devnet 2 or the fast-time harnesses) before any height is named. Clock conversion: DAA d after the genesis lock = lock time + d seconds at 1 block/s (7,200 = 2 h; 108,000 = 30 h).
## 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.