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

Hydra node resets head state when replaying close of another head #927

Closed
ch1bo opened this issue Jun 14, 2023 · 0 comments · Fixed by #930
Closed

Hydra node resets head state when replaying close of another head #927

ch1bo opened this issue Jun 14, 2023 · 0 comments · Fixed by #930
Labels
bug 🐛 Something isn't working
Milestone

Comments

@ch1bo
Copy link
Member

ch1bo commented Jun 14, 2023

Context & versions

Any recent version, likely 5642332 and master

Steps to reproduce

  1. Initialize a head on a network and initialize in block x+1
  2. Open & close that head again
  3. Start the hydra-node with --start-chain-from on block x
  4. Open another, new head and do some transactions
  5. Restart the hydra-node with same (start chain from x) configuration
  6. The hydra-node has thrown away it's layer two state

Actual behavior

The hydra-node replays the L1 history. While most chain tx observations are ignored, the CloseTx from the old head will have the node evolve it's headState to first follow the old head getting closed and then the new head beeing initialized. Ultimately it will appear as the hydra-node has thrown away it's L2 state and got reset with a "fresh" open head.

Expected behavior

Observes and deliberately ignores Hydra transactions from other heads. For example using the headId

@ch1bo ch1bo added the bug 🐛 Something isn't working label Jun 14, 2023
@pgrange pgrange mentioned this issue Jun 14, 2023
5 tasks
@ch1bo ch1bo added this to the 0.11.0 milestone Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant