Updates

A second delivery route still gets a reply

A submitting gateway could miss the signed acknowledgements it needed to establish data availability because another member delivered the same body first. The data was present, but the acknowledgement went to the first deliverer rather than the gateway collecting it.

The v0.24.7 fix makes an eligible member reply to each sender even when it already holds the body. It does not store or flood the body again. A bounded cache reuses signatures for recently repeated acknowledgements. The gateway no longer has to win that delivery race to receive a reply.

The same change checks every supplied authorization—the signed approvals accompanying a transaction—rather than trusting an earlier cached copy. Retained content is served with the authorizations recorded by consensus, not whichever copy arrived first.

Stronger evidence, not a faster benchmark

The reviewed source passed CI and a separate full isolated container regression: 34 passing stages, no skips. Targeted tests exercise the late-arriving gateway and authorization variants. The load test now requires every node to show an empty outstanding queue at two fresh committed rounds after the flood, within the existing recovery budget. Workload and thresholds were not relaxed; this is not a before-and-after performance claim.

Easier access, repeatable checks

The Install guide now recommends the standalone Evolver MCP server: use your existing MCP client with its own local devnet follower, without installing the full Pi agent. The LLM proxy also has a publicly pullable v0.2.5 image; its existing deployment was upgraded with identity and configuration preserved.

Automatic branch and merge-request checks, plus on-demand isolated CI, now reuse the normal validation scripts and coverage gate.

Release status

Node v0.24.7 is published and its images verified anonymously pullable. Dependent releases and running-node upgrades are in progress and verified separately. This is not an all-nodes-upgraded announcement, and the previously reported runtime leak warnings remain unresolved.