Optional Channel limits which are applied during channel creation. These limits are only applied to our counterparty's limits, not our own
Record Field | Description |
Full Usage:
ForceChannelAnnouncementPreference
Field type: bool
|
Set to force the incoming channel to match our announced channel preference in ChannelConfig. Defaults to true to make the default that no announced channels are possible (which is appropriate for any nodes which are not online very reliably)
|
|
The remote node will require we keep a certain amount in direct payment to ourselves at all time, ensuring that we are able to be punished if we broadcast an old state. This allows to you limit the amount which we will have to keep to ourselves (and cannot use for HTLCs).
|
|
Maximum allowed threshold above which outputs will not be generated in their commitment Transactions. HTLCs below this amount plus HTLC tx fees are not enforceable on-chain.
|
|
|
|
before a channel is usable the funding TX will need to be confirmed by at least a certain number of blocks, specified by the node which is not the funder (as the funder can assume they aren't going to double-spend themselves). This config allows you to set a limit on the maximum amount of time to wait. Defaults to 144 blocks or roughly one day and only applies to outbound channels.
|
|
|
|
HTLCs below this amount plus HTLC transaction fees are not enforceable on-chain. This settings allows you to set a minimum dust limit for their commitment TXs, Defaults to 546 , or the current dust limit on the Bitcoin network.
|
|
|
Full Usage:
MinMaxAcceptedHTLCs
Field type: uint16
|
The remote node sets a limit on the maximum number of pending HTLCs to them at any given time. This allows you to set a minimum such value.
|
|
The remote node sets a limit on the maximum value of pending HTLCs to them at any given time to limit their funds exposure to HTLCs. This allows you to set a minimum such value.
|
Static member | Description |
|
|