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

release 0.3.13: the exec checks red at the close, the cause, the four rules, 0.3.14 named

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs 2026-10-06 15:52:54 +00:00
parent 025cc19b76
commit f688f5bcd4
1 changed files with 11 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
docs/plans/release-0.3.13.md
View file

@ -126,9 +126,17 @@ the seed on 83089544 at 7bd98cc4; the Mac 0.3.12 (paused on the project lead's o
| the fix | the proving agent's, as 0.3.14 (the tooling refuses "0.3.13.1"): never replay from genesis on a pruned node (unwind through the persisted generations, else a peer's snapshot over protocol 16); keep executing from the persisted state when the pruning point passes the anchor (the anchor only for a node with nothing); never overwrite a good snapshot with a tip-0 one |
| node 1's follower | found in the same hour: node 1's `chain follower stopped` at every start since 12:37Z because both hands bound the eth_ JSON-RPC on 26790 and node 1 lost ("Address already in use"), so the Mac app's node never executed; `restart-hand-nodes.sh` now gives node 1 26791 (this commit), live at the next hand restart |
Rules from it: a miner never stays on the old side across an activation (the switch jobs go out before the height; an activation height is
never set inside a rollout window, the floor of 10,800 exists for that); a hand node restart is announced before it runs (the 14:56:28Z
SIGTERM of both hands by an unnamed hand cost 24 minutes of stale stats); the two hands never share a port.
Rules from it (the coordinator's four and two more): the switch jobs go out before the height, no miner stays on the old side across an
activation; an activation height is never set inside a rollout window (the floor of 10,800 exists for that); a deep reorg must not reset the
exec layer (unwind through the persisted generations, else a peer's snapshot; never a genesis replay on a pruned node); the pruning point must
not strand an anchor (a node keeps executing from its persisted state, the anchor is for a node with nothing); a hand node restart is
announced before it runs (the 14:56:28Z SIGTERM of both hands by an unnamed hand cost 24 minutes of stale stats); the two hands never share a port.
The exec checks of section 2 are therefore RED at the close of this cut (every node at `eth_blockNumber` 0 since 15:44:47Z, `startedFrom`
genesis or snapshot-at-0, `paidShards` 0; the chain, the finality locks and the hash untouched; the proving ledger below the trust DAA pays
as carried once the exec layer is back); the cause is the pruning point past the anchor and the genesis replay over the snapshot; the fix is
0.3.14 (node-only, the proving agent's branch; one publish with the object carried over and a hand-node swap first if it is code-only, the
exec check per node the gate; two publishes only if a field changes; no re-pin of the anchor). The coordinator's decision 15:53Z.
## 5. The one line for the project lead