xraid

one can call into the LNDHub API with the credentials for account and get balance etc. if a user lost his account, they can create a new account and issue...

try use lncli on LND machine : `lncli decodepayreq ` `lncli lookupinvoice ` `lncli lookupinvoice | grep state` - "state": "OPEN", - "state": "SETTLED", and maybe make a script of...

You could also try use the API call : GET LndHub-URL/decodeinvoice `{ invoice: }` that would return status of decoded invoice string

For a quick MVP of above described functionality one could do the following --takes 10 minutes. 1) Copy folder of a already verified to run 'lndhub' `cp -r lndhub lndhub-invoice-only`...

iirc when passing in `description_hash:` one lose the `memo:` and `description:` fields i would recommend leave LndHub as is and create a side microsevice for lnurl related extensibility using the...

i made withdraw and pay with existing LndHub calling `/addinvoice`that sets `{ memo, value }` so i can not follow in Your reasoning ... please expand

correct in as "Thus LndHub currently can not be used as a backend for an lnurl/lightning address service." that is why one should use a separate microservice for extending LndHub...

also BlueWallet need be able read memo for presentation in its UI ?, whereas with `description_hash` is not really readable ! ...

`metadata:` in tag: "payRequest", can be anything ? as long as lnurl can later verify it itself make invoice with a hash in metadata: --later verify the metadata: is payed...

it is possible use a NEW endpoint in LndHub either running in same memarea or as a microservice in parralell with LndHub where service runs with separate :port, using a...