Skip to main content

92 posts tagged with "hydra"

View All Tags

· 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

· One min read
Sasha Bogicevic
Sebastian Nagel

High-level summary

This week, most of the Hydra team was attending a cardano scaling workshop in Nantes, France. They used this oportunity to meet fellow mithril team and spend some time together to hack on some code and, as always, reflect on the past work and find optimal path forward for both projects. They also fixed a bug that caused hydra-node to crash when querying L1, worked on a new network resillience proof-of-concept and accepted a new ADR related to stateless transaction observation.

What did the team achieve this week

  • Cardano scaling workshop with members of hydra and mithril teams
  • Accepted user contribution for possible new use-case #1048
  • Fix for the hydra-node crash related to internal wallet query #1053
  • Collected experimental CI findings #1070
  • Propose first POC for the network resilience #1074

What are the goals of next week

  • Monthly review meeting & report including updates from Mithril
  • Review POC and discuss our options for the network resilience
  • Update cardano-api to version 8.20
  • Address TODOs on aiken commit validator #1072
  • Complete hydra-support in kupo kupo#117

· 2 min read
Sebastian Nagel

High-level summary

This week, the Hydra team improved the commit process with support for inline datums. They simplified the chain layer by refactoring how the chain state is persisted. Updates to the Hydra tutorial were completed, including CI workflows to keep it up-to-date. The team engaged in discussions with researchers about incremental commits & decommits, and drafted an architectural decision record for a resource-based API. They also explored simpler solutions for the upcoming network resilience feature.

What did the team achieve this week

  • Support InlineScriptDatum in commit #1043
  • Refactored chain state persistency #1049
  • Completed tutorial updates (by adding CI and some cleanup) #997
  • Intersect Open Source committee meeting
  • Experimented with various models to better express the \"Network resilience problem\" to find a KISS solution for #188
  • Drafted and discussed incremental de-/commit features within team and with researchers #199 and #1057
  • Created ADR for a resource based overhaul of the API #1028

What are the goals of next week

  • Meetup of Hydra & Mithril contributors in Nantes, France
  • Integrated cardano-api 8.15 to have GHC 9.6 support
  • A clear design for incremental commits (decommits are already understood)
  • An ADR for improving tx construction & observation to not need chain state

· One min read
Sasha Bogicevic

High-level summary

This week, the Hydra team focused primarily on changes needed in the network layer and have the first draft document related to needed design. They also improved the user experience by allowing a commit using inline datums. Discussed the off-chain governance with researchers and improved internal model tests.

What did the team achieve this week

  • Monthly report published
  • Small changes to hydraw and tutorial in light of the Masterclass
  • Investigated a bug and saw it was solved by recent developments
  • Improved the model tests by fully validating L1 transactions
  • Enhanced the /commit API to also allow commit from scripts with inline datums (user request)
  • Discussed off-chain governance with IOG and CF researchers
  • Drafted a first network specification document in the context of Network resilience

What are the goals of next week

  • Have a clear understanding of the changes we need for the "Improve network resiliency" feature
  • Groomed and agreed plan on incremental commits/decommits
  • Updated tutorials including CI workflows to check consistency
  • Update to GHC 9.6 and latest cardano dependencies (ledger/plutus)