Skip to main content

103 posts tagged with "hydra"

View All Tags

· 2 min read
Sebastian Nagel

High-level summary​

During this week, the Hydra team achieved significant progress in various areas. They conducted the monthly review meeting for July, which continously ensures transparent communication and project evaluation. The team migrated the core logic of the node to an event-sourced architecture and incremental writes of events to persistence, enhancing the project’s performance and maintainability. Furthermore, the team added the ability to read protocol parameters via the API and fixed the CI workflows to support pull requests from forks of external contributors, streamlining the development process for community involvement.

What did the team achieve this week​

  • Held the monthly review meeting for July (recording)
  • Migrate the core logic of the node to an event-sourced architecture #999
  • Updated persistence to faster incremental writes of events #1000
  • Added ability to read protocol parameters via API #735
  • Fix CI workflows to support pull requests from forks of external contributors #993
  • Updated to GHC 9.2.8 #1005
  • Prepared an updated use cases section on https://hydra.family (published with next release)

What are the goals of next week​

  • Publish monthly report
  • Complete user transaction submission work #966
  • Remove commit from internal wallet (deprecated) #954

· One min read
Sebastian Nagel

High-level summary​

This week, the Hydra team updated the specification to align with recent off-chain protocol changes, completed refactoring the snapshot emission in preparation for event-sourced protocol logic, and updated to GHC 9.2.7, resulting in improved compile times and slightly smaller Plutus scripts.

What did the team achieve this week​

  • Updated the specification to match the recent off-chain protocol changes to complete #728
  • Refactored the snapshot emission logic in preparation for event sourced protocol logic.
  • Updated to GHC 9.2.7, which led to improved compile times and slightly smaller plutus scripts.

What are the goals of next week​

  • Monthly review meeting next wednesday and July report
  • Reflect latest information onto our roadmap.
  • Actual implemention of event-sourced persistence #913.
  • Update the use cases section on https://hydra.family
  • Remove deprecated internal commit #954.

· One min read
Franco Testagrossa
Sasha Bogicevic

High-level summary​

This week the team focused on exploring the event sourced persistence in order to improve hydra-node performance. Because of this work the team noticed we need to refactor the emit snapshot emission logic and update the spec in the light of new changes. They also took the time to revisit their goals and product plans for the next quarter as well as doing some security fixes related to multisignatures.

What did the team achieve this week​

  • Finished spike about performance improvements of event sourced persistence #963.
  • Refactor snapshot emission in protocol logic.
  • Revisited our roadmap and goals.
  • Prepared and conducated a learning session on lean-waste.
  • Improve security of multi-signature checks, see this Github security advisory.
  • Implemented a cache friendly way to version our binaries #962.

What are the goals of next week​

  • Implement Event sourced persistence #913.
  • Remove deprecated internal commit #954 and close #728.

· One min read
Franco Testagrossa
Sasha Bogicevic

High-level summary​

This week the Hydra team accomplished some nice progress. They secured the network layer further by implementing authentication of the messages between the peers in the Head protocol. In the process they also managed to separate HeartBeat messages from the protocol ones which somewhat improved the quality of code in Hydra. The team also finished work related to sending only transaction ids in ReqSn messages, fixed an issue in the smoke tests, and improved benchmark publishing on the website.

What did the team achieve this week​

What are the goals of next week​

  • Spike on performance improvements of event sourced persistence #913
  • Add new endpoint for submitting client transactions
  • Remove commit from internal wallet

· One min read
Sebastian Nagel

High-level summary​

This week, the Hydra team wrote and published the monthly report for June, implemented the end-to-end functionality for external commits, and tested it on the preview environment. They also listed Hydra as a tool on the Cardano developer portal, providing more visibility for the project. The team clarified the path forward for L2 protocol improvements and explored an alternative CI approach using cabal instead of nix. Additionally, they released version 0.11.0, marking another milestone in the project’s development.

What did the team achieve this week​

  • Written and published the monthly report for June
  • Implemented external commits end-to-end incl. tested it on preview #215
  • Listed Hydra as a tool on cardano developer portal
  • Cleared up path forward on L2 protocol improvements #728
  • Established an alternative CI using more cabal tools #923
  • Release version 0.11.0

What are the goals of next week​

  • Spike on performance improvements of event sourced persistence #913
  • Complete ReqSn only sends transaction ids #728
  • Groom and plan last items for 0.12.0 (remove internal commit)
  • Improve reliability of benchmarks