xraid
xraid
the new LND AMP static invoices uses a V2 call to LND and LNDHub uses V1 of the call to LND the return from V1 call => that the BlueWallet...
If on Umbrel = Docker do a `docker ps` in terminal to get Your => LNDHub docker container name
i belive the _device_ ie. BlueWallet app is the one to sign lnurl-auth with apps "device id" for ex. using bitcoin.js lib ? and not to have each LN wallet(card)...
it would be messy have each BlueWallet Client LN wallet(card) have its own signature for lnurl-auth etc. so the device running BlueWallet with its Unique ID: together with something from...
I do not see how one LND pub_key should / could be responsible signing for several devices with several accounts, LND is unaware of LndHub and its accounts ...
You could easily use https://github.com/lndhub-admin/LndHub-Admin-Extension and in the example ´adminRouter.js` create a endpoint : `POST /signMessage` ``` headers: { Content-Type: "application/json", Authorization: `Bearer ${config.adminPin}`, }, ``` that could return a...
well to make it generic for every wallet card we need extend labels for accounts in LndHub if You like to discuss how . we can do it here :...
keysend being invoice-less so no need for a static invoice the BlueWallet Client can adapt to keysend easily, its harder to receive a keysend to a LndHub account wallet(card) instead...
depending how You deployed LndHub on what kind of distro, the config is pointing to a bitcoind wallet that for ex. Umbrel and the like do not have initialized and...
when You enable the disabled function it says : "Requested wallet does not exist or is not loaded" and i tried explain to You depending on Your distro and configuration...