-
Notifications
You must be signed in to change notification settings - Fork 385
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
Generate a funding_locked on relevant transactions_confirmed calls #1363
Generate a funding_locked on relevant transactions_confirmed calls #1363
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1363 +/- ##
=======================================
Coverage 90.65% 90.66%
=======================================
Files 73 73
Lines 40462 40482 +20
=======================================
+ Hits 36682 36701 +19
- Misses 3780 3781 +1
Continue to review full report at Codecov.
|
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.
Looks good modulo one nit.
4e89d79
to
5d82303
Compare
5d82303
to
abfc3ec
Compare
Previously, if we were offline when a funding transaction was locked in, and then we came back online, calling `best_block_updated` once followed by `transactions_confirmed`, we'd not generate a funding_locked until the next `best_block_updated`. We address this by re-calling `best_block_updated` in `transactions_confirmed`, similar to how `ChannelMonitor` works.
abfc3ec
to
ea76942
Compare
Squashed without changes. |
Previously, if we were offline when a funding transaction was
locked in, and then we came back online, calling
best_block_updated
once followed bytransactions_confirmed
,we'd not generate a funding_locked until the next
best_block_updated
.We address this by re-calling
best_block_updated
intransactions_confirmed
, similar to howChannelMonitor
works.Reported by BlueWallet.