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

Number of pending channels exceed maximum #7657

Closed
tolsadus opened this issue Feb 11, 2022 · 8 comments
Closed

Number of pending channels exceed maximum #7657

tolsadus opened this issue Feb 11, 2022 · 8 comments

Comments

@tolsadus
Copy link

Can't reproduce this with other lightning wallet, but it seems that when I try to open a channel with the node 03f3297397c8f5f685a562847611e20d15f56d6aaabc4d808a6e04e631dea6e612 I keep getting that error. (even if the node doesn't have pending channels)

No issues when using Zap for exemple. Am I missing something here?

@ecdsa
Copy link
Member

ecdsa commented Feb 12, 2022

how do you know the node does not have pending channels? is it your own node?

@tolsadus
Copy link
Author

Cause I talked directly with the owner on Twitter.

@SomberNight
Copy link
Member

Number of pending channels exceed maximum

Is this the error the other node is sending over the lightning transport? Where do you see this message?
Can you share the full error text/log?

@tolsadus
Copy link
Author

This message show up when trying to open a channel with this node. Not sure on the node side if I can ask him full details, but that's as far as I can see :(

https://imgur.com/a/Wp6TynZ

@spesmilo spesmilo deleted a comment from dangvietquang Feb 15, 2022
@spesmilo spesmilo deleted a comment from dangvietquang Feb 15, 2022
@SomberNight
Copy link
Member

SomberNight commented Feb 15, 2022

The error in the first image (RemoteConfig.dust limit too low: 354 sat) is #7541
The second error (Number of pending channels exceed maximum) could simply be a consequence of the first one:

  • we initiate a channel-open open_channel
  • other node sends accept_channel
  • we see they sent a too low dust limit and abort
  • they keep waiting for us to proceed until some timeout, during which this counts as a "pending channel"
  • if user now tries to open a channel again, remote might see too many pending channels

@SomberNight
Copy link
Member

closing this as above sounds plausible enough.
though note that fix for referenced issue is not released yet :/

@tolsadus
Copy link
Author

So I should just try to open the channel with a bigger mining fee ? https://imgur.com/a/7Lu07J3

@SomberNight
Copy link
Member

No, #7541 is about a dust limit parameter negotiated for the life of the channel to be used for later txs (e.g. force-close).
lnd started setting it to a very low number by default which electrum 4.1.5 considers not safe.
The master branch of electrum has the acceptance-threshold lowered so that lnd's new default is accepted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants
@ecdsa @tolsadus @SomberNight and others