Skip to main content

90 posts tagged with "hydra"

View All Tags

· One min read
Franco Testagrossa
Sebastian Nagel

High-level summary

This week, the Hydra team updated hydra-node to support cardano-node version 8.1.2, ensuring compatibility with the latest mainnet release. The team also participated in discussions about a "cardanonical" JSON schema and added it as a submodule to the project, contributing to improved data modeling and interoperability.

In terms of community engagement, the team successfully onboarded a new contributor, also participated in a RareEvo Twitter space, and continued preparations for the Hydra master-class.

What did the team achieve this week

  • Updated dependencies to support cardano-node 8.1.2 #1007
  • Engaged in discussions about a cardanonical json schema and add it as submodule to the project #1013
  • Onboarded a new contributor to the hydra project (@locallycompact)
  • Joined RareEvo twitter space and continued preparation of hydra master-class

What are the goals of next week

  • Update & streamline tutorial to work with latest version of hydra-node
  • Remove the internal commit functionality #954
  • Release 0.12.0

· 2 min read
Sebastian Nagel

High-level summary

This week, the Hydra team achieved notable progress in various aspects of the project. The team updated the use case section for auctions on the /unstable branch of the website, improving the understanding of Hydras applicability.

From the development side, the team successfully completed event-sourced persistence, a key enhancement in the projects architecture which improves off-chain transaction processing performance. They also added a submit-transaction endpoint to the API.

In addition to project-related progress, the team actively engaged in community reviews for several catalyst proposals related to Hydra and Mithril, contributing to the wider Cardano ecosystem.

Finally, the full report for the month of July was also published here.

What did the team achieve this week

  • Published the monthly report for July
  • Updated the use case section for auctions (published on /unstable branch)
  • Completed event sourced persistence #913
  • Added a submit-transaction endpoint to the API #966
  • Community reviews for several catalyst proposals related to Hydra and Mithril
  • Created a network testing tool (hydra-net) #1006

What are the goals of next week

  • Update hydra-node to work with cardano-node version 8.x
  • Remove the internal commit functionality
  • Release version 0.12.0
  • Update & streamline tutorial to work with latest version of hydra-node

· 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 projects 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.