-
Notifications
You must be signed in to change notification settings - Fork 204
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
Add support for lnurl-auth #264
Comments
Im fully support this. Bluewallet my favorite wallet but Im using BLW for LNURL Auth |
I second this addition, a feature seriously needed as no application on iOS currently supports this! |
maybe can use BlueWallet Client Unique ID : as linkingPrivKey |
This need be implemented at BlueWallet Client for lnurl-auth against services exposing lnurl-auth functionality for devices. LndHub could also in future need / use auth with lnurl-auth . to login to some service exposed other then the now in place auth for user.wallet.accounts. |
i was thinking implement first sign/verify on lndhub's side (for each user) to fully conform to lnd's implementation |
LND signs with pub_key, LndHub could make something with a mix userid for account. while considering : lnurl-auth is not limited to the signage from device on the service provider side, it is more the client that need sign and BlueWallet could do that with a special bitcoinjs key used in parallel with device unique ID. for LndHub hand out signage for each LN (or BTC) wallet account(card) would be messy for user - its rather the device that should be identified to a lnurl-auth service without bind any account in a BlueWallet device, still be able auth against a lnurl-auth service. |
@Overtorment any word on the sign and verify? I've created an issue about it #303 |
Are there any plans for implementing lnurl-auth? I think it'd make a great addition to the wallet feature-set.
The text was updated successfully, but these errors were encountered: