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

release 0.3.17 plan: the cases' verdict (PASS; relay-into-target void by topology); 0.3.17 closes

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs 2026-10-07 06:36:51 +00:00
parent 017553b8c5
commit a7a9e5c231
1 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -121,3 +121,7 @@ Mac (d937c69d): app 0.3.17 applied 04:51:43Z; own node pid 20371, the bundle's i
- 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.
**Cases verdict, 06:35Z: PASS on every read the form could take on c17-1 (d712b498).** Over the 12-minute window (poison 713ef876 mining on the 1026 datadir, relay 6615571c with 20 peers): c17-1 wrong-version 0, from-relay 0, got-reject 5 (the hands' traversal drops at 06:04 to 06:08Z on the pool's stale blocks; none after), synced throughout at the hub's height (125,871 at 06:35Z); the mid-window restart at 06:28:47Z with the hub as its only peer re-synced in 3 s. Poison: 47 blocks accepted by its own node, 0 rejected, got-reject 1. Relay: 1,680 blocks relayed, wrong-version 0, got-reject 31 (the hands' traversal drops on the pre-window 1026 chain, the right outcome). Hub: "wrong block version" 0 today on the hotfix, rejects naming c17-1 0; the clean form's read of 19 blocks held by c17-1's key at 05:04Z stands (its miner was off after the restart). VOID: the relay-into-target case (c17-1 never connected to the relay: same RunPod host, no hairpin); re-run on 0.3.18 with pods on separate hosts. Pods c17-1, c17-relay, c17-poison destroyed.
**0.3.17 closes on this line.** Open for the next tree: PC 1's workers (the two rules in 0.3.18), PC 2 offline, the CI payload exe sha difference on the day's check list, the relay-into-target read on 0.3.18.