Skip to main content

109 posts tagged with "hydra"

View All Tags

· One min read
Daniel Firth

High-level Summary​

This week, the Hydra team worked on forward compatibility for Conway support, deployed the hydra explorer tool, and improved the model based testing to support more actions (Fanout and Rollbacks).

What did the team achieve this week​

  • Addressed flakyness in two types of integration tests
  • Fixed our tooling (HLS 2.6 on GHC 9.6.4)
  • Fixed configuration of running head in preview
  • Added Fanout and Rollbacks to our Model basd test suite #1296
  • Deployed the hydra explorer to http://explorer.hydra.family:9090/heads (url will change a bit more)
  • Updated smoke test to run sanchonet

What are the goals of next week​

  • Fix the fanout after contest bug
  • Specify the on-chain validators for incremental decommits
  • Complete smoke tests on sanchonet

· One min read
Sebastian Nagel

High-level Summary​

This week, the Hydra team authored and published the monthly report for January 2024, enhanced user feedback for failed commands, updated cardano-api dependency and GHC to newer versions, re-opened their persistent head in preparation for the hard-fork, extended the model-based testing suite to cover the closing of heads, fixed a bug in io-sim, and contributed to cardano-node.

What did the team achieve this week​

What are the goals of next week​

  • Fix the fanout after contest bug #1260
  • Run Hydra smoke tests on sanchonet #1257
  • Specify the on-chain validators for incremental decommits #1057
  • Have the explorer hosted #696
  • Prepare PRs for dropped JSON instances from API #1213

· One min read
Sebastian Nagel

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

· 2 min read
Arnaud Bailly

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

· 2 min read
Sebastian Nagel

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.