Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add PersistClaimInfo and ClaimInfoRequest events #3067
Add PersistClaimInfo and ClaimInfoRequest events #3067
Changes from 1 commit
8a56137
0e8d297
060db20
7fad4ee
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This event can never be ignored, cause if it is generated
PersistClaimInfo
is being handled.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should probably have some kind of advice for what users should do if they don't find the claim info on disk - I assume they should probably treat it as if they definitely just lost funds (panic or whatever)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: No need to add this reference if in the same module. Then again, we may want to move the new structs to
ChainMonitor
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The names of other event types usually either reflect that something happened (
PaymentClaimed
/PaymentFailed
) or that something needs to be done (DiscardFunding
,ConnectionNeeded
).ClaimInfoRequest
(and to an extend alsoPersistClaimInfo
) doesn't make it easy to infer whether it's simply informational or if the user needs to take action. Could this be improved?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ClaimInfo
andClaimMetadata
are very similar and very generic names. Can we make them a bit more specific, i.e., reflect their purpose a bit better?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be called
funding_txo
? Do we already now how this will work in the context of splicing? If this is indeed amonitor_id
, should we use an opaqueMonitorId
type that would allow us to change its semantics internally in the future? If not, can we make this abitcoin::OutPoint
to avoid mixing the two differentOutPoint
types across our public API?