From 3438c3f1e2d6c328de4757aa9bc9d87ca0cc57f6 Mon Sep 17 00:00:00 2001 From: igneum-labs <337424239+igneum-labs@users.noreply.github.com> Date: Wed, 7 Oct 2026 20:00:19 +0000 Subject: [PATCH] release 0.3.22 section 10: the shared chain id 4463 and its replay window as a fact, Devnet 3 to 4464 in 0.3.24, the chain-id uniqueness gate, the steward's two items closed, the second proven-share hour, the pool hour Co-Authored-By: Claude Fable 5.1 --- docs/plans/release-0.3.22.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/plans/release-0.3.22.md b/docs/plans/release-0.3.22.md index 2e3a152ca..390f4105a 100644 --- a/docs/plans/release-0.3.22.md +++ b/docs/plans/release-0.3.22.md @@ -104,3 +104,11 @@ Three commits on 96161037: bd710a36 the sub-version 3 re-pin (byte 7, igneum-pow **PC 2 tonight:** the take-4 0.3.21 installer (mingw host, run-20261007-175020) was picked up at 18:51:57 BST before its removal deployed and the runner's abort ended the install in its first second (the build-server lane's fault, two rules added to the job tooling: an installs-app job is never removable without --force; never remove a published job without reading the machine's latest line); the update-return lane re-ran the kept installer at 19:07:56 BST and the 0.3.21 engine then restarted four times a minute apart and died ("quit requested by the window host went away (stdin closed)" 3 s after the node start: an engine started by a parent whose stdin closes at once); the founder reinstalled PC 2 by hand with the public 0.3.20 installer (45b2f3fb, the MSVC host; the public alias confirmed as that file by hash at 19:12:54 BST). PC 2 is read-only for every lane until its app uploads as 0.3.20; then the 0.3.22 installer job (--installs-app) and the smoke, one job at a time; then the Intel lane's driver retry with the minidump copy folded in (one UAC click). PC 1: released to the Counter lane's queue at 19:04:37 BST (the 0.3.21 MSVC host e223db18 built there in 9 s, collected by the relay Blob); one slot for the 0.3.22 host (app/windows/version.h moved to 0.3.22, host.cpp untouched). + +## 10. The chain id finding, the proven share, the pool hour (20:5x to 21:0x BST) + +**Chain id, a fact for the record (main's ruling 21:0x BST):** eth_chainId answers 0x116f (4463) on both the live shared devnet and Devnet 3 (the fleet's read at 20:59 BST while closing the steward's MINER_KEY item), so from Devnet 3's first block at 18:06 BST until the 0.3.24 sweep a signed transaction replays across the two chains by the chain id alone (the networks refuse each other at p2p; a raw transaction carried by hand to the other chain's RPC is accepted). Nothing of value sits on either chain. Devnet 3 takes its own chain id, 4464, in the 0.3.24 object (the v5 object moves the digest anyway), every Devnet 3 node and app in the same sweep, existing transactions judged by the chain id they carry at acceptance. Rule from tonight, a gate check: every network object names a chain id no other object carries (the shared devnet 4463, Devnet 3 4464, the testnet 4462, mainnet its own), a test over every Params table, known-failed first on tonight's duplicate. + +**The steward's two items before the public repository opens, both closed:** tools/exec-attacks/lib/common.mjs MINER_KEY is the public Anvil/Hardhat default account 1 key (five harnesses use it; balance 0 and nonce 0 on both chains at 20:55 and 20:59 BST; the fix is a chain-id guard in the five harnesses and a README line, a 0.3.24 steward row); app/igneum-wallet/src/hd.rs's KEY in one history commit is the public Hardhat default account 0 key in a removed test. + +**Proven share, the second hour (20:59 BST):** cumulative 0.468 (1,848 of 3,952 shards since DAA 0); the hour's own segments 0.84 (1,094 of 1,304), the shortfall mostly the 34a2dbaa sweep's one-minute node restart per prover; eleven provers (five 3060s at about 85 s a segment, two 3090s, three 4090s, one A5000), a twelfth starting; the next hour's own segments should read one and the founder's 24 hours count from the first that does. **The pool hour** counts from 20:33:28 BST (dn3-pool-b's first OPEN SHARE on the 017e7037 daemons a357c581; WRONG HASH 0 since), the pool split's condition.