122 posts tagged with "hydra"

High-level Summary​

We've published the 2.2.0 release! It bundles up the partial fanout work and the hydra-tui revamp from the last couple of updates, together with a much richer benchmark suite (real-world TPS metrics, a Mixed UTxO generator, and a new matrix sub-command that sweeps cluster sizes and UTxO shapes, published to a scenario benchmarks page). On top of that we unified the on-chain membership checks around the BLS accumulator, which shrinks the snapshot-signing tuple and removes a pile of now redundant hashing, and started optimising snapshot processing so script-heavy heads don't pay to re-evaluate Plutus they've already validated.

What did the team achieve?​

• Released 2.2.0, packaging partial fanout, the hydra-tui revamp, and the new benchmarking work, with the changelog and network config updated accordingly
• Unified the membership checks: the three separate UTxO hash fields (utxoHash, alphaUTxOHash, omegaUTxOHash) collapse into a single accumulatorHash derived from the BLS accumulator, shrinking the snapshot signing tuple from 7 fields to 4, and full fanout now verifies outputs via a KZG membership proof (the same path as partial fanout) rather than a hash comparison #2619
• Started a snapshot-side throughput optimisation: transactions already validated on receipt are now re-applied via reapplyTx, skipping redundant Plutus script evaluation on the hot path, with a fallback to full application when a commit or decommit changes the active UTxO #2717
• Extended PR benchmarking: a "TPS" count (both waiting for TxValid and firing as fast as possible then counting confirmed-snapshot txns) #2635, and a benchmark comparison comment showing the PR-vs-master difference #2721
• Added a head-state visualisation tool for inspecting single states and diagnosing multi-party scenarios #2719
• Added a mustNotMintOrBurn guard to the Increment and Decrement validator transitions, consistent with all the other head transitions #2718, #2697
• Further validator fixes: CloseInitial now constrains the accumulator commitment, and the HeadStatus schema and Haskell types agree on Final #2712
• Removed leftover CollectCom/Abort handling missed in the original "directly open head" work #2709
• Switched to makeIsDataIndexed instead of unstableMakeIsData for stable on-chain constructor indices #2724, #2713
• TUI fixes: the increment dialog no longer re-queries L1 UTxO state every time (it reuses the cached value and lets you refresh if you want) #2726, plus more small fixes #2710 and a fix for flakey TUI tests #2708
• Merged a handful of simple fixes across smaller issues #2715
• Added deposit and recover transition tests and tidied up some others #2711
• CI and tooling: more nix caching by building derivations with -Werror to match nix flake check #2720, added etcd to the exes shell so smoke tests can run a system etcd #2722, and skipped the preprod-with-mithril path while it's offline #2723

What's next?​

• Add a test that probes how large a UTxO set we can actually (partially) fan out #2616
• Continue the still-open node-observing-unrelated-Heads deposit issue #2606
• Finish the user-friendly hydra-node configuration file #2581
• Accept PaymentExtendedKey (HD wallet keys) #2583

High-level Summary​

Big news is that we have merged the partial fanout work!. After many months of design and review, heads with large UTxO sets can now be fanned out in multiple steps, each verified on-chain via a BLS accumulator membership proof, with the chunk size determined dynamically by a binary search so each step packs in as many outputs as will fit. This removes the long-standing limit on UTxOs per head. Alongside that, the hydra-tui got a significant refactor, the test suite moved to tasty, and a handful of correctness fixes landed around cross-head event contamination and recovered deposits leaking back into L2.

What did the team achieve?​

• Merged partial fanout, including the on-chain validators, BLS accumulator membership proofs, and the PartialFanoutTx / FinalPartialFanoutTx transactions #2324
• Made the fanout chunk size fully dynamic via binary search over fitting tx size, replacing the hardcoded threshold #2617
• Significantly revised hydra-tui: pending-deposit recovery from Open and Closed/Final, dark/light theme toggle persisted to disk, event-history filter, tab navigation, and a per-tab rendering refactor #2590
• Switched the test suite from hspec to tasty #2620
• Validated headId in the aggregate function to prevent replayed events from a previous head corrupting the state of a newly opened one #2618
• Fixed a bug where a recovered incremental-commit deposit could reappear in the L2 UTxO after sideloading a snapshot, making the same UTxO spendable on both L1 and L2 #2630, #2629
• Made etcd writes more resilient to resolve a pumba-style network-partition test failure #2627
• Bumped rust-accumulator to fix musl build issues #2622
• Disabled nix store optimisation on CI to work around a macOS dyld issue #2626
• Sped up repeated linting and normal building, and added a small CLAUDE.md #2625
• Updated docs and changelog to reflect the partial fanout implementation, and documented the remaining large-UTxO limitation #2631

What's next?​

• Get a new release out!
• Add a test that probes how large a UTxO set we can actually (partially) fan out #2616
• Continue the still-open node-observing-unrelated-Heads deposit issue #2606
• Land the user-friendly hydra-node configuration file #2581
• Accept PaymentExtendedKey (HD wallet keys) #2583

High-level Summary​

This week the team shipped hydra-node 2.1.0 - a significant release that brings improved deposit security, the new SQLite-backed event store, a ~7% reduction in snapshot confirmation latency, and compatibility with cardano-node protocol version 12+. We encourage all operators to upgrade. Alongside the release, work continues on two long-standing items: partial fanout and a user-friendly configuration file for hydra-node to replace the current sprawl of command-line flags.

What did the team achieve?​

• Released hydra-node 2.1.0, which includes improved deposit security, the SQLite-backed event store, a ~7% reduction in snapshot confirmation latency, and compatibility with cardano-node protocol version 12+ release 2.1.0
• Upgraded to cardano-api 11.1 / cardano-node 11.0.1 to support protocol version 12+ #2607
• Switched from a lazy to a strict Map to reduce memory pressure during transaction processing #2599

What's next?​

• Continue work on partial fanout — choosing the UTxO set to fan out and final code review #2593, #2324, #2573
• Reduce disk usage in hydra-node #2601, #2600
• Investigate a node observing/persisting deposit events from unrelated Heads #2606
• User-friendly hydra-node configuration via config file #2581
• Accept PaymentExtendedKey (HD wallet keys) #2583

What did the team achieve?​

• Continued progress on partial fanout, including KZG trusted setup with G1 accumulator commitments #2582, #2324
• Potential performance improvement: switched from list to Seq for faster benchmark runs at higher tx counts #2597
• Fixed file-handle explosion ("Too many open files") by closing connections properly #2588
• Upgraded mithril compatibility and added a fallback so nix develop works on aarch64-darwin #2596, #2598
• Updated the pumba flake so it builds on modern mac hardware #2602

What's next?​

• Continue work on partial fanout, set up a secure CRS and perform final code-review! #2573
• Work on reducing disk usage #2601, #2600
• Support the upcoming Dijkstra Era #2495
• User-friendly hydra-node configuration via config file #2581
• Accept PaymentExtendedKey (HD wallet keys) #2583

What did the team achieve?​

• Continued progress on partial fanout #1667, #2538
• Final touches on the "Directly Open Heads" feature #1329
• Investigating a blocker when upgrading to cardano-api 10.21 #2520
• Working on more resilient snapshots #2551

What's next?​

• Merge approach for resilient snapshots #2551
• Merge "Directly Open Heads" #1329
• Get more structure in our benchmarks #2439
• Release 2.0.0!