[BUG] LNDhub extension return unusable `getinfo` response
See original GitHub issueDescribe the bug
The getinfo call simply returns bad auth
everytime, which breaks integrations like for us in BTCPay Server (see btcpayserver/btcpayserver#4414).
Expected behavior
Return valid information, which we can use to connect. For us that would mean having a list of uris
and a block_height
being set.
Issue Analytics
- State:
- Created 9 months ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
LndHub/rpc.proto at master
It provides separate accounts for end-users - LndHub/rpc.proto at master ... GetInfo returns general information concerning the lightning node including.
Read more >Bitcoin Project Release Tracker
This release fixes a series of bugs related to fee estimation with taproot outputs/inputs, a bug fix to ensure new channels are always...
Read more >Lnbits Lnbits Statistics & Issues - Codesti
Issue Title State Comments Created Date Upd...
Can't change funding wallet in .env file closed 1 2022‑12‑20 202...
duplicate ENV variable LNBITS_ALLOWED_USERS closed 0 2022‑12‑17...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Since LNbits works with many different backends, we don’t have that info universally. Example: People using LNTXBOT or Opennode as a backend.
It should basically pass up the info of the underlying LN node
getinfo
call. Also see the LND reference.