Skip to main content

88 posts tagged with "hydra"

View All Tags

· 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

· 2 min read
Noon van der Silk

High-level summary​

We have put together a nice base of network-resiliance tests to build from, and already started exploring potential improvements to our networking. We've made good progress on incremental commits, by way of deposits, and settled on an approach to tackle a few of the known problems related to "stuck funds", and finally we completed some work related to usability of new functionality and documentation in our changelog. Up next we will switch the ledger to Conway and prepare a release, and we will continue working on incremental commits.

What did the team achieve?​

  • Implemented initial suite of network-resiliance tests #1532
  • We explored persistence as an improvement to our networking layer #1593
  • Incremental commits (coming in a 0.19 release) have pivoted to a deposit-based scheme based on open discussions (thanks @GeorgeFlerovsky!)
  • Settled on Partial Fanout as a good solution to a few known problems
  • Split out some functionality into a new library, hydra-tx, to eventually support user workflows around deposit/recover transactions #1587
  • Golden tests to help track breaking data changes in the changelog #1554

What's next?​

  • Switch ledger to Conway #1178
  • Update our networking page with the findings from our resiliance work
  • Fix search on the docs #1556
  • Release 0.19.0 with L2 Ledger in Conway
  • Continued work on incremental commit #199

· One min read
Noon van der Silk

High-level summary​

Firstly, we had a succesful launch of the Hydra Doom project at RareEvo! Coinciding with this we updated our landing page, and released a minor version with a small, but important, bugfix. In the next period we will continue our focus on incremental commits, network testing, and general API compatibility.

What did the team achieve?​

What's next?​

  • Test more network resiliance scenarios #1575
  • Continued work on incremental commit #199
  • Switch ledger to Conway #1178
  • Investigate how to be compatible with cardanonical #1577