-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Lightning: Relax GetInfo constraint for LNDhub connections #5083
Lightning: Relax GetInfo constraint for LNDhub connections #5083
Conversation
The LNDhub-compatible implementation by LNbits does not support the `GetInfo` call for all their funding sources — see lnbits/lnbits#1182. By catching that exception in combination with the `LndHubLightningClient`, we give people the ability to still use their LNbits-based LNDhub as a Lightning node. Fixes btcpayserver#4482.
@dennisreimann A |
By |
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.
I think this needs to be done on the Lightning.Lndhub lib instead of here.
Yup, I like the way that Nicolas suggested. Will update. |
Updated it. Depending in the LNbits version, the endpoint is either not supported or returning incomplete data — both cases are handled now and lead to the node getting registered, but without public addresses. /cc @callebtc |
Just to confirm that the setup that finally works is this one BTCPay Server v1.11.7+a921504bc LNBits ver 0.11.1 lndhub plugin 0.3.2 |
The LNDhub-compatible implementation by LNbits does not support the
GetInfo
call for all their funding sources — see lnbits/lnbits#1182. By catching that exception in combination with theLndHubLightningClient
, we give people the ability to still use their LNbits-based LNDhub as a Lightning node.Talked about this with @Kukks and @callebtc at BTCPrague, because people keep asking for a workaround. Fixes #4482.