103 posts tagged with "hydra"

High-level summary​

This week, the Hydra team had a monthly review meeting with their stakeholders, contributors and interested people from the community. The monthly repot for January 2023 is a digest of the things presented and also includes a summary of the meeting. The Hydra specification was getting discussed and the team is incorporating suggested changes of reviewers. Last but not least, they compute and publish script information on every PR and also on the website now.

What did the team achieve this week​

• Had the monthly review meeting with a broader audience
• Published the monthly report for January 2023
• Reviewed the spec and discussed individual aborts with researchers
• Compute and publish script information along benchmarks on every PR and website

What are the goals of next week​

• Add rollback section to Hydra spec, update pictures and publish it as part of repository
• Discuss bigger spec findings (full minting policy, individual aborts, split fanout) as change/pull requests on the spec in the repository.
• Groom & plan actions required for a maintainable Head explorer + break down “align gaps” feature.

High-level summary​

This week, the Hydra team has been focusing on the write-up of the Hydra HeadV1 specification. Of which a first version has been aggregated and is currently under review. They aligned the on-chain scripts of reimbursing funds on abort like defined in the specification, improved the mutation test framework to have more control when testing plutus scripts. The added HeadId in the API and the TUI example client make hydra-node easier to use and a first experiment of a Hydra Head explorer was showing the utility of this - see what Heads exist on the preview network here.

What did the team achieve this week​

• HeadId to API and display in the TUI #678
• Experiment of creating a hydra explorer, first result hosted here
• Improved mutation framework allowing to fail for the right reason #679
• Correctly reimburse funds in abort (matching the spec) #670
• Finished a first write-up of the Hydra HeadV1 spec: Read it on overleaf (Communication channels for feedback)

What are the goals of next week​

• Monthly review meeting with a broader audience
• Groom & plan actions required for a maintainable Head explorer
• Break “align gaps” feature into smaller chunks (at least on- /off-chain) and groom it
• Review the spec & discuss individual aborts with researchers (a bigger open question)

High-level summary​

Since last weekly update before christmas, the Hydra team worked on the technical specification, closed gaps in hydra-plutus scripts, made the unique headId available to Hydra clients through the API, allow the hydra-node to explicitly synchronize from genesis (if configured), and fixed smaller log and build issues reported by new users.

Besides this, a retrospective blog post was published by Matthias Benkort (CF) on Hydra, summarizing our progress made in 2022 also an outlook where Hydra is headed for in 2023. Also, the team had some first sessions on the voting project with Catalyst and the CF.

A full digest monthly digest for December 2022 can be found on the hydra website.

What did the team achieve this week​

• Had some first sessions on the voting project with Catalyst and CF
• Published retrospective blog post by Matthias Benkort (CF) on Hydra, summarizing our progress made in 2022 also an outlook where Hydra is headed for in 2023.
• Worked on the LaTeX spec for HydraHeadV1, not final or published yet - latest version in this repository.
• Add unique headId to API and hence make it available to clients.
• Allow hydra-node to explicitly synchronize from genesis using --start-chain-from 0.
• Closed gaps in hydra-plutus scripts
  • bounded transaction validity (ADR21)
  • enforcing contract continuity via state token in output
• Fixed JSON for some logs and smaller build issues reported by new users.

What are the goals of next week​

• Reach out to have hydra-tutorial integrated.
• Plan the next couple of months.
• Complete checking reimbursing of commits in head validator.
• Align plutus scripts to spec and simplify them (identified some simplifications)
• Improve mutation framework to be sure we fail tests for the right reasons
• Complete the spec except the open points (<5) and also discuss them with researchers.

High-level summary​

This week, the Hydra team kicked off a new project together with Catalyst, the Cardano Foundation and researchers from IO: a proof of concept for voting on Hydra. The concluded work on validating the Head protocol using model-based testing and formulated next steps, fixed the transaction cost benchmark reporting on the website and reduced the cost for commit transactions by ~30% with the help of reference scripts.

The year is coming to an end and velocity will slow down a bit while the team focuses on wrapping up loose ends. The updates here will pause until January 2023.

What did the team achieve this week​

• Kicked-off Hydra Voting project with Catalyst, CF, and IO Research.
• Reduce commit transaction costs by ~30% with reference scripts.
• Prepared an RFP for external audit of the Hydra Head solution.
• Fixed transaction cost benchmarks for abort tx #631.
• Recorded decision to use model-based testing (ADR22) and improved Model documentation.
  • Concluding the first increment on “Validate coordinated Head protocol” #194.
  • Formulated next step / follow-up on testing the Soundness property of our protocol #656.
• Switched to using nix flakes for development setup and CI build #646.

What are the goals of next week​

• Push ADR21 & tx validity gap over the finish line (smoke tests missing).
• Integrate the hydra-tutorial.
• Have a LaTeX write-up of the HeadV1 (Coordinated Hydra Head) spec.
• Close & recap on the year with another monthly report (+ blog post).

High-level summary​

This week, the Hydra team has worked on completing to "Validate coordinated head protocol against formal model", this is a huge step to verify the implementation is secure. They also worked on implementing ADR21 related to bounded tx validity which is now under review. HydraPay project, from Obsidian Systems, is coming to an end of the first phase at least, so team did a review and submitted couple of issues they found in the process. The team had a meeting with the Director of CyberSecurity - topic was the RFP that is currently in flight that should scope the work of future auditors. Also, the team completed the hydra-tutorial review created by our colleague Thomas Vellecoop from the education team, and we are close to integrate it to our official site. From the development side, they have fixed a bug on the CI when running the benchmark jobs to calculate the cost of abortTx and a flaky spec which checks a plutus merkle-tree is always balanced.

What did the team achieve this week​

• Document model based testing #194 & #641
• Got ADR21, reducing gaps between implementation and specification, under review.
• Complete review on hydra-tutorial.
• Complete first round of review on HydraPay work #634
• Meeting with Director of CyberSecurity frio IOG to unblock "the RFP prepared for the external audit" #606
• Remove vasil-dev and testnet from smoke-test because they were not working #630
• Fix flaky plutus-merkle-tree test #642
• Refactor NetworkSpec to improve legilibility.
• Fix benchmark cost for abortTx #631
• Adapt nix.conf to the recent hydra-ci nix cache migration.

What are the goals of next week​

• Get ADR21 accepted & close tx validity gap in our implementation.
• Integrate the hydra-tutorial.
• Have a LaTeX write-up of the HeadV1 (Coordinated Hydra Head) spec.
• Get Cicero (new CI) working.
• Use reference inputs to reduce the cost of the commitTx.