Skip to main content

29 posts tagged with "hydra"

View All Tags

· One min read
Sebastian Nagel

High-level summary

This week, the Hydra team focused on improving the smoke test, fixing developer tooling, and improving the API for voting use cases. They reviewed progress on auction, payments, and voting projects and made worked on reproducing a bug with handling rollbacks. Moving forward, the team plans to update dependencies, implement a dirt road fix for the rollbacks bug, and explore adding Hydra support to kupo.

What did the team achieve this week

  • Reviewed progress on auction, payments and voting projects
  • Improved smoke tests so they can run on mainnet
  • Fixed a regression in the development environment and updated cardano-node used in tests
  • Improved API with more configurability to unblock voting use case
    • Exclude utxo in SnapshotConfirmed outputs #808
    • Addressed a user request by only sending Greetings once #813
  • Reproduced the rollback bug by improving our model-based test suite #784

What are the goals of next week

  • Update dependencies to match cardano-node master
  • Dirt road fix for rollbacks #784
  • Update Hydraw to maintain state locally
  • Explore adding Hydra support to kupo
  • Put disclaimer texts and closing mainnet compatibility feature #713

· One min read
Sebastian Nagel

High-level summary

This week, the Hydra team published the monthly report for March, created separate links for different versions of documentation, and clarified potential solutions for the Rollbacks bug. The team also discussed Query API requests for the Hydra Voting project and met with community members to answer questions about Hydra. Moving forward, the team plans to integrate the specification into the repository, implement a short-term fix for the Rollbacks issue, and draft a Query API ADR.

What did the team achieve this week

  • Published monthly reports on website
  • Separate last released and latest versions of docs (e.g. normal released vs. /unstable)
  • Discussed Query API concerns from Hydra Voting project (link)
  • Clarified rollbacks bug and defined possible solutions (short and long term) #784
  • Met with community members to answer questions about Hydra

What are the goals of next week

  • Finally get the docs integrated into the repository #693
  • Dirt road fix for rollbacks #784
  • Disclaimer text and detail known issues about mainnet compatibility #713

· One min read
Sebastian Nagel

High-level summary

This week, the Hydra continued work on finishing mainnet compatibility. The semi-automated smoke tests and some missing documentation is still preventing from calling that fully done. They fixed smaller issues and made a step in the Head protocol more robust. Besides development, they met with interested people from the community who want to get started collaborating on communication and marketing materials.

What did the team achieve this week

  • Groomed and followed-up on GetUTxO user request discussion #797
  • Fixed hydra-node crashes after forks #560
  • Made collectCom more robust and aligned with spec #786
  • Completed configurable API feature #380
  • Met potential contributors about Hydra communication and marketing materials
  • Versioned documentation: we have a unstable bleeding edge version available as well now, seperate from the last released version

What are the goals of next week

  • Follow-up backlog and roadmap clean-up
  • Complete mainnet compatibility feature #713 (documentation updates)
  • Integrate Hydra specification into repository #693

· One min read
Sebastian Nagel

High-level summary

This week, the Hydra had a team workshop and conducted the monthly review meeting for March. They demonstrated a Hydra Head on mainnet, which was running the hydraw demo application. While this marks an important milestone, they also emphasized that more features are still to be added as needed for applications to run on Hydra. Besides this, the roadmap is getting cleaned up to encourage discussions and provide more space for user requests.

What did the team achieve this week

  • Monthly review meeting slides/recording, full report of March next week
    • Opened a head on mainnet with hydraw demonstration
    • Hydra pay updates
  • Team workshop in Austria
    • Hydra presentation at the Cardano Foundation in Zurich
    • In-person grooming session, marked many items as candidates to be rather :idea: dicussions
    • Improved head protocol #786 and investigated a potential bug in rollback handling #784
    • Team building and retrospective

What are the goals of next week

  • Follow-up on backlog and roadmap clean-up
  • Complete mainnet compatibility feature (documentation updates)
  • Make API more configurable #380
  • Integrate Hydra specification into repository #693

· 2 min read
Sebastian Nagel

High-level summary

This week, the Hydra team has continued work on the mainnet compatibility of the hydra-node. They added a golden test suite for hydra-plutus scripts, added some detection of hydra-node misconfiguration, established a limit of 100 ADA per commit and other smaller tasks to prepare for a mainnet beta release.

Next week there will be a small team workshop to push for demonstrating a Hydra Head on the Cardano mainnet, ideally just in time for the monthly review meeting. See the hydra channels on the IOG Technical Community discord server for details.

What did the team achieve this week

  • Implement a 100 ADA hard-coded commit limit in the hydra-node #763
  • Pay back funds to faucet after smoke-test run #773
  • Setup custom github runner for smoke-tests on mainnet #775
  • Created golden tests to assure the script hash stays the same between changes #772
  • Removed hardcoded error codes in plutus scripts #768
  • Detect misconfiguration of a hydra-node given persistent state #767
  • Met with potential users for hydra-pay
  • Prepared hydra workshop

What are the goals of next week

  • Hydra monthly meeting
  • Open a multi-party head on mainnet
  • Complete mainnet compatibility feature