You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before we were ignoring dust when creating the closing channel fee. Now
if an output would be dust, we will recalculate the fee with the missing
output. This should fix some force closes that happen with lnd nodes.
// Note that technically we could end up with a lower minimum fee if one sides' balance is
4428
-
// below our dust limit, causing the output to disappear. We don't bother handling this
4429
-
// case, however, as this should only happen if a channel is closed before any (material)
4430
-
// payments have been made on it. This may cause slight fee overpayment and/or failure to
4431
-
// come to consensus with our counterparty on appropriate fees, however it should be a
4432
-
// relatively rare case. We can revisit this later, though note that in order to determine
4433
-
// if the funders' output is dust we have to know the absolute fee we're going to use.
4434
-
let tx_weight = self.get_closing_transaction_weight(Some(&self.get_closing_scriptpubkey()),Some(self.counterparty_shutdown_scriptpubkey.as_ref().unwrap()));
4435
-
let proposed_total_fee_satoshis = proposed_feerate asu64* tx_weight / 1000;
4436
-
let proposed_max_total_fee_satoshis = ifself.is_outbound(){
4437
-
// We always add force_close_avoidance_max_fee_satoshis to our normal
4438
-
// feerate-calculated fee, but allow the max to be overridden if we're using a
0 commit comments