From 017553b8c5dd0f1b099086a8c52f4e2f4f7d745c Mon Sep 17 00:00:00 2001 From: igneum-labs <337424239+igneum-labs@users.noreply.github.com> Date: Wed, 7 Oct 2026 06:26:34 +0000 Subject: [PATCH] release 0.3.17 plan: the cases' interim (c17-1 clean, relay case void by topology, poison mining) Co-Authored-By: Claude Fable 5.1 --- docs/plans/release-0.3.17.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/plans/release-0.3.17.md b/docs/plans/release-0.3.17.md index 67683b332..be9dca391 100644 --- a/docs/plans/release-0.3.17.md +++ b/docs/plans/release-0.3.17.md @@ -115,3 +115,9 @@ Mac (d937c69d): app 0.3.17 applied 04:51:43Z; own node pid 20371, the bundle's i **0.3.17 is live** on every node that can take it: the 14 standing fleet boxes, the Mac, PC 1 (node; the workers wait for the project lead), the observer node, node 1 and the seed, all on commit string 5899f603, digest eada4bda, igneum-pow linked. PC 2 is offline since 02:00 UK (host unreachable) and takes the manifest when it returns. The canary's relay and poison cases run on as confirmation (verdict about 05:55Z); a FAIL there is a 0.3.16-with-the-fix rebuild by main's rule, not a rollback. The Discord card posts on this line. + +## 9. The cases (confirmation, interim 06:25Z) + +- c17-1 (d712b498) holds the live chain: wrong-version 0, from-relay 0, synced at 125,034 (hub 125,0xx), peers the two hands, the hub and pool-1; got-reject 5, all "traversal error: passed max allowed traversal (721 > 720)" from the hands at 06:04 to 06:08Z on the pool's 480-DAA-stale blocks c17-1 relayed (the pool daemon's fault, fixed in the pool lane), not a version matter. The hub (d712b498 since 05:27Z) has logged zero "wrong block version" lines since the hotfix (its only ones are yesterday's 22:28Z home-miner refusals). +- Relay 6615571c on the 1026 datadir: 19 peers, 1,238 blocks relayed, wrong-version 0; the hub dialled it outbound at 06:05:36Z and dropped it after one second on the traversal rule (its blocks are the pre-window 1026 chain, 721 deep), then took it inbound; 0 PoW accepted from it, the right outcome. The relay-into-the-target case is NOT exercised on c17-1: both pods sit on the same RunPod host (64.119.209.250) and the dial to the host's public port does not hairpin (0 lines for the relay's address in c17-1's log). On 0.3.18 the target c18-1 is on another host and the dial works. +- Poison 713ef876: synced from the relay 06:22Z, mining (accepted 0 at +83 s, about 3 minutes per block on a 3090 at today's difficulty), got-reject 1. Mid-window restart of c17-1 at +300 s, hub read at +720 s, then the verdict line.