Adds InboundChannelsConfig configuration
#594
Conversation
|
I've assigned @tnull as a reviewer! |
This commit aims to give two new configurations for node runners that want to control how inbound channels are requested. - `reject_announced_channels_requests`: Enable user to reject any request channel for announced channels. - `minimum_channel_size`: Permits node runner to set a minimum channel size for remote peers to open channels.
a-mpch
force-pushed
the
2025-07-add-disable-and-min-amount-incoming-channels
branch
from
2479260 to
610b49b
Compare
|
🔔 1st Reminder Hey @tnull! This PR has been waiting for your review. |
|
🔔 2nd Reminder Hey @tnull! This PR has been waiting for your review. |
|
🔔 3rd Reminder Hey @tnull! This PR has been waiting for your review. |
Fixes partially #502
Context
When running a personal or business node would like to control how peers request channels either blocking all possible channels, announced channels or some channels given a minimum.
This is useful as operator to take care of how liquidity moves. Even more, if we acquired a channel LSP for specific reasons and don't want that liquidity to move.
Other example is when running a operative node (i.e, exchange / wallet) don't want to be full of tiny channels that could affect route finding.
Solution
Added a
InboundChannelsConfigconfiguration onconfig.rswith two parameters to reject channels or set a minimum channel size. In case that node runner wants to block all possible channels, it would mean to set theminimum_channel_sizeto a greater number.Questions
I was thinking that better approach is to have a "channels_config" and inside would have inbound (or policy / limits) and also de Anchors channel config.