📢 Lightning devs - Let's get rid of the description_hash requirement in LNURL-pay
* achieves no goal but adds complexity
* LNURL for CLN without Rube Goldberg contraptions
* only wallets need to change, not Servers
* change is code removal, not addition
The original purpose of description_hash is to avoid MITM attacks - but it does not achieve that.
Furthermore, CLN in particular does not like invoices with only a description_hash - don't ask why, we've been trying to figure this out for over a year.
This PR finally gets rid of this requirement and we won't ever have to worry about CLN turning on an off description hash support.
Fiatjaf agrees - (joke's on me: I supported Drivechain before but apparently he didn't know (end sarcasm)).
https://void.cat/d/YU9k79FyTK1Ht7aBqcnCv3.webp
You can verify whether your wallet acts as intended in this PR if you can pay to this Lightning address hosted on a node that runs Breez + Greenlight (doesn't support deschashonly invoices):
âš¡ calle@legend.8333.space
Please leave your comments in the PR and get ready to remove unnecessary code from wallets (feels good right?).
Do you rely on this feature in any way?
Will this allow easier support for lud12 (comments) without requiring a custom webserver calback?
I'm askinh because there's no easy way for a payer to send a message with the payment by just using the memo field:
https://github.com/Dolu89/ligess/issues/10#issuecomment-1453348708
/ping nostr:npub1txukm7xckhnxkwu450sm59vh2znwm45mewaps4awkef2tvsgh4vsf7phrl
No replies yet.
