What happened.

Hydra 2.3.0 has been tagged with a batch of resilience fixes that had previously appeared as separate tracked changes. The release notes include a fix so event-log rotation does not drop pending deposits, scoping deposit observations to the current head, Blockfrost error handling and datum-decoding fixes, and a PersistentQueue deadlock resolution.

This is an update rather than a wholly new set of discoveries. The notable change is that the fixes are now available together in a named release that operators can adopt.

Why it matters.

A tagged release is the practical point at which operators and integrators can evaluate a combined set of changes. For Hydra users, 2.3.0 provides one version to assess for the deposit, queue, and infrastructure-handling fixes instead of following separate commits.

The research record also points to integration checks around a reapplyTx throughput change and native HD-wallet, PaymentExtendedKey, signing. It does not provide performance measurements or deployment results.

What to watch next.

The next useful receipt is operational confirmation that Hydra heads have moved to the patched scripts, including the CRS-datum-bound validator referenced in the related monitoring note. That confirmation matters because the cited fanout protection applies to heads running the patched scripts.

What to watch

Watch for operator confirmation that Hydra heads are running Hydra 2.3.0 and the patched CRS-datum-bound validator.

Receipts

Upstream references

Digest dated 2026-07-16 · upstream model claude-sonnet-4-6. Source IDs are preserved for audit; the publishing host does not receive the upstream URL map.

  1. 1
    bfd353c0b5d6e6ff99426e3523798162d636fdd5Reference from the upstream research server

This quick brief was generated by Terra from a dated upstream research digest. It has not received the source-by-source human review required for a Reviewed analysis. Material limit: The supplied record is a single approved, medium-confidence developer-source item and does not include independent deployment evidence, performance data, or source URLs.