92 posts tagged with "hydra"

High-level Summary​

This week, the Hydra team conducted yearly roadmapping sessions, introduced a breaking API change to eliminate JSON encoding of transactions (refer to issue #1213 for details), completed off-chain logic for incremental decommits through, and implemented a hydra-explorer backend.

What did the team achieve this week​

• Conducted yearly roadmapping sessions
• Merged a breaking API change to drop JSON encoding of transactions #1213 - contact us if you were relying on this.
• Completed off-chain logic for incremental decommits #1223
• Implemented a hydra-explorer backend #1235

What are the goals of next week​

• Publish the monthly report
• Prepare PRs for hydra clients to switch to CBOR due to the changed API (see above)
• Enhance the model testing framework to cover close/contest (needed to fix a bug and incremental decommit development)
• Fix new bugs (all minors) and finish things before starting new

High-level Summary​

The team made good progress this week, with the release of version 0.15.0 marking a milestone, along with the monthly review including both Mithril and Hydra work. We addressed issues in smoke tests and website publishing workflows, ensuring a more robust development environment, and along the way included more "dogfooding" through the use of Mithril to synchronize nodes in smoke tests.

What did the team achieve this week​

• Release of Version 0.15.0. This release enhances the overall stability and functionality of our product.
• Monthly Review and Community Demos
• Smoke Tests and Website Publishing Workflow Fixes: #1246
  • Resolved glitches in the website publishing workflows, enhancing the efficiency of our deployment processes.
• Integration of Mithril for Smoke Test Synchronization: #1252
• Polishing of Hydra-Chess v0.1.0: #1237
  • Worked on polishing hydra-chess v0.1.0, treating it as an example application running on Hydra. This not only demonstrates the capabilities of our platform but also aims at providing a reference for future Hydra developers.

What are the goals of next week​

• Merge Off-Chain Protocol Logic for incremental decommits
• Initiate work on the on-chain portion of incremental decommits
• Merge CBOR API Change #1240
• Troubleshoot Dangling Fanout Issue #1260

High-level summary​

This week, the Hydra team improved Github actions workflows, addressed protocol parameter schema consistency in hydra-node, and made enhancements to log schema tests. They created an Architectural Decision Record (ADR) for Cardano transactions serialization in APIs, moved the hydra-chess project to a dedicated repository, and resolved a bug in quickcheck-dynamic and model tests.

There will be the monthly review meeting with demos on Hydra, Mithril and related projects. If this sounds interesting, join us in Google Meet https://meet.google.com/udc-zgyw-agd next week, January 19 2024 at 17:30 UTC.

What did the team achieve this week​

• Github actions improvements and small fixes to the smoke tests #1242, #1233
• Fixed protocol parameter schema consistency around hydra-node #1234
• Log schema tests improvements and fixes #1244
• Created ADR about Cardano transactions serialisation in our APIs #1215
• Moved hydra-chess #1237 to a dedicated cardano-scaling organisation repository https://github.com/cardano-scaling/hydra-chess
• Identified bug on quickcheck-dynamic / our model tests #1239

What are the goals of next week​

• Monthly review meeting (January 19, 17:30 UTC) including several demos (from team and contributors)
• Do release 0.15.0
• Improve quickcheck-dynamic model to be more robust and cover more behaviour.
• Draft POC about backend for a hydra-explorer that can track all heads on-chain.

High-level summary​

In between the end-of-year holidays, the Hydra team completed the implementation of the Conway support feature, fixed a minor bug that was hindering tests from running on MacOS, and addressed a regression in the protocol-parameter formats used by the hydra-node. They also worked on off-chain code for incremental decommits, specifically focusing on transaction creation. Furthermore, they conducted a spike on implementing a Chess game using Hydra, with an experience report provided.

What did the team achieve this week​

• Fixed a regression on protocol-parameter formats used by the hydra-node #1226
• Fixed a minor bug prohibiting tests running on MacOS #1218
• Complete conway support feature #1227
• Transaction creation off-chain code for incremental decommits #1218
• First spike on implementing a Chess game on Hydra report, related to: #1098

What are the goals of next week​

• Fully resolve protocol parameter misalignment #1234
• Cut a release 0.15.0 to ship offline-mode and conway support
• Prepare demo for conway support
• Complete transaction creation and observation for incremental decommits
• Backend for a hydra-explorer that can track all heads on-chain

High-level summary​

This week, the Hydra team made significant progress, implementing an offline mode with associated refactoring. They enhanced user experience by detecting incompatible eras in hydra-node. Protocol changes were implemented for incremental decommits, addressing off-chain logic. Additionally, the team contributed fixes to cardano-ledger and coordinated with the Eternl team on enabling committing into a head from their wallet.

What did the team achieve this week​

• Offline mode implementation #1118 and refactoring #1222
• Detect incompatible era in hydra-node and provide better UX #1216
• Implemented protocol changes for incremental decommits (off-chain logic) #1057
• Contributed fixes to cardano-ledger#3949 and #3953
• Synced up with the Eternl team on enabling committing into a head from their wallet

What are the goals of next week​

• Maybe cut a release 0.15.0 to ship offline-mode and unsupported era UX
• Full conway support in hydra-node
• Transaction creation and observation for incremental decommits