What happened
Hydra merged change #2746 to address a replay-time failure involving inline datums. The reported issue affected non-canonical inline datums, including definite-length CBOR arrays that are valid on L1.
During Snapshot, HTTP, or event-replay paths, a UTxO JSON round-trip could lead to an inline datum hash mismatch. The change deserializes the original inline-datum bytes directly, with the aim of preserving those bytes through the round-trip.
Why it matters
For Hydra head operators, the failure could cause a node to crash during event replay when L2 UTxOs carried affected inline datums. The change is therefore a narrow but practical reliability improvement for Hydra applications that use inline datums.
Builders with relevant L2 outputs can test replay behavior against a build that includes #2746 to check whether the mismatch no longer occurs. This is operational software information, not financial advice.
What to watch next
The main receipt to watch is a tagged hydra-node release that includes this fix. The record also says an upstream cardano-api fix remains pending, and one property test is marked xprop.
A tagged hydra-node release that ships #2746, plus progress on the pending upstream cardano-api fix.
Upstream references
Digest dated 2026-07-10 · upstream model claude-sonnet-4-6. Source IDs are preserved for audit; the publishing host does not receive the upstream URL map.
- 1
1c816c49d1caafa817c86414799f4181a46b932aReference from the upstream research server - 2
440c57f1550202acb8b9af521da0c1162b500611Reference 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 evidence is a merged repository change from a thin, dev-only source record. It does not establish a released hydra-node version, deployment status, or broad production impact.