Week 27 · 2026
Jun 29 – Jul 5, 2026 · gathered Aug 13, 2026
- 2
- PRs merged
- 1
- PRs opened
- 5
- Closed
- 2
- Opened
- 0
- Releases
- 1
- Repos
- 18
- Commits
- 1
- Comments
Highlights
2 PRs merged, 5 issues closed and 18 commits: a week of closing out long-standing bugs rather than opening new fronts.
Operational Excellence (M3). Both merged PRs landed here: pre-rotated databases are now kept around for operators who want the history (#2748), and the node no longer observes deposit events from unrelated Heads (#2743). Persistence backup before rotation was filed and closed the same week (#2747), and selective partial fanout opened (#2750), merging in W30.
Maintenance and DevX (M5). Three older issues closed: the
--deposit-period consistency issue (#2725), closed ahead of the PR that
enforces it, which lands in W30, the hydra-formal-specification
repo moved back into the monorepo (#2727), and the unrelated-Head deposit
observation issue (#2606) closed behind its fix. The hydra-tui reporting
NodeInSync too often was filed (#2749) and closes in W30.
Performance (M2). The report of node memory steadily increasing and never dropping (#2624) was closed as not a bug: the GHC runtime holds freed memory rather than returning it to the OS, and the RTS flag that returns it brought the figure down.
Activity
Merged PRs, issues, and releases grouped by deliverable — the evidence behind the narrative above.
M3 Operational Excellence
In progress- MergedKeep pre-rotated databases around, for people that want history.cardano-scaling/hydra · @noonio
- MergedDon't observe unrelated Head depositscardano-scaling/hydra · @v0d1ch
- PR openedImplement selective partial fanoutcardano-scaling/hydra · @vrom911
- Issue openedBack up persistence before rotationcardano-scaling/hydra · @noonio
- Issue closedBack up persistence before rotationcardano-scaling/hydra · @noonio
M5 Maintenance and DevX
In progress- Issue openedhydra-tui gets too many reports of NodeInSynccardano-scaling/hydra · @noonio
- Issue closedMove the hydra-formal-specification "repo" back into the "monorepo"cardano-scaling/hydra · @noonio
- Issue closedMake sure all hydra-nodes in a Head use the same --deposit-periodcardano-scaling/hydra · @v0d1ch
- Issue closedNode observes and persists deposit events from unrelated Headscardano-scaling/hydra · @leuhk
M2 Performance
Done- Issue closedHydra node memory steadily increases and never dropscardano-scaling/hydra · @kenlau666
Other / Reactive
18 commits · cardano-scaling/hydra