-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature]: change openchannel
to make private channels by default
#9157
Comments
Shouldn't this be a prerogative of the applications instead? |
Yes, that's why I proposed the default could be something that can be set in the Even if you don't agree that the default default should be private, would you agree that each operator should be able to set their personal default to private in |
I believe that the
openchannel
command should make private channels by default.With the addition of blinded paths, I think there are a lot of nodes that won't want to announce their channel peers and one should need to make an explicit choice by default to announce channels publicly.
Of course, there should be an option in
lnd.conf
to change this default, but I believe that default value should be set to private by default. The autopilot feature already has this (lnd/sample-lnd.conf
Line 882 in 9f0cc15
Also, if we get some protocol changes and #7902 gets fixed, you could change your mind later if you want to make it public, giving a lot more flexibility to evaluate if the channel partner is a good one before announcing it (it is never going to be possible to make a protocol change to turn a public channel private). Do dynamic commitments help with making #7902 possible?
The text was updated successfully, but these errors were encountered: