Skip to content
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

i_know_what_i_am_doing option for closeallchannels #6743

Closed
hieblmi opened this issue Jul 16, 2022 · 5 comments · Fixed by #8526
Closed

i_know_what_i_am_doing option for closeallchannels #6743

hieblmi opened this issue Jul 16, 2022 · 5 comments · Fixed by #8526
Labels
channel closing Related to the closing of channels cooperatively and uncooperatively documentation Documentation changes that do not affect code behaviour lncli

Comments

@hieblmi
Copy link
Collaborator

hieblmi commented Jul 16, 2022

Background

Unintentional closure of all channels can have various negative implications for routing node operators.
A i_know_what_i_am_doing flag would mitigate unintentional closure of all channels.

Your environment

lncli version 0.15.0-beta

@lucasdcf lucasdcf added channel closing Related to the closing of channels cooperatively and uncooperatively lncli labels Jul 16, 2022
@yyforyongyu
Copy link
Collaborator

I think for closeallchannels, as the name itself suggests clearly, that you will close all your channels when using this command. And I'm not sure of the utility of adding that flag?

@hieblmi
Copy link
Collaborator Author

hieblmi commented Jul 17, 2022

From other tools I am used to have at least another check before performing critical operations. Maybe a "Do you really want to close all channels?" would be better than a flag?

@Roasbeef
Copy link
Member

Something basic here would just be a simple confirmation dialogue on the CLI (y/n).

@Roasbeef Roasbeef added the documentation Documentation changes that do not affect code behaviour label Jul 19, 2022
@ohenrik
Copy link

ohenrik commented Mar 6, 2024

Yes the closeallchannels says what it does pretty clearly, but... I was a bit quick, a bit tired and looked for the closedchannels command to see all closed channels... boom, I nuked my node. It's a monumental fail on my part and entirely my own. But.

The payinvoice command has a confirmation dialogue. I would say closeallchannels is a much more dangerous command and absolutely deserves to have such a confirmation dialogue. I'm not sure how much work it is to add one though. Maybe this is a good candidate for "good first issue"?

@guggero
Copy link
Collaborator

guggero commented Mar 6, 2024

Created a PR to fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
channel closing Related to the closing of channels cooperatively and uncooperatively documentation Documentation changes that do not affect code behaviour lncli
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants