-
Notifications
You must be signed in to change notification settings - Fork 208
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
Feature request: Support for lightning addresses #277
Comments
Lightning Address is xtra sugar ontop of lnurl-pay and with the implementation needed lnurl-withdraw can also be had. |
SEND LIGHTNINGADDRESS:Making the issue back to BlueWallet Client repo in regards to send, where in the send screen for "recipient@lightningaddress.fqdn" Then BlueWallet Client can send to "lightningaddress" with the already implemented lnurl-pay code. RECEIVE LIGHTNINGADDRESSTo be able payto a "lightningaddress" ie. recive to a LndHub account we will need implement lnurl-pay and be able label accounts. This is work i made but not finalized, the communication relating to bounties of lnurl-pay and lnurl-withdraw has been halted. when bounties is settled in full, i would then populate the https://github.com/lndhub-admin/LndHub-LNURL-Extension repo. |
@lndhub-admin you‘re obviously @xraid, and you‘ve obviously written no code. Stop trying to steal bounties. |
You up for a bet on code made but not payed ? Walk the Talk @Fittiboy |
Are you not seeing the irony, @lndhub-admin? I'm asking you to walk the talk, and you reply with "walk the talk?" Get your code merged -> claim bounty |
Not sure what the issue is. But it would be nice to keep personal issues outside of the repo please. |
I am making a Extension to LndHub without disturbing the core of LndHub, I have committed to make a functionality, without mention of it being merged somewhere other then where i se fit. Else LndHub would have LNURL capabilities since Feb-2021. @Fittiboy You accuse me of trying to steel bounties ? |
Lightning addresses are a natural extension of the lnurl-pay scheme.
They are described here and here, and sending should be fairly simple to implement.
The text was updated successfully, but these errors were encountered: