Idea: LNURL #1516
Replies: 1 comment 5 replies
-
|
This will be hard/impossible to implement securely since to my knowledge LNURL responses aren't signed using a scheme that lends itself to be run as a threshold scheme. For LNURL Pay recurring invoices to be secure the initial LNURL would need to commit to a pub key with which the generated invoices need to be threshold-signed (and this is widely enforced by clients). Currently LNURL's security model depends on TLS/PKI and assumes that users are talking to a single server that is trusted (which doesn't exist in Fedimint's security model). Unless LNURL has been or will be patched this way BOLT12 seems the better alternative #1507. |
Beta Was this translation helpful? Give feedback.
-
|
For the record, not supporting LNURL means not supporting Lightning Addresses. Sounds like either adapting BOLT12 to lightning addresses or patching LNURL are the way to go. I think not having support for Lightning Addresses is hugely detrimental for the UX/UI of fedimint users. So if its doable then it should be added. |
Beta Was this translation helpful? Give feedback.
-
|
Bolt12 will enable an improved version of LNURL that doesn't require a web server request per payment. Instead, a one-time web server request can be made to receive a bolt12 offer (a static, reusable payment identifier). Client software can then easily map that bolt12 offer to whatever UI makes sense for the application (a nym user name, a real name, a phone #, a nostr pubkey, etc.). This address the privacy and censorship concerns around LNURL. |
Beta Was this translation helpful? Give feedback.
-
|
Question. I'm not sure where the latest documentation is on how fedimints will run lightning nodes. Apologies. But based off of eric's comment, it sounds like each lightning payment will need to be signed by multiple members in the federation? |
Beta Was this translation helpful? Give feedback.
-
With BOLT12, the federation would be able to turn BOLT12 offers into BOLT12 invoices while end-user is offline. This is possible because the offer contains a schnorr pubkey, and the federation can produce signatures for this pubkey. This isn't possible with LNURL because it contains no such pubkey. |
Beta Was this translation helpful? Give feedback.
-
|
More progress on BOLT 12 / DNS / human-readable names / Lightning Address compatibility: bitcoin/bips#1551 |
Beta Was this translation helpful? Give feedback.
-
LN-URL for federation guardians and for users.
Also add Lightning Addresses so that pay-to-email works.
Beta Was this translation helpful? Give feedback.
All reactions