-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Comments
how do you know the node does not have pending channels? is it your own node? |
Cause I talked directly with the owner on Twitter. |
Is this the error the other node is sending over the lightning transport? Where do you see this message? |
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 :( |
The error in the first image (
|
closing this as above sounds plausible enough. |
So I should just try to open the channel with a bigger mining fee ? https://imgur.com/a/7Lu07J3 |
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). |
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?
The text was updated successfully, but these errors were encountered: