Skip to main content

90 posts tagged with "hydra"

View All Tags

· One min read
Franco Testagrossa

High-level summary​

This week, the Hydra team mainly focused on preparing a masterclass and workshop for #CardanoSummit2023.

In addition, they improved the Hydra node API's submit-transaction endpoint to accept three different encoding types: Base16 encoded CBOR string, TextEnvelope type, and JSON. This improvement offers users greater flexibility and ease of interaction with the API.

Finally, the team has followed up on the TUI brick upgrade to version 1.10. This effort has resulted in addressing minor details and enhancing the overall user experience with the TUI.

What did the team achieve this week​

  • Prepare presentation and workshop for Cardano Summit.
  • More TUI fixes and improvements.
  • Upgrade GHC from 9.2.8 -> 9.6.2 #1105
  • Solved user issue related to submitting transactions in cbor format #1111.
  • Fix hydraw connection issue making it more stable #1121.

What are the goals of next week​

  • Work on hydra-poll dApp for Cardano summit.
  • Start the work on packaging hydra-node and related services.

· One min read
Franco Testagrossa

High-level summary​

This week, the Hydra team's primary focus was on finalizing the new network resilience layer. This involved adding persistency to ensure data integrity.

They also completed the exploration of potentially moving the Plutus validator scripts to Aiken.

Additionally, the team dedicated some attention to our TUI by upgrading the Brick framework. They also undertook a comprehensive refactoring of the project's structure and addressed various bug fixes. These efforts are aimed at enhancing the overall user experience of our project.

What did the team achieve this week​

  • Network Resilience Persistence (#1101)[https://github.com/input-output-hk/hydra/pull/1101].
  • Upgrade brick on TUI (#1103)[https://github.com/input-output-hk/hydra/pull/1103].
  • Aiken commit validator translation (#1072)[https://github.com/input-output-hk/hydra/pull/1072].
  • Fixed some bugs in our TUI client.

What are the goals of next week​

  • Prepare presentation and workshop for Cardano Summit.
  • Work on hydra-poll dApp for Cardano summit.
  • Start the work on packaging hydra-node and related services.

· One min read
Franco Testagrossa

High-level summary​

This week, the Hydra team released version 0.13.0, which includes fixes and extensions for state persistency and the ability to draft a commit transaction using inline datums.

The team also delivered the first version of the network resilience layer, significantly increasing head availability.

Additionally, they have been providing support to several funded Catalyst projects that want to build on Hydra.

Last but not least, they updated and published security policy and vulnerability disclosure policy reports on how to handle security vulnerabilities within Hydra.

What did the team achieve this week​

  • Release 0.13.0
  • Published vulnerability reports #1088
  • Merged network resilience work part I #1074
  • Planning for Cardano Summit participation
  • Discussions with funded Catalyst projects wanting to build on Hydra for support
  • Merged typos fix PR from @omahs #1095

What are the goals of next week​

  • Complete Aiken commit validator script #1072
  • Complete Kupo integration #1078
  • Brick upgrade on TUI #1103
  • Clean backlog
  • Prepare and rehearse demo and talk for Cardano Summit

· One min read
Franco Testagrossa

High-level summary​

This week, the Hydra team mainly focused on having a working new reliability network layer; and specified its expected behavior in a new ADR.

They also revisited the security policy and vulnerability disclosure policy on how to handle security vulnerability within Hydra, and in particular how to handle so-called "Silent fixes".

What did the team achieve this week​

  • Updated security policy and vulnerability disclosure policy #1088
  • Adr/network reliability #1082

What are the goals of next week​

· 2 min read
Sebastian Nagel

High-level summary​

This week, the Hydra team conducted the monthly review meeting in collaboration with Mithril, enhancing project coordination.

The team improved the gen-hydra-key node command for smoother usability and identified concrete steps to enhance network resiliency in feature items #188, #1080, and #1079. Additionally, they contributed the aiken-mode editor integration to the aiken-lang organization, updated dependencies to utilize cardano-api 8.20, and published the Hydra security advisory CVE-2023-42806 with a workaround available for users.

These efforts demonstrate the team\'s commitment to project improvement, security, and open-source community collaboration.

What did the team achieve this week​

  • Conducted the monthly review meeting together with Mithril
  • Improved gen-hydra-key node command #1077
  • Established a clear plan to improve resiliency of network and manifested feature items #188, #1080 and #1079
  • Moved aiken-mode (created by SN) to aiken-lang organization
  • Updated dependencies to using cardano-api 8.20 #1075
  • Published security advisory CVE-2023-42806 (workaround available)

What are the goals of next week​

  • Write-up the monthly report for September
  • Finish "network resilience to disconnects" #188
  • Finish kupo integration with hydra #1078
  • Discuss and decide on using aiken or not
  • Address the published security advisory CVE-2023-42806 (to not require workaround)
  • Ideally, release 0.13.0