of course we all should be using bolt12 instead of LNURL.
not all wallets support it, but the most importants do
Discussion
Just need a way to include a some data (a zap request nostr note) when fetching a bolt12 invoice. Not sure if thats possible nostr:npub179e9tp4yqtqx4myp35283fz64gxuzmr6n3yxnktux5pnd5t03eps0elz4s
With lnurl we include this in the deschash (cln stores the original). So we can retrieve it when the invoice is paid and then we can send the zap.
Or even if we had a payer signature or a signature from the lightning node. We just need some way to verify the zap was initiated by a pubkey and a way for clients to verify it was from the designated lightning node that sends the zaps.
can it be just a field?
user enters its own bolt12 and then its p2p and anonymous
You can use the payer_note field during invoice fetching to put some data in the invoice
hmm ok will try that
testing zaps for this note… we made six attempts to⚡zap this note, at daywalker@noserver4u.de, over a period of about 2 hours. six of the zaps were successfully paid... please check for 6 satoshis received. however, we did find that only four of the payments produced zap receipts in time for our server to recognize them. this is a problem because the user who zapped you would not see an active ⚡icon after zapping. they might think the zap failed, and therefore might not zap you again.... also.... your average zap time was 12096ms (12.1 seconds). we consider this zap time slow... if possible, zaps should be confirmed in under two seconds. (if time is too slow, other nostr users might think your zaps are broken, might not zap you again.) if you wanted to fix this... you could try getting a free rizful lightning address -- https://rizful.com ... if u get it set up, pls reply here so we can do this ⚡zap test again.
Rusty just published a spec for BOLT 12 proof-of-payment which would form the basis of this like two weeks ago.
lets gooo
Maybe wouldn’t even need a full note if it can just be a signature from their nostr key
Sadly it’s a bit more complicated. To avoid making all lightning nodes speak nostr, you probably just want the PoP scheme, which is (a) enough to prove the BOLT 12 invoice came from the public BOLT 12 offer in the profile, (b) the payment preimage (and matching hash in the invoice), (c) the payer key signing the nostr zap info (and matching payer pubkey in the invoice).
There’s a corresponding new PoP field in BIP 321 with the intention of being able to just paste/open a BIP 321 with a BOLT 12 offer (and nostr metadata requesting the PoP) and then once the payment completes the wallet can automatically jump back to the nostr client with the PoP provided.
All a bit off of wallet support, of course, but step one is getting the note type defined and validation in place in clients.