103 posts tagged with "hydra"

High-level summary​

This week, the Hydra team released version 0.9.0 - a version of the hydra-node with fully specified behavior of on-chain scripts and off-chain head-logic, decreased costs for opening/closing a Head and scalable contestation deadline semantics. Check out the full release notes for details.

Furthermore, they published the monthly report of the Hydra project and conducted a review meeting with an increasingly wider audience. The team plans to extend invitations through the new Hydra #announcements discord channel for the next months, stay tuned!

What did the team achieve this week​

• Monthly review meeting with report published on website
• Fixed smoke tests #726
• Reduced the cost of opening/closing a Head (error codes #748 + head reference script #701)
• Released version 0.9.0
• Conducted a first experiment on mainnet compatibility #713
• New discord category with #announcements channel
• Received a demo about the Hydra for Voting project
• Lightning talk on mutation-based testing (to be shared)
• New themes view in on our roadmap and some rearranging as we align it with high-level objectives
• Clarified things with researchers, but mostly identified action items for them

What are the goals of next week​

• Redraw transaction graphs and address TODOs specification
• Run hydraw with 0.9.0 on preprod
• Make smoke tests on mainnet possible
• Groom the explorer item
• Unblock the auctions projecth with “commit from script” a solution

High-level summary​

This week, the Hydra team continue closing many gaps and aligning the implementation with the specification. More over, they have groomed a plan to make Hydra Mainnet compatible. Also, they continue moving forward with the internal auditing and have published some auditing guidelines to receive contributions from the community.

What did the team achieve this week​

• Completed #452 (what is remaining in there)
• Aligned the Head protocol logic implementation with the specification
• Completed full minting policy implementation and spec #720
• Clarified message authentication with researchers
• Groomed what is left to do for Mainnet compatibility #713 and drafted a 0.10.0 version
• Added a tutorial by @perturbing to the website LINK
• Published auditing guidelines LINK
• Made hydra-node work for macos #746 and added support for building on aarch64 #673
• Met with a potential customer of Hydra for Payments

What are the goals of next week​

• Have the monthly review meeting incl. the report
• Have smoke tests fixed and running regularly
• Release 0.9.0 with updated scripts
• Redraw transaction graphs for specification

High-level summary​

This week, the Hydra team completed work on dealing differently with contests during the contestation period. These will now always push out the deadline and hence contestation periods are easier to pick (depending on the network a Head runs on). Furthermore, they added an important acceptance test and completed internal refactoring of the protocol logic making future changes easier.

What did the team achieve this week​

• Push contestation deadline on each contest #716
• Wrote an acceptance (property) test “can always close/fanout when collect is successful”
• Internal refactoring of our HeadLogic
• Groomed remaining things from #452 into dedicated features

What are the goals of next week​

• Complete full minting policy #720
• Release 0.9.0 with updated scripts
• Plan mainnet milestone and a 0.10.0 version
• Redraw transaction graphs for specification (upon feedback)
• Have smoke tests fixed and running regularly

High-level summary​

This week, the Hydra team closed several gaps to align the Hydra scripts implementation further with the specification. This also resulted in a slight improvement on Hydra script size and costs. They consequently analysed the asymptotic complexity of collect and fanout and how they relate. Also plutus-tx profiling toolchain was evaluated and set up for future improvements on Hydra on-chain performance. In discussions with researchers and internal auditors, they also uncovered next steps on further securing the Head protocl using a "full" minting policy.

What did the team achieve this week​

• Closed several gaps to align script implementation with specification #452
  • Allow contest only once #680
  • Optimization through head output at index 0 #700
  • Value is preserved #702 + optimized exact value equality #709
• Analysed asymptotic complexity of some of our scripts and set up profiling toolchain to #721
• Fixed our tooling around the Haskell language server
• Discussed full minting policy with researchers
• Started grooming “what we need for mainnet” on this idea ticket and milestone

What are the goals of next week​

• Implement full minting policy
• All remaining protocol discrepancies are implemented or groomed as individual features
• Ideally release 0.9.0 with updated scripts
• Discuss what we need for mainnet (milestone planning)
• Redraw transaction graphs for specification (upon feedback)

High-level summary​

This week, the Hydra team completed the Hydra specification with a section about rollbacks and updated graphs (#448). In a next step, the specification will be made more approachable and an open standard. They improved their hydra-cluster tool to launch a local --devnet sandbox environment and continued aligning the hydra-plutus scripts with the specification by hardening the checks on close and contest transactions.

What did the team achieve this week​

• Completed the specification with a section about rollbacks and updated graphs #448, with a follow-up on making it more approachable and an open standard.
• Continued spec review with internal auditor and incorporated changes.
• Talked to TxPipe about how Demeter and Hydra could work together
• The hydra-cluster executable can be used to launch a local --devnet sandbox environment.
• Reproduced the “head being stuck on network outage” bug
  • relates to what liveness guarantees we can / want to give on the protocol level and needs to be discussed.
• Progressed with higher velocity by addressing more and more gaps #677

What are the goals of next week​

• Upstream our JSON instances to the ledger
• Close all transaction security related on-chain gaps
• Ideally release 0.9.0 with updated scripts
• Groom & plan (or not) protocol changes yielded from specification discussions -> updated roadmap