111 posts tagged with "hydra"

High-level summary​

This week, the Hydra team fixed the gen-hydra-keys command to avoid overwriting existing keys, and resolved issues related to the rewritten hydra-tui. They also worked on a \"dirt road\" implementation for the \"Ignored init tx\" notification, improving the robustness of the system.

The team finalized preparations for the Cardano Summit presentation, including implementation of the hydra-poll example DApp.

If you happen to read this and attend the Summit in Dubai, make sure to check out our Masterclass about \"Developing Hydra + Mithril for Scaling Cardano\" on Friday, November 3 at 14:00-15:30 local time in the \"Al Dar\" room!

What did the team achieve this week​

• Fix gen-hydra-keys command to not overwrite existing keys #1136
• Fixed the rewritten hydra-tui#1113#1137
• Finalized cardano summit preparation #1109
• Implemented the hydra-poll example DApp link to repository
• Dirt road implementation for \"Ignored init tx\" notification #529

What are the goals of next week​

• Attend cardano summit and deliver presentation
• Clarify / close user created issues
• Build aarch64-darwin binaries in CI

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.
  • #1127
  • #1120
• 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.

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.

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

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​

• Introduce reliability network layer [#1074] (https://github.com/input-output-hk/hydra/pull/1074)
• Refactor the vCommit validator in Aiken #1072