Skip to main content

90 posts tagged with "hydra"

View All Tags

· One min read
Noon van der Silk

High-level summary​

This last few weeks have been focused on incremental commits, re-writing more validators in Aiken, and the associated changes that have come about as the our scripts sizes increase. We continue along on prioritising incremental commits and a 0.20.0 release, as well as some repository cleanup and additional functionality based on user requests.

What did the team achieve?​

  • Benchmarked memory limits on number of Txns #1724
  • Re-wrote Initial validators script to Aiken #1734
  • Bump to PlutusV3 #1734
  • Continued progress on incremental commits #199

What's next?​

  • Move hydra-explorer out of the mono-repo #1716
  • Add ability to filter the API by UTxO address #1719
  • Continued work on incremental commits #199
  • Investigate options for customised ledger in a Hydra Head #1727
  • Plan the 0.20.0 release
  • Continue to support Hydra Doom

· One min read
Noon van der Silk

High-level summary​

This last few weeks have seen us spend some time in internal planning, focus hard on incremental commits. We've made good progress on the on-chain validators and associated tests; we continue on with this work. We are also beginning to tackle partial fanout by making some small steps based on the ongoing work of Thomas and others.

What did the team achieve?​

  • Small cleanup as part of our first group knowledge-sharing session #1714
  • Progress on the validators and tests for incremental commits #1715, #1664

What's next?​

  • Continued work on incremental commits #199
  • Begin work on partial fanout #1468
  • Investigate options for customised ledger in a Hydra Head #1727
  • Continue to support Hydra Doom
  • Continue to plan the 0.20.0 release

· 2 min read
Noon van der Silk

High-level summary​

The last few weeks have seen a solid amount of work and changes to the user-facing side of Hydra; namely great progress on incremental commits and using Aiken for our commit validator which has yielded size/cost savings. This has also allowed us to support PlutusV3 validators and keep up to date with the cardano-api. We also made a breaking change (improvement) to the server output SnapshotConfirmed to make it easier to work with signed snapshots. Finally, we made good progress on blockfrost support by adding an option to follow the chain via blockfrost, instead of through a cardano-node. Next up we continue our focus on incremental commits and general improvements, while planning the next release.

What did the team achieve?​

  • Added the raw CBOR datum in transaction outputs #1543
  • Used Aiken for commit validator #1680
  • Updated to cardano-api 9.4 #1706
  • Implemented the off-chain user journey for incremental commits #1522
  • Documentation on the incremental commits feature #1704
  • Some cleanup of unused modules and functions
  • Full transaction information in SnapshotConfirmed event #1685
  • Added blockfrost mode to hydra-chain-observer #1631

What's next?​

  • Continued work on incremental commits #199
  • Improvements to memory usage #1618
  • DevEx improvements to split out components of the hydra monorepo
  • Start to plan the 0.20.0 release

· One min read
Noon van der Silk

High-level summary​

This month we continued our work on incremental commits and blockfrost. We spent a bit of time conducting some experiments in ways to potentially improve our CI build times, and completed an encouraging spike around using Raft (via etcd) for our networking layer, among some other minor cleanups and version bumps. Up next We will continue on with incremental commits and blockfrost, as well as some items coming out of the Doom work, to improve our memory efficiency, and finally we will aim to move to PlutusV3!

What did the team achieve?​

  • Investigated CI improvements #1647, #1615
  • Updated networking documentation to reflect assumptions and present state #1649
  • Good progress on incremental commits #1522
  • Good progress on blockfrost integration in the Hydra node #1631
  • Update to use cardano-node 9.2.0 #1651
  • Investigated Raft for networking #1591
  • Grooming work on the partial fanout feature #1468

What's next?​

  • Continued work on incremental commit #199
  • Continued work on Blockfrost integration #1305
  • Improvements to memory usage #1618
  • Work towards moving to PlutusV3 #1665
  • CBOR datum on transaction outputs #1543

· 2 min read
Noon van der Silk

High-level summary​

We released 0.19.0 of the hydra-node, where the ledger has been upgraded to Conway, while still maintaining compatibility with Babbage transactions. We made some small improvements to the TUI, and did some investigations into a "Head-In-Head"-style operation of hydra, where one Head can be used to launch another. This isn't supported officially yet, but we will be considering it in the future. Up next we will continue on incremental commits, work towards a Blockfrost chain layer, and continue investigations into our core networking, and finally spend some time planning some potential upcoming Hydra Doom-related work.

What did the team achieve?​

  • Switched ledger to Conway #1178
  • Remain compatible with Babbage transactions #1608
  • Manual address entry in the TUI #1607
  • Completed an investigation into "Two-phase commit" for reliability #1597
  • Hydra "Head-In-Head" Spike #1590
  • Fixed Aloglia search index on docs site #1556
  • Updated to use cardano-node 9.1.1 and mithril 2430 #1630
  • Added "HeadId" into the "Greetings" message #1557
  • Change network semantics to broadcast to everyone #1624
  • Released 0.19.0 with ledger in Conway, among other fixes

What's next?​

  • Continued work on incremental commit #199
  • Continued work on Blockfrost integration #1305
  • Investigate raft for consensus networking #1591
  • Work and planning for more Hydra Doom-related activity