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
In this commit we introduce maximum fee percentages
for the static loop-in htlc transactions. Since
the server has the ability to publish htlc transactions
without settling the swap payment we have to restrict
the amount the server allocates for fees of these
transactions.
// defaultRPCBatchSize is the default batch size to use for RPC calls
52
54
// we make to LND during migrations. If operations on the LND side are
@@ -183,6 +185,9 @@ type Config struct {
183
185
TotalPaymentTimeout time.Duration`long:"totalpaymenttimeout" description:"The timeout to use for off-chain payments."`
184
186
MaxPaymentRetriesint`long:"maxpaymentretries" description:"The maximum number of times an off-chain payment may be retried."`
185
187
188
+
MaxStaticAddrHtlcFeePercentagefloat64`long:"maxstaticaddrhtlcfeepercentage" description:"The maximum fee percentage that the server can charge for the htlc tx."`
189
+
MaxStaticAddrHtlcBackupFeePercentagefloat64`long:"maxstaticaddrhtlcbackupfeepercentage" description:"The maximum fee percentage that the server can charge for the htlc backup tx. The backup transaction is only used in rare cases when the regular htlc tx is not confirmed on time. These backup transactions refer to high fee or extremely high fee transactions in the API."`
0 commit comments