nmfretz
commented
10 months ago Thank you for this suggestion and breakdown @Bosch-0! There is now an option to open a channel as private/unannounced fadb184b2e43ef1ac996210c3f25de1a6780f6a9, with an info popup describing the tradeoffs to users.
Umbrel should default to new channel opens being unannounced. Public channels should be opt in as they are primarily for routing node operators which the majority of lightning users are not.
When opening channels unannounced as default it would be handy to have a tool tip that pointed users who do want to be a routing node towards enabling a public channel open. Users who are looking to be routers would probably know the difference between public and unannounced though but this is a little extra life improvement. This is important because a channel needs to be closed and re-opened to change it's public status.
What benefits does this have?
More reliable network wide payments as you wouldn't have inefficiently allocated capital acting as de-facto routing nodes (I'd assume many Umbrel users are opening nodes to make payments and doing zero channel management). These channels also generally have low fees (the default) so get selected for routes more often than not which as the liquidity is not managed results in more payment failures for all users on lightning.
Users who open channels to just make payments (I'd assume most) wouldn't have to deal with all the UX implications of routing payments.
Some added privacy for users, they can still be revealed through probing but it makes it that little bit harder.
Some marginal reduction in gossip on the network limiting bandwidth requirements for node operators. This is likely going to become problematic with onion messages coming to lightning so limiting this as much as possible is a minor + to me.
We recently implemented this in Zeus: https://github.com/ZeusLN/zeus/pull/1002