From 7fabc3bf1f948c0d87b6c39ee8e0cc8edc0d300d Mon Sep 17 00:00:00 2001 From: igneum-labs <337424239+igneum-labs@users.noreply.github.com> Date: Wed, 7 Oct 2026 06:15:13 +0000 Subject: [PATCH] release 0.3.18 plan: the cut at ae17ad00, chains restarted, the two canary reads for PC 1's rules Co-Authored-By: Claude Fable 5.1 --- docs/plans/release-0.3.18.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/plans/release-0.3.18.md b/docs/plans/release-0.3.18.md index d0adbea83..2298705db 100644 --- a/docs/plans/release-0.3.18.md +++ b/docs/plans/release-0.3.18.md @@ -154,3 +154,7 @@ The merge of ca3-v4-0318 (8220c944) into 12153428 with the six resolutions, plus Digests on the Mac binary: sixteen eada4bda (igneum_getNodeInfo: powEngine igneum-pow, blockrate {bps 1, finalityDepth 43200, ghostdagK 18, mergeDepth 3600, pruningDepth 108000}), thirteen b18ed271, no file c562d70e (re-read on free ports, 06:15Z). All three unchanged from 0.3.16/0.3.17. (suite, integration check, seed, hive, inputs, Windows run, staging, canary: rows as they land) + +## 11. The cut: release-0.3.18-node = ae17ad00 (the node lane's word, 06:14Z) + +1cf43254 plus the second merge of ca3-v4-0318 (e3a00bf0: 4f7c56a0 PC 1's two node rules, getBlockTemplate answers inside its timeout during the finality catch-up and isSynced reads false while the catch-up is behind; e3a00bf0 the installing-tests move on that branch too). Box at ae17ad00: `cargo test -p kaspa-consensus` 111 in the lib plus the two moved targets 1 each, p2p-flows 37, `cargo check -p kaspad -p kaspa-rpc-service -p kaspa-testing-integration --tests` clean. One hand fix in the merge: the W7 leaves block in template_section rides the template snapshot like the other items (newest 32, emitted last under the leave_active gate). The 1cf43254 chain was stopped at its seed step (its suite: see r0318/ae17/box-1cf43254.log) and both chains restarted on ae17ad00 at 06:2xZ. The canary form gains two reads for PC 1's rules: on a restart with a kept datadir, every getBlockTemplate inside 5 s through the catch-up (no "template fetch timed out" lines), and isSynced false while the catch-up holds the finality state, true after.