106 posts tagged with "hydra"

High-level summary​

This week, the Hydra team released version 0.12.0, a significant update that brings support for cardano-node 8.1.2, along with performance enhancements and various API improvements. Additionally, the team successfully onboarded a new contributor who is now actively participating in operating a Hydra Head. They took part in a meeting of the Intersect open source committee and prepared the Hydra master-class for RareEvo, an educational initiative for the community.

If you happen to be at RareEvo, register for the Hydra master-class using this form. We hope to make it possible to follow along on-line as well and will announce details on the Hydra announcements channel on the IOG discord server.

What did the team achieve this week​

• Released version 0.12.0 which adds support for cardano-node 8.1.2, performance and several API improvements. Release notes
• Replaced commit via websocket with external draft + submit. #954
• Onboarded new contributor to the point where he actively participates in operating a Head now.
• Joined a first meeting of the Intersect open source committee
• Prepared the Hydra master-class for RareEvo.

What are the goals of next week​

• Monthly review meeting
• Run the Hydra master-class at RareEvo!
• Updated Hydra tutorial including Mithril and re-record demo/tutorial stuff
• Clear out red bin items (technical debt)
• Groom network resilience and explorer features

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

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 Hydra’s applicability.

From the development side, the team successfully completed event-sourced persistence, a key enhancement in the project’s 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

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

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.