What happened.
Hydra’s fanout benchmark has been updated so its transaction-cost table is no longer fixed at 10 parties. It now tests several party counts and reports the largest UTxO set that still fits for each case.
The change makes the trade-off more visible: as the number of parties rises, additional participation tokens leave less room for outputs. Builders sizing Hydra heads can use the table to compare fanout constraints across participant counts.
Why it matters.
This is useful capacity-planning information for teams working with Hydra, particularly where the expected number of participants and the size of a UTxO set both affect fanout feasibility. The broader feed was thin and heavily focused on Hydra and Leios development work, so this is a narrow builder-facing update rather than a general ecosystem event.
What to watch.
Watch for further benchmark results or tooling that expands the range of tested conditions and clarifies how builders should apply the measurements in practice. The relevant receipt is the upstream Hydra benchmark update identified by source ID 4751556664bc08e614f2cda5057d33ef8efb0436.
Further Hydra benchmark updates that add tested conditions or practical guidance for applying the party-count results.
Upstream references and independent checks
Digest dated 2026-08-04 · upstream model claude-sonnet-4-6. Direct links are matched to all 1 upstream source IDs.
- 1Vary the number of parties in the fanout benchmark (#2796)Direct upstream source ·
4751556664bc08e614f2cda5057d33ef8efb0436
This Research brief was generated by Terra from a dated upstream research digest. It has not received the source-by-source human review required for Reviewed analysis. Material limit: This is single-source benchmark tooling with medium confidence; it is not a protocol change or evidence of a performance improvement to fanout itself.