Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open a head between Hydra core members and test out the new functionality #1738

Closed
13 of 15 tasks
Tracked by #199
v0d1ch opened this issue Nov 8, 2024 · 0 comments
Closed
13 of 15 tasks
Tracked by #199
Assignees
Milestone

Comments

@v0d1ch
Copy link
Contributor

v0d1ch commented Nov 8, 2024

Within a group of 3+ people, we want to open a head to validate thte incremantal commit feature scenarios manually:

  • Can commit to an open Head
    • no matter what is currently available on L2 (also empty head)
  • Can commit and immediately close with the same snapshot
  • Can do multiple increments one after another
  • Can do multiple commits and decommits in sequence as long as decommitted UTxO are consistent
  • Can commit and decommit the same UTxO should result in the same open Head UTxO
  • Cannot commit while another decommit is pending
  • Cannot decommit funds you don't own
  • Cannot commit funds you don't own (to submit a deposit we need a proper sig)
  • Can decommit everything from the Head
  • Can process L2 transactions of independent UTxO while commit is happening.
  • Cannot commit same UTxO in two Heads
    • specially in presence of rollbacks (due to network partition)
    • possible interactively?
  • Can close and fanout while commit is pending
    • i.e. when someone did not submit incrementTx
    • either funds did not get committed at all or reimbursed by fanout (in my case funds got stuck in the deposit contract thus this issue Enable recovering in closed state too #1812 )
    • possible interactively?.

We are going to use a recent, but unreleased version of Hydra for this

@v0d1ch v0d1ch mentioned this issue Nov 8, 2024
15 tasks
@github-project-automation github-project-automation bot moved this to In Progress 🕐 in ☕ Hydra Team Work Nov 8, 2024
@noonio noonio moved this from In Progress 🕐 to Todo 📋 in ☕ Hydra Team Work Nov 12, 2024
@noonio noonio moved this from Todo 📋 to In Progress 🕐 in ☕ Hydra Team Work Jan 2, 2025
@noonio noonio moved this from In Progress 🕐 to Done ✔ in ☕ Hydra Team Work Jan 7, 2025
@noonio noonio closed this as completed by moving to Done ✔ in ☕ Hydra Team Work Jan 7, 2025
@ch1bo ch1bo reopened this Jan 7, 2025
@github-project-automation github-project-automation bot moved this from Done ✔ to In Progress 🕐 in ☕ Hydra Team Work Jan 7, 2025
@noonio noonio moved this from In Progress 🕐 to Todo 📋 in ☕ Hydra Team Work Jan 8, 2025
@noonio noonio assigned v0d1ch and unassigned ffakenz Jan 20, 2025
@noonio noonio added this to the 0.20.0 milestone Jan 20, 2025
@ch1bo ch1bo moved this from Todo 📋 to Blocked ✋ in ☕ Hydra Team Work Jan 20, 2025
@ch1bo ch1bo moved this from Blocked ✋ to In Progress 🕐 in ☕ Hydra Team Work Jan 21, 2025
@ch1bo ch1bo removed their assignment Jan 28, 2025
@noonio noonio moved this from In Progress 🕐 to Done ✔ in ☕ Hydra Team Work Jan 31, 2025
@noonio noonio closed this as completed by moving to Done ✔ in ☕ Hydra Team Work Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

5 participants