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

release-0.3.22 plan: section 2, 21d8f454 green on every box gate and the canary set; the app side's first commit and the packaged peers

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

6
docs/plans/release-0.3.22.md
View file

@ -27,3 +27,9 @@ Three commits on 96161037: bd710a36 the sub-version 3 re-pin (byte 7, igneum-pow
**Main (17:4x BST): yes to the second node per standing box**, three waves of 5/5/4 after the genesis pair locks, nothing stopped on the old chain, with two conditions: (1) a 24-hour exception to the one-miner-per-GPU rule, not a new rule: when the apps move to Devnet 3 and the old chain's miners stop, each box is back to one miner (written as an exception with its end in the fleet notes); (2) the contention read on wave 1 decides the fallback mechanically: a live miner's rate on any of the five down more than 10 percent against its hour-before mean, or the dn3 node's template latency above the 0.3.20 gate figure, takes the 3070 set for the remaining waves without asking; spend under the USD 1,000 ceiling either way.
**The app side of 0.3.22 (the shipper):** the app's node starts on igneum-devnet-3 through its packaged config (Runtime.network "devnet" with devnet_suffix 3, read from igneum-app.json in the 0.3.22 package; the OTA update replaces the package, so the signed 0.3.22 update is the move), with node_dir devnet-3 (a fresh datadir beside devnet-v4, the old chain's kept for the way back), the node_override_file None on a suffixed devnet (the node refuses the file; the OTA manifest's consensus.override is ignored with a log line on devnet-3), the chain scene, the ladder, first-block and earnings reading the new chain from zero, the prover on the new chain's records; the manifest for the 0.3.22 publish carries channel "devnet-3". Cut after the genesis on its own branch release-0.3.22 off release-0.3.21's tip; published by signed update when Devnet 3 has 24 hours (main's clock).
## 2. The candidate moved to 21d8f454 (16:43:11Z); every box gate GREEN by 16:48:48Z (17:49 BST)
21d8f454 = one test-only commit on fa7f854f (the signalling integration tests read object 7 as 1794, the pow pairing test allows sub-version 3's retried draw, the miner's pool test fills the era fields); every gate runs on the exact commit, so fa7f854f's build (1db7c6ac) is void. On 21d8f454: the release build on build-1 GREEN 16:45:19Z (igneumd sha256 b96b424c7b284501306dbf4a76657fd1e359c0c6532c59a0daf431547fcca21d, carrying 21d8f45; igneum-miner c29f33bb…; the artefact at /srv/artefacts/0322-21d8f454/, handed to the fleet); igneum-exec 36 of 36 (16:45:31Z); kaspa-consensus-core 151 of 151 (16:48:25Z, the parent's fast-time file carrying the era fields); kaspa-pow 17 of 17 with the sub-version 3 pairing id a785001687d8688a (16:47:10Z); kaspa-consensus whole 120 + 1 + 1 at object 7 (16:47:54Z); igneum-miner 25 of 25 against the sub-version 3 packs (16:48:48Z; cpu_recheck reads a785001687d8688a). The canary set from the artefact on build-1 (16:45:53 to 16:47:11Z): the empty-datadir start GREEN (data dir igneum-devnet-3; "stamps object version 7 into its headers (block version 1794)"; "Era VDF active from DAA 0: scheme 0 (class-group), T 108000000, era 15552000 DAA, lead 7200"; the ladder at rung 0 with 27 shadow passes; calibrated v1 fees from DAA 0; proving v0 and v1 from DAA 0 with the embedded keys resolving both ids on the bare node); the igneum-devnet-3 digest with no file ab9af79f40cd9b5fbed2577406d6b32e103bd86a7dd26df2aabceb7b673ced23; shutdown under 1 s (571 ms); the override file refused on devnet-3 with exit 1 (the known-failed case) while the shared devnet still takes it (eada4bda unchanged); two empty devnet-3 nodes handshake on protocol 17 with equal digests; a shared-devnet node dialling devnet-3 rejected "Network mismatch - local: igneum-devnet-3, remote: igneum-devnet". The node side is ready at 17:49 BST. Remaining before genesis, the fleet's: the fresh-genesis agreement on dn3-g1 and dn3-g2 from empty, the late joiner's sync; then the genesis clock. The prover pair stands (21d8f454:igneum/evm-types = fe4145b9, the exec pin's tree).
**The app side (release-0.3.22 at 5f1652c0 on origin):** the package names the network (igneum-app.json node_devnet_suffix and node_peers; Runtime::from_env_with when the environment is silent; node_dir devnet-3 beside devnet-v4, the old chain's datadir kept for the way back); no override file on a suffixed devnet from 3 (the manifest's consensus override ignored with one log line); the version strings 0.3.22; the app gate on build-2 258 + 32 + 8. Packaged peers for devnet-3 (the fleet, 16:50Z): build-1's seed 188.40.146.49:26631 and node1-dn3 188.40.146.49:26671 only (dn3-g1's and dn3-g2's mapped ports are not stable across a pod restart; they stay the fleet's seeds for the fleet's nodes); a third static peer would be a Hetzner box or the project lead's GEX45-1, outside the fleet's rent. Next on the app side: packaged-config.sh and make-payload.sh writing the two fields for the 0.3.22 DMG and installer; the manifest's channel "devnet-3"; the publish by signed update when Devnet 3 has 24 hours.