Deploying to gh-pages from @ cardano-scaling/hydra@cfe89e0836f14df84c94d0ea0b19ed3fa0a53286 🚀
Home /
Input Output /
hydra-poc
Apr 29, 1-2 PM (0)
Apr 29, 2-3 PM (0)
Apr 29, 3-4 PM (0)
Apr 29, 4-5 PM (1)
Apr 29, 5-6 PM (2)
Apr 29, 6-7 PM (1)
Apr 29, 7-8 PM (0)
Apr 29, 8-9 PM (0)
Apr 29, 9-10 PM (0)
Apr 29, 10-11 PM (0)
Apr 29, 11-12 AM (0)
Apr 30, 12-1 AM (0)
Apr 30, 1-2 AM (0)
Apr 30, 2-3 AM (0)
Apr 30, 3-4 AM (0)
Apr 30, 4-5 AM (1)
Apr 30, 5-6 AM (2)
Apr 30, 6-7 AM (0)
Apr 30, 7-8 AM (0)
Apr 30, 8-9 AM (0)
Apr 30, 9-10 AM (0)
Apr 30, 10-11 AM (0)
Apr 30, 11-12 PM (1)
Apr 30, 12-1 PM (0)
Apr 30, 1-2 PM (0)
Apr 30, 2-3 PM (0)
Apr 30, 3-4 PM (0)
Apr 30, 4-5 PM (0)
Apr 30, 5-6 PM (0)
Apr 30, 6-7 PM (0)
Apr 30, 7-8 PM (0)
Apr 30, 8-9 PM (0)
Apr 30, 9-10 PM (0)
Apr 30, 10-11 PM (0)
Apr 30, 11-12 AM (0)
May 01, 12-1 AM (0)
May 01, 1-2 AM (0)
May 01, 2-3 AM (0)
May 01, 3-4 AM (0)
May 01, 4-5 AM (0)
May 01, 5-6 AM (0)
May 01, 6-7 AM (0)
May 01, 7-8 AM (0)
May 01, 8-9 AM (0)
May 01, 9-10 AM (0)
May 01, 10-11 AM (0)
May 01, 11-12 PM (0)
May 01, 12-1 PM (0)
May 01, 1-2 PM (0)
May 01, 2-3 PM (0)
May 01, 3-4 PM (0)
May 01, 4-5 PM (0)
May 01, 5-6 PM (0)
May 01, 6-7 PM (0)
May 01, 7-8 PM (0)
May 01, 8-9 PM (0)
May 01, 9-10 PM (0)
May 01, 10-11 PM (0)
May 01, 11-12 AM (0)
May 02, 12-1 AM (0)
May 02, 1-2 AM (0)
May 02, 2-3 AM (0)
May 02, 3-4 AM (0)
May 02, 4-5 AM (0)
May 02, 5-6 AM (0)
May 02, 6-7 AM (0)
May 02, 7-8 AM (0)
May 02, 8-9 AM (0)
May 02, 9-10 AM (0)
May 02, 10-11 AM (0)
May 02, 11-12 PM (0)
May 02, 12-1 PM (0)
May 02, 1-2 PM (0)
May 02, 2-3 PM (0)
May 02, 3-4 PM (0)
May 02, 4-5 PM (0)
May 02, 5-6 PM (0)
May 02, 6-7 PM (0)
May 02, 7-8 PM (0)
May 02, 8-9 PM (0)
May 02, 9-10 PM (0)
May 02, 10-11 PM (0)
May 02, 11-12 AM (0)
May 03, 12-1 AM (0)
May 03, 1-2 AM (0)
May 03, 2-3 AM (0)
May 03, 3-4 AM (0)
May 03, 4-5 AM (0)
May 03, 5-6 AM (0)
May 03, 6-7 AM (0)
May 03, 7-8 AM (0)
May 03, 8-9 AM (0)
May 03, 9-10 AM (0)
May 03, 10-11 AM (0)
May 03, 11-12 PM (0)
May 03, 12-1 PM (0)
May 03, 1-2 PM (0)
May 03, 2-3 PM (0)
May 03, 3-4 PM (0)
May 03, 4-5 PM (0)
May 03, 5-6 PM (0)
May 03, 6-7 PM (0)
May 03, 7-8 PM (0)
May 03, 8-9 PM (0)
May 03, 9-10 PM (0)
May 03, 10-11 PM (0)
May 03, 11-12 AM (0)
May 04, 12-1 AM (0)
May 04, 1-2 AM (0)
May 04, 2-3 AM (0)
May 04, 3-4 AM (0)
May 04, 4-5 AM (0)
May 04, 5-6 AM (0)
May 04, 6-7 AM (0)
May 04, 7-8 AM (0)
May 04, 8-9 AM (0)
May 04, 9-10 AM (0)
May 04, 10-11 AM (0)
May 04, 11-12 PM (0)
May 04, 12-1 PM (0)
May 04, 1-2 PM (0)
May 04, 2-3 PM (2)
May 04, 3-4 PM (0)
May 04, 4-5 PM (0)
May 04, 5-6 PM (0)
May 04, 6-7 PM (0)
May 04, 7-8 PM (0)
May 04, 8-9 PM (0)
May 04, 9-10 PM (0)
May 04, 10-11 PM (0)
May 04, 11-12 AM (0)
May 05, 12-1 AM (0)
May 05, 1-2 AM (0)
May 05, 2-3 AM (0)
May 05, 3-4 AM (0)
May 05, 4-5 AM (0)
May 05, 5-6 AM (0)
May 05, 6-7 AM (0)
May 05, 7-8 AM (0)
May 05, 8-9 AM (4)
May 05, 9-10 AM (0)
May 05, 10-11 AM (0)
May 05, 11-12 PM (2)
May 05, 12-1 PM (1)
May 05, 1-2 PM (1)
May 05, 2-3 PM (0)
May 05, 3-4 PM (0)
May 05, 4-5 PM (0)
May 05, 5-6 PM (1)
May 05, 6-7 PM (0)
May 05, 7-8 PM (0)
May 05, 8-9 PM (0)
May 05, 9-10 PM (2)
May 05, 10-11 PM (0)
May 05, 11-12 AM (0)
May 06, 12-1 AM (0)
May 06, 1-2 AM (0)
May 06, 2-3 AM (0)
May 06, 3-4 AM (0)
May 06, 4-5 AM (0)
May 06, 5-6 AM (0)
May 06, 6-7 AM (1)
May 06, 7-8 AM (1)
May 06, 8-9 AM (1)
May 06, 9-10 AM (1)
May 06, 10-11 AM (6)
May 06, 11-12 PM (2)
May 06, 12-1 PM (0)
May 06, 1-2 PM (0)
33 commits this week
Apr 29, 2026
-
May 06, 2026
Seq instead of list (#2597)
Uses the `Seq` type instead of a `list`, which makes it a little faster, on my computer, in some circumstances: ### Scenario 1 Before (`--number-of-txs 300`): ``` > cabal run bench-e2e -- datasets --number-of-txs 300 --output-directory /tmp/bench-before-300 Average confirmation time (ms): 17.457022511 P99: 29.295330019999994ms P95: 22.807852549999993ms P50: 16.398083ms ``` 41s clock time as measured by my terminal. After (`--number-of-txs 300`): ``` > cabal run bench-e2e -- datasets --number-of-txs 300 --output-directory /tmp/bench-after-300 Average confirmation time (ms): 17.389314338 P99: 27.240633599999995ms P95: 22.911740449999996ms P50: 16.474119ms ``` 40s clock time. _Conclusion_: Almost no difference. ### Scenario 2 Before (`--number-of-txs 3000`): ``` > cabal run bench-e2e -- datasets --number-of-txs 3000 --output-directory /tmp/bench-before-3000 Average confirmation time (ms): 40.479327468 P99: 57.356654989999996ms P95: 52.25816309999999ms P50: 40.995065ms ``` 2min 37s clock time. After (`--number-of-txs 3000`): ``` > cabal run bench-e2e -- datasets --number-of-txs 3000 --output-directory /tmp/bench-after-3000 Average confirmation time (ms): 17.389314338 P99: 27.240633599999995ms P95: 22.911740449999996ms P50: 16.474119ms ``` 1min 25s clock time. _Conclusion_: Roughly twice as fast! -- Edit: <img width="1200" height="900" alt="image" src="https://github.com/user-attachments/assets/c8f88948-acee-4f90-9fa3-4f46515f6119" />
Remove mkTwoPartyConfigs
Signed-off-by: Sasha Bogicevic <[email protected]>
Remove RecordWildCards
Signed-off-by: Sasha Bogicevic <[email protected]>
Add HydraNodeConfig and update withHydraNode to use it
Introduce HydraNodeConfig record type and smart constructors (mkSoloConfig, mkTwoPartyConfigs, mkThreePartyConfigs) to replace positional arguments in withHydraNode, withHydraNodeCatchingUp, and withUnsyncedHydraNode. Update all call sites in Scenarios, EndToEndSpec, ChainObserverSpec, TUISpec, and Bench/EndToEnd accordingly. Signed-off-by: Sasha Bogicevic <[email protected]>
Merge branch 'master' into vrom911/strict-map
Merge branch 'master' into minor-tx-speedups
CHange the fanout chunk size limit
Use EIP-4844 KZG trusted setup with G1 accumulator commitments
Deploying to gh-pages from @ cardano-scaling/hydra@fe5f29fa10ede3b4d9e16bee21643b7d65d2d62a 🚀
Fall back to mithril package when mithril-client-cli is unavailable (#2598)
The `mithri`l `2617.0` release switched all nodes to static musl builds. As a side effect, mithril-client-cli is no longer exposed as a standalone Nix package for non-Linux platforms. It only exists under `packages.x86_64-linux`. This broke nix develop on `aarch64-darwin`. The one real downside of current solution is that the fallback pulls in the entire mithril package (aggregator, signer, end-to-end tooling, etc.) just to get `mithril-client`. <!-- Describe your change here --> --- <!-- Consider each and tick it off one way or the other --> * [ ] CHANGELOG updated or not needed * [ ] Documentation updated or not needed * [ ] Haddocks updated or not needed * [ ] No new TODOs introduced or explained herafter --------- Co-authored-by: Noon <[email protected]>
Changelog entry
Signed-off-by: Sasha Bogicevic <[email protected]>
Remove redundant newLocalUTxO from StateChanged events
newLocalUTxO was carried on TransactionAppliedToLocalUTxO, SnapshotRequested, and DecommitRecorded but is fully derivable from the event's tx (or snapshot fields) plus current state. Aggregate now recomputes it via a new IsTx method `applyTxTo` (pure UTxO arithmetic, no ledger validation). Removes O(N²) on-disk growth on Growing-UTxO workloads. JSON format is forward/backward compatible — old event stores still parse. Measured (bench-e2e --utxo-size Growing -n 2000): - hydra.db: 1.6 GB → 526 MB (-67%) - hydra-node-0.log: 2.1 GB → 1.1 GB (-48%) - avg confirm: 92.9 ms → 84.1 ms (-9%) Signed-off-by: Sasha Bogicevic <[email protected]>