Skip to content
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

Open
Fittiboy opened this issue Aug 22, 2021 · 8 comments
Open

Feature request: Support for lightning addresses #277

Fittiboy opened this issue Aug 22, 2021 · 8 comments

Comments

@Fittiboy
Copy link

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.

@Overtorment Overtorment transferred this issue from BlueWallet/BlueWallet Aug 22, 2021
@xraid
Copy link
Contributor

xraid commented Aug 23, 2021

Lightning Address is xtra sugar ontop of lnurl-pay and with the implementation needed lnurl-withdraw can also be had.

@lndhub-admin
Copy link
Contributor

lndhub-admin commented Aug 27, 2021

SEND LIGHTNINGADDRESS:

Making the issue back to BlueWallet Client repo in regards to send, where in the send screen for invoice has to implement a catch and identify a "lightningaddress : for ex.

"recipient@lightningaddress.fqdn"
and should then initiate a lnurl-pay request to :
"https//lightningaddress.fqdn/.well-known/lnurlp/recipient"

Then BlueWallet Client can send to "lightningaddress" with the already implemented lnurl-pay code.
BlueWallet Client need add where amemo in lnurl-pay screen becomes commentField in the lnurl-pay response.

RECEIVE LIGHTNINGADDRESS

To 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.

@Fittiboy
Copy link
Author

@lndhub-admin you‘re obviously @xraid, and you‘ve obviously written no code. Stop trying to steal bounties.
Provide code. No cheap talk. Just show the code you want to claim the bounties for.

@lndhub-admin
Copy link
Contributor

lndhub-admin commented Aug 27, 2021

You up for a bet on code made but not payed ?

Walk the Talk @Fittiboy

@Fittiboy
Copy link
Author

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?"
This is GitHub, not a gambling site. You've written other code before, but none has gotten merged yet.

Get your code merged -> claim bounty
(The key term here is merged)

@ncoelho
Copy link
Member

ncoelho commented Aug 27, 2021

Not sure what the issue is. But it would be nice to keep personal issues outside of the repo please.

@lndhub-admin
Copy link
Contributor

lndhub-admin commented Aug 27, 2021

I am making a Extension to LndHub without disturbing the core of LndHub,
in a repo outside of BlueWallet LndHub, if they se fit they can incorporate it.

I have committed to make a functionality, without mention of it being merged somewhere other then where i se fit.
The specification agreed on before i started work has not been honored by opposite party.

Else LndHub would have LNURL capabilities since Feb-2021.

@Fittiboy You accuse me of trying to steel bounties ?

@AaronDewes
Copy link
Contributor

@Dolu89 Implemented it (basically) in #291

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants