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

Implement retry mechanism for Close and Contest Hydra transactions #42

Open
errfrom opened this issue May 2, 2024 · 0 comments · May be fixed by #48
Open

Implement retry mechanism for Close and Contest Hydra transactions #42

errfrom opened this issue May 2, 2024 · 0 comments · May be fixed by #48
Assignees

Comments

@errfrom
Copy link
Member

errfrom commented May 2, 2024

Relevant snippet from the hydra-node docs:

Depending on the contestation period value and the network conditions,
`Close` and `Contest` transactions could become invalid and be
silently rejected by the cardano-node to which they have been
submitted. This can happen, for example, if:
* The network is congested, with lot of transactions waiting to be
  included in a block,
* The node's connectivity to the network drops and the transaction is
  not propagated to block producers fast enough.

The hydra-node itself does not currently handle this situation and
therefore each client application needs to put in place some retry
mechanism depending on the time it should "normally" take to have the
transaction.

https://github.com/input-output-hk/hydra/blob/d12addeeec0a08d879b567556cb0686bef618936/docs/docs/getting-started/quickstart.md?plain=1#L196-L212

@errfrom errfrom self-assigned this May 16, 2024
@errfrom errfrom linked a pull request May 17, 2024 that will close this issue
@errfrom errfrom linked a pull request May 17, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant