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

Include channel ID in lncli pendingchannels #5575

Open
C-Otto opened this issue Jul 27, 2021 · 6 comments
Open

Include channel ID in lncli pendingchannels #5575

C-Otto opened this issue Jul 27, 2021 · 6 comments
Labels
beginner Issues suitable for new developers help wanted P3 might get fixed, nice to have rpc Related to the RPC interface

Comments

@C-Otto
Copy link
Contributor

C-Otto commented Jul 27, 2021

Background

See #5574 for more background.

I force-closed a channel and now have to wait for my funds to arrive in my wallet (limbo). This is fine and it works as expected.

The channel is listed in lncli pendingchannels, but this output does not include the channel ID. As I derive certain statistics for my channels based on the channel IDs, I cannot do this for pending (force closed) channels. As a result, the numbers for such channels just drop to 0, messing up my statistics. As soon as a closed/closing channel is fully closed and the channel ID appears in lncli closedchannels, I guess the corresponding number will jump back up, causing more confusion.

Your environment

  • lnd 0.13.1 with some patches
  • Linux server 4.19.0-14-amd64 Fix name typo in README #1 SMP Debian 4.19.171-2 (2021-01-30) x86_64 GNU/Linux
  • bitcoind 0.21.0 (bitcoin core)

Steps to reproduce

Force-close a channel with local balance that will be returned after the time lock. Run lncli pendingchannels.

Expected behaviour

The channel ID appears in lncli pendingchannels.

Actual behaviour

It does not show up.

@carlaKC carlaKC added beginner Issues suitable for new developers rpc Related to the RPC interface help wanted labels Jul 27, 2021
@ErikEk
Copy link
Contributor

ErikEk commented Jul 27, 2021

I can fix this.

@ErikEk
Copy link
Contributor

ErikEk commented Aug 1, 2021

@C-Otto I've made a pr. Sorry for the delay. If it doesn't get merged, for whatever reason, you have to do a lookup based upon an internal list of channel_point entries instead.

@Roasbeef Roasbeef added the P3 might get fixed, nice to have label Aug 31, 2021
@C-Otto
Copy link
Contributor Author

C-Otto commented May 24, 2022

The channel point is included, which is enough to identify the channel. With this information I was able to work around my intial issue. As such, I don't mind if this will be closed ("won't do").

@guggero
Copy link
Collaborator

guggero commented Jun 1, 2022

Closing as per above comment and #5592 (comment).

@guggero guggero closed this as not planned Won't fix, can't repro, duplicate, stale Jun 1, 2022
@LNBIG-COM
Copy link

Hello,

Can I ask to open this issue again?

I have described my explanation here

@guggero
Copy link
Collaborator

guggero commented Sep 18, 2023

Re-opened the PR in #8000.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
beginner Issues suitable for new developers help wanted P3 might get fixed, nice to have rpc Related to the RPC interface
Projects
None yet
Development

No branches or pull requests

6 participants