Skip to content

Simplify and expand logging in is_resolving_htlc_output #283

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

Merged

Conversation

TheBlueMatt
Copy link
Collaborator

Based on #282 since they conflict.

@TheBlueMatt TheBlueMatt changed the title 2019 01 htlc resolution log Simplify and expand logging in is_resolving_htlc_output Jan 6, 2019
@TheBlueMatt TheBlueMatt force-pushed the 2019-01-htlc-resolution-log branch from f79b74d to 9e6a369 Compare January 6, 2019 22:44
@TheBlueMatt TheBlueMatt force-pushed the 2019-01-htlc-resolution-log branch from 9e6a369 to 0baf07e Compare January 7, 2019 17:59
Copy link

@ariard ariard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, just few nit suggestions

When our counterparty claims multiple HTLCs from offered outputs in
one transaction we should still be able to learn the preimages.
Sadly, due to two bugs we were not previously doing so.
This clarifies all the conditions we can hit and also ensures they
are all logged in a clear and consistent manner.
@TheBlueMatt TheBlueMatt force-pushed the 2019-01-htlc-resolution-log branch from 0baf07e to 90ce971 Compare January 9, 2019 04:03
@TheBlueMatt TheBlueMatt merged commit a604cb6 into lightningdevkit:master Jan 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants