-
Notifications
You must be signed in to change notification settings - Fork 44
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
feat(rpc): CloseChannel call #1478
Conversation
lib/cli/commands/closechannel.ts
Outdated
import { CloseChannelRequest } from '../../proto/xudrpc_pb'; | ||
import { callback, loadXudClient } from '../command'; | ||
|
||
export const command = 'closechannel <node_identifier> <currency>'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The [force]
parameter is missing here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was actually intentional since it's a flag, I'm envisioning it's usage as just adding --force
to the command.
It looks like I can put closechannel <node_identifier> <currency> [--force]
here and then it'll work either by putting true
at the end of the command or --force
anywhere in the command, so that's what I'll go with.
49fc80e
to
fe6bba8
Compare
fe6bba8
to
380cb26
Compare
Would yo ustill want this for the bot for |
It would be nice to have. I will give this PR another review |
380cb26
to
f69fa7c
Compare
This introduces the ability to close channels through xud. Currently this is only implemented for lnd, and is implemented in a naive way that relies on the peer we are trying to close channels with being online and cooperative.
Closes #1471. Follow-ups are #1472 and #1476.
I've tested this fairly extensively to ensure we are handling the responses from lnd correctly and it's working well.