Commit 0f4e6c2
committed
Fix
`build_commitment_transaction`'s fifth argument is supposed to be
whether we're the one generating the commitment (i.e. because we're
signing rather than validating the commitment). During splicing,
this doesn't matter because there should be no async HTLC
addition/removal happening so the commitment generated wil be the
same in either case, but its still good to pass the correct bool.generated_by_local arg to build commmitment during splicing1 parent 491b694 commit 0f4e6c2
1 file changed
+1
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
6252 | 6252 | | |
6253 | 6253 | | |
6254 | 6254 | | |
6255 | | - | |
| 6255 | + | |
6256 | 6256 | | |
6257 | 6257 | | |
6258 | 6258 | | |
| |||
0 commit comments