highperfocused/lnd
1
0
Fork 0
mirror of https://github.com/lightningnetwork/lnd.git synced 2025-11-10 06:07:16 +01:00
Code Issues Packages Projects Releases Wiki Activity

multi: deprecate dust-treshold config value

Browse Source 
Replace ambigious config value "dust-treshold" with a more clear
"channel-max-fee-exposure" exposure value. The old value is
deprecated and will be removed in the near future.
This commit is contained in:
ziggie
2024-10-12 20:29:08 +02:00
parent a040f8fafa
commit 7b2da94750
5 changed files with 54 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
sample-lnd.conf
View File

@@ -474,10 +474,32 @@
; propagation
; max-commit-fee-rate-anchors=10
; A threshold defining the maximum amount of dust a given channel can have
; after which forwarding and sending dust HTLC's to and from the channel will
; fail. This amount is expressed in satoshis.
; dust-threshold=500000
; DEPRECATED: This value will be deprecated please use the new setting
; "channel-max-fee-exposure". This value is equivalent to the new fee exposure
; limit but was removed because the name was ambigious.
; dust-threshold=
; This value replaces the old 'dust-threshold' setting and defines the maximum
; amount of satoshis that a channel pays in fees in case the commitment
; transaction is broadcasted. This is enforced in both directions either when
; we are the channel intiator hence paying the fees but also applies to the
; channel fee if we are NOT the channel initiator. It is
; important to note that every HTLC adds fees to the channel state. Non-dust
; HTLCs add just a new output onto the commitment transaction whereas dust
; HTLCs are completely attributed the commitment fee. So this limit can also
; influence adding new HTLCs onto the state. When the limit is reached we won't
; allow any new HTLCs onto the channel state (outgoing and incoming). So
; choosing a right limit here must be done with caution. Moreover this is a
; limit for all channels universally meaning there is no difference made due to
; the channel size. So it is recommended to use the default value. However if
; you have a very small channel average size you might want to reduce this
; value.
; WARNING: Setting this value too low might cause force closes because the
; lightning protocol has no way to roll back a channel state when your peer
; proposes a channel update which exceeds this limit. There are only two options
; to resolve this situation, either increasing the limit or one side force
; closes the channel.
; channel-max-fee-exposure=500000
; If true, lnd will abort committing a migration if it would otherwise have been
; successful. This leaves the database unmodified, and still compatible with the