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

Plan 0.3.17: the fork gate's green line (aa0182aa rides 0.3.18; the switch is at never)

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

2
docs/plans/release-0.3.17.md
View file

@ -34,5 +34,5 @@ App tests on the merged tree: 175 + 28 + 8; UI 41. A whole-file take of a lane's
- exec-sync-0313's consensus verification behind a feature off for Windows (the proving lane), then its two commits.
- finality-pause-node rebased onto the 0.3.17 node (the finality lane).
- decimals (B10 gate), vote-weigh and tail-emission docs: the next cut.
- The fork gate's fast-time line is not green (a private chain forked at an idle node's own tip passed as an extension); the switch is at never, the fix lands in the plan later (node lane). vote-or-burn and the signing bonus: the replay gate FAILED on both, so neither may be set anywhere.
- The fork gate's fast-time line is GREEN on aa0182aa (gate on: a 27.5 percent key's private chain 183 DAA deep refused, 268 refusal lines, the honest node kept its chain; gate off, the known-failed case reorgs), one commit past the 9a44fcb8 this tree carries; the switch is at never on every network, so 9a44fcb8 stands for 0.3.17 (the chains were building) and aa0182aa rides 0.3.18. vote-or-burn and the signing bonus: the replay gate FAILED on both, so neither may be set anywhere.
- The canary in the full form before publish (a new node mining beside an old one with a poisoned peer, ten minutes, a mid-window re-sync), the staged-in-scratch rule, every new switch at never.