Skip to main content

90 posts tagged with "hydra"

View All Tags

· 2 min read
Franco Testagrossa

High-level summary​

This week, the Hydra team has put their effort on finding solutions on many different problems, such as our broken head on mainnet #897, our fragile monthly report publications on the website and implementing “Option A” for external commits #215. Although most of these items are still open, huge progress has been made. To accelerate the investigation, they improved their logging to give more precise errors when a transition requirement fails, and to reduce duplication on effets logged content. Last but not least, the team is exploring formal methods and attended a workshop on formalizing cryptographic protocols in Agda.

What did the team achieve this week​

  • Continued investigating broken head and opened an issue to keep track #897.

    As part of this issue, improvements were made to the node logs:

    • Give a precise error when a transition requirement fails #895.

    • Reduce duplication for effects logged content by using sequential eventId and effectId pair #896.

  • Fixed references in the hydra specification #893.

  • Attended a workshop on formal methods and crypto in Agda.

What are the goals of next week​

  • Investigate and re-open our team-internal head on mainnet.
  • Improve and provide regular benchmarks for Hydra #186.
  • Complete journey for external commits implementing “Option A” and start implementing “Option B” #215.
  • Authenticate network messages #727.
  • Add hydra as tool to developr platform #872.
  • Fix monthly report publication on docs website.

· 2 min read
Sebastian Nagel

High-level summary​

This week, the Hydra team accomplished several important tasks. They held their monthly review meeting and drafted the report for May. They made progress on implementing the first end-to-end journey for external commits using "Option A" for normal UTxOs, while still considering "Option B". The team also integrated a Spanish translation contributed by the community, created micro-benchmarks for transaction validation and deserialization, and made improvements to hydra-node's version reporting. Last but not least, they implemented the ability to commit multiple UTxOs to a head at once.

What did the team achieve this week​

  • Held the monthly review meeting (recording + slides) & drafted the report for May.
  • Have a first end-to-end journey for external commits implementing “Option A” for normal UTxOs #887 (still considering “Option B”).
  • Integrated the spanish translation #866.
  • Created micro-benchmarks for transaction validation and deserialization #884.
  • Improve hydra-node –version reporting on non-released builds #849
  • Some minor CI improvements following up last weeks changes.
  • Allow commit transactions with multiple UTxO #774.

What are the goals of next week​

  • Investigate and re-open our team-internal head on mainnet.
  • Improve and provide regular benchmarks for Hydra #186.
  • Complete external commits with script UTxOs #215.
  • Authenticate network messages #727.
  • Add hydra as tool to developr platform #872.

· 2 min read
Franco Testagrossa

High-level summary​

This week, the Hydra team has worked on several fronts, including improvements of their CI speed, logs, documentation pages and adding the support for timed transactions. They also updated the "Coding Standards" for the project, improved the troubleshooting page on their website and wrote a section about how to operate a hydra node. Finally the team completed a feature request that allows clients to submit and validate transactions to their hydra nodes using time validity ranges, ensuring isomorphism with L1.

What did the team achieve this week​

  • Complete validation of timed transactions feature #196.
  • Write “ops” instructions and troubleshooting #569 and improve logs.
  • Remove --ledger-genesis argument to hydra-node options #863.
  • Fix issue with garbage collected caches by using a new cardano-scaling.cachix in more workflows #877.
  • Use nix to build test binaries to increase CI speed #867.
  • Updated our Coding Standards.

What are the goals of next week​

  • Monthly report & review meeting.
  • Have a first end-to-end journey for external commits implementing "Option A" #215.
  • Integrate spanish translation #866.
  • Improve and provide regular benchmarks for Hydra #186.
  • Allow commit transactions with multiple UTxO #774.
  • Explored stateless observation and refined hydra explorer ticket #696.

· 2 min read
Sebastian Nagel

High-level summary​

This week, the Hydra team achieved a number of milestones, including the release of the first mainnet compatible version. Besides this they also addressed inconsistencies in rollback handling, added an architecture page to the website, reducing the size of logs using event IDs. They also had productive discussions with researchers on plans for incremental commits/decommits and had a whiteboard session on DeFi and lending protocols. The goals for next week include completing the validation of the timed transactions feature, exploring stateless observation, refining the Hydra explorer ticket, writing ops instructions and troubleshooting, and implementing the first end-to-end journey for external commits.

What did the team achieve this week​

  • Released first mainnnet compatible version 0.10.0
  • Addressed inconsist handling of rollbacks #784
  • Added architecture page and fixed haddock links on our website #838
  • Opened a new hydra head on mainnet
  • Talked with researchers on initial plan for incremental commits/decommits
  • Had a Whiteboard session on DeFi and lending protocols
  • Reduced size of logs using event ids #859
  • Published the monthly report for April

What are the goals of next week​

  • Complete validation of timed transactions feature #196
  • Explored stateless observation and refined hydra explorer ticket #696
  • Write “ops” instructions and troubleshooting #569 and improve logs
  • Have a first end-to-end journey for external commits implemented #215

· 2 min read
Sebastian Nagel

High-level summary​

This week, the Hydra team held their Monthly review meeting and drafted the report which likely is published next week. They put the spec into the repository and website, addressed a user issue and fixed the TUI peer list. Furthermore, they updated dependencies, conducted a Twitter space on Auctions use cases, covered the rollback bug with tests and implemented a solution. Looking ahead, their goals for next week include releasing 0.10.0, implementing timed transactions support, writing a Query API ADR, and grooming work items like off-chain benchmarks.

What did the team achieve this week​

  • Held the Monthly review meeting and drafted the report (to be published next week)
  • Added the spec into the repository #693 and published on the website
  • Groom and addressed user issue #823
  • Covered the rollback bug with tests and implemented a solution (to be reviewed) #784
  • Fixed the TUI peer list
  • Updated dependencies to match cardano-node master
  • Conducted a twitter space on Auctions use cases

What are the goals of next week​

  • Release 0.10.0
  • Support timed transactions solution drafted and validated API with users
  • Write Query API ADR and groom a concrete step
  • Groom and solve PostTxOnChainFailed UX problem #832
  • Groom off-chain benchmarks idea #186 and turn it into a “feature”