Could not finalize refund transaction: could not broadcast transaction: min relay fee not met, 0 < 162 about boltz-client HOT 5 CLOSED

Same happened to me just now. I quickly worked around it with this:

diff --git a/nursery/reverse.go b/nursery/reverse.go
index 802d4ef..604a401 100644
--- a/nursery/reverse.go
+++ b/nursery/reverse.go
@@ -158,6 +159,9 @@ func (nursery *Nursery) handleReverseSwapStatus(reverseSwap *database.ReverseSwa
 			logger.Error("Could not get LND fee estimation: " + err.Error())
 			return
 		}
+		if feeSatPerVbyte < 1 {
+			feeSatPerVbyte = 1
+		}
 
 		logger.Info("Using fee of " + strconv.FormatInt(feeSatPerVbyte, 10) + " sat/vbyte for claim transaction")
 

But a proper investigation needed of course. With this patch your only risk is that the transaction might get stuck but you can recover it easily with CPFP.

from boltz-client.

Same happened to me just now. I quickly worked around it with this:

This patch should get the transaction through.

But a proper investigation needed of course

I think I already know what's wrong. What LND version are you guys using @rkfg @lschmierer?

from boltz-client.

Compiled from master a few days ago, lncli version 0.13.99-beta commit=v0.13.0-beta-113-g583dee99

from boltz-client.

@michael1011 what was the motivation to get floor to 2 sats instead of 1 sat?

Also lightningnetwork/lnd#5483 is probably related

from boltz-client.

@michael1011 what was the motivation to get floor to 2 sats instead of 1 sat?

Sorry for the late reply. The reason is that the onchain HTLCs are somewhat time critical and in my experience using a 2 sat/vbyte fee is more reliable when lnd suggests 1 sat/vbyte. I have had quite a few transactions stuck at 1 sat/vbyte in the past.

from boltz-client.