Janzeer node 0.1.10

Hotfix after the node-five freeze of 25 October and the Raspberry Pi outage of 26/27 October. Protocol 3.4.0 and API 1.1.0 unchanged — a rolling upgrade; every validator should install it, home boards first.

What happened. On 25 October the project's fifth node committed the block that carried its own validator registration and then stopped at that height for four hours, healthy by every health check and without one log line. On 26 October a Raspberry Pi validator went silent the same way for 13 hours after a power glitch. Both ended only with a stop and a fresh start.

Fixed — a tip re-check could lose its retry loop (F-056). When a node falls behind it asks its peers whether they know its tip; the first answer starts a catch-up session. On a fast link the answer arrived before the node had armed its retry loop; the late arming then cancelled the session's own page timer and replaced it with a loop that stayed silent while a session existed. One lost page request after that meant PROCESSING for ever. The round is now armed on the sync thread, retry loop first and request second, so no answer can overtake it; a retry period that finds a live session re-requests the outstanding page; and every catch-up session start is logged.

Fixed — a validator re-validated two epochs at its own registration (F-056, second part). Committing the block that registers this node's key switched the node to full sync mode and re-ran the boot sweep over the last two epochs, on the consensus thread, under the ledger lock, even when the node already was in full mode. The switch is now a no-op when nothing changes, and a real switch runs after the commit, off the consensus thread.

Files: janzeer-node-0.1.10-mainnet-linux-x64.tar.gz, -linux-arm64.tar.gz, -windows-x64.zip, janzeer-node-bin-0.1.10-1-x86_64.pkg.tar.zst, SHA256SUMS, SHA256SUMS.minisig (project key RWQBrkWzg4V5n5wUBa9GNPpa95Z7WFT2EY5QrabMv/DP+KG+gJsPIgdr). Docker: ghcr.io/janzeerorg/janzeer-node:0.1.10.