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

release 0.3.12: the plan widens to the node change (the fresh-record rule switch, the segment-aligned prover)

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs 2026-10-06 08:40:18 +00:00
parent 9245d1592b
commit d2fcf93e68
1 changed files with 17 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

27
docs/plans/release-0.3.12.md
View file

@ -1,10 +1,12 @@
# Igneum Miner 0.3.12: app only, prepared to the publish gate, 6 October 2026
# Igneum Miner 0.3.12: the fresh-record rule switch (proving v1) and the app cut, prepared to the publish gate, 6 October 2026
Release engineer, from 08:05 UTC, on the coordinator's instruction ("prepare 0.3.12, APP ONLY, up to the publish gate and STOP there; the project lead
gives the go"). No node change, no override change, no consensus parameter: the node fork stays 89dfcb95 (`release-0.3.11-node`), the
override the nine-field object of 0.3.11 (digest 0139ab9d...), the packaged line unchanged. Worktree `/Users/joshm/Projects/igneum-wt-ship0312`,
branch `release-0.3.12` from master ddfcdac; `vendor/` symlinked to the main checkout's (46 entries) with `vendor/igneum-node-0312` pointing at
the 0.3.11 fork worktree (89dfcb95). The 0.3.11 recipe (`release-0.3.11.md`) throughout; every Mac build under the main checkout's lock;
gives the go"), widened at 08:55Z on its clock: "no longer app only", the proving agent proved the segment record rule needs a consensus
switch, so the node fork `proving-v1` 0f0dda95 (`proving_v1_fresh_rule_daa`: never by default, in the digest only once set; from it a fresh
segment record is valid whenever the previous segment is not proven) and the app's segment-aligned prover (272b025, docs aea2f6a) ride in it.
Worktree `/Users/joshm/Projects/igneum-wt-ship0312`, branch `release-0.3.12` from master ddfcdac; `vendor/` symlinked to the main checkout's (46
entries); the fork worktree `vendor/igneum-node-0312`, branch `release-0.3.12-node` = 0f0dda95 cherry-picked onto 89dfcb95 (its parent ece42979
is inside 89dfcb95, so the rebase is the one commit: `params.rs`, `exec/proving.rs`, `exec/rpc.rs`, `daemon.rs`) = **83089544**. The 0.3.11 recipe (`release-0.3.11.md`) throughout; every Mac build under the main checkout's lock;
igneum-labs commits. Times are UTC.
## 1. What 0.3.12 carries
@ -18,14 +20,19 @@ igneum-labs commits. Times are UTC.
| Ember Tune: two-knob plans + priors + the UI line; every quit names its source (b671c8b); a second engine never runs the updater (e600e63, C35); no pipe into a second engine (8ab9068); `jobrun.rs` elevated `follow_file` (1e9550e); the BOM fix + CI check (8273494); Power control switch (49bbe14 = 3562f26); `igneum-gpu-telemetry.exe` (ADLX) built by `build-windows.sh` and carried in the Windows inputs | `ember-tune` 9a6469f | NOT MERGED: conflicts in seven files against the 0.3.10/0.3.11 app (its base ca8d9f3 predates both): `ci.yml`, `config.rs`, `engine.rs` (the detect path, the power-cap plan, the test module), `ui/app.js` (four hunks against miner-ui-2's View), `ui/index.html` (the settings panel 0.3.10 removed), `proto-opencl/README.md`, `bench-log.md`. Its agent is rebasing it onto release-0.3.12 (section 2) |
| The hidden-console builder for every elevated launch, `windows-spawn-check.mjs`, the PC 1 console-watch scripts | `job-console` 13755b9 (+ 3562f26 Power control) | NOT MERGED: conflicts in six files (`ci.yml`, `config.rs`, `engine.rs`, `jobrun.rs`, `app.js`, `index.html`), base a93199a; carried by the ember-tune rebase (it already holds 3562f26) |
| The miner's gRPC resubscribe after a node restart (C43, the 0.3.11 finding) | no commit exists (the ledger entries b19fe5f, 0751dde, c8c831c only) | OWED, listed in section 10 |
| The fresh-record rule switch: `proving_v1_fresh_rule_daa` (Option, never by default; a node with the field set prints it and carries it in the digest; a fresh segment record is valid from it whenever the previous segment is not proven) | fork `proving-v1` 0f0dda95 on ece42979 | cherry-picked onto 89dfcb95 as 83089544 (`release-0.3.12-node`) |
| The segment-aligned prover: a segment record the chain rule refuses is held and offered again every pass until the segment closes; the fast-time harness on the fresh-record rule (both cases); the prover host and export; the WSL2 prover package script; `infra/fast-time/override-60x.json` (measured by its agent: 9 segments per 30 min on PC 2, 72 of 72 shards paid, 11% hash cost, 17.6 GB peak) | `proving-v1` app 272b025 + docs aea2f6a (on 6714a45) | merged 49e0e2c (clean) |
| The packaged line (C34): the ten-field object of section 4 | 7dd3ff7 | `packaged-config.sh --test` passes |
| The six version files | 81e4ecb (`--check`: 0.3.12 in all 6) | |
Left out on the coordinator's word: the node fork, prover-floor's server (its packaging row is 0.3.13), explorer d7e797c, pool-v0, rig-install,
ota-k2, the ledger forks.
Left out on the coordinator's word: prover-floor's server (its packaging row is 0.3.13), explorer d7e797c, pool-v0, rig-install, ota-k2, the
ledger forks.
Changelog line (draft, for the manifest notes at the go): "Igneum Miner 0.3.12: the GPU list in performance order; an old update no longer
waits for the hour; Ember Tune (every card tuned for MH per watt, Power control off by default, the app never asks for administrator
rights on its own); a second engine never installs over the app; /api/state always answers; HiveOS rigs carry the override. Node unchanged."
Changelog line (draft, for the manifest notes at the go): "Igneum Miner 0.3.12: the fresh-record rule for proving v1 from DAA 192,000 (a fresh
segment record is valid whenever the previous segment is not proven) and the segment-aligned prover; the GPU list in performance order; an
old update no longer waits for the hour; Ember Tune (every card tuned for MH per watt, Power control off by default, the app never asks for
administrator rights on its own); a second engine never installs over the app; /api/state always answers; HiveOS rigs carry the override.
Node 83089544."
## 2. The branch