Conversation
|
I've assigned @wpaulino as a reviewer! |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 0.2 #4239 +/- ##
==========================================
+ Coverage 88.85% 88.86% +0.01%
==========================================
Files 180 180
Lines 138003 138042 +39
Branches 138003 138042 +39
==========================================
+ Hits 122619 122675 +56
+ Misses 12562 12551 -11
+ Partials 2822 2816 -6
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
wpaulino
left a comment
There was a problem hiding this comment.
@TheBlueMatt up to you if you want to include it this late in the cycle
|
👋 The first review has been submitted! Do you think this PR is ready for a second reviewer? If so, click here to assign a second reviewer. |
There was a problem hiding this comment.
Seems this needs a rebase.
Also, I want to note that this breaks SemVer rules as adding new fields to enum variants are considered major changes.
So not sure we can/should actually land this in a patch release?
|
This is not meant to go in a patch release as 0.2 does not have a final release yet. |
|
Please include the suffix we generally include in backported commits - add |
Original context and motivation comes from here: lightningdevkit/ldk-node#677 (comment) When splicing-in, the default case is our channel utxo + our wallet utxos being combined. This works great however, it can give our wallet issues calculating fees after the fact because our wallet needs to know about our channel's utxo. We currently have it's outpoint and satoshi value available, but not its output script so we are unable to construct the TxOut for the channel. This adds the redeem script to the `ChannelDetails` and `ChannelPending` event which gives us enough information to be able to construct it. Backport of add202e
6e6e4c2 to
0075d5a
Compare
rebased and done, there were no conflicts |
Backports #4234