Oddbean new post about | logout
 is anyone using the LNURLp plugin with LNbits for zaps? is the latest version of the plugin, version 0.5.0, working with zaps for you? i upgraded LNbits and the plugin yesterday and apparently my zaps are now broken. i can receive them fine, but they don't actually register with nostr. it sounds like the callback to nostr is not working as expected?  
 I wanted to find out about lnbits myself  
 I've been using LNBits for my Zaps for about a year and a half. It's worked great up until now. 
 You should have told us, we can fix whatever issues you have. 
 I am. Its been like this for me for the past 3 months. 

I receive the sats, but the confirmation does not show up. The only zaps i see on nostr seem to be ones coming from Damus users. (at least thats my theory). Would be happy to test with you since we have a good mix of devices between Damus/Primal/Nostur/Amethyst

Spoke to  @Ben Arc very briefly about this, but he is a busy person and i didnt want to badger him about this.

 
 Badger away, I'm forgetful more than busy.
Lnbitsers are looking into it now 
 Thank you sir.  
 If there is any help needed in testing.... able and willing. ill keep an eye on telegram. 
 Thanks man. I think Tal has actually fixed. Will link once reviewed, so we can test and get update pushed through 
 Awesome! 
 Amazing. Thanks Ben. You're a legend. 
 Hmm I wonder if mine shows now. I'm using 050. 
 sent you a 21 sat zap on this note. 
 Same but my client shows mine but I don't see yours 😔 
 amethyst shows it because it's cache. if you nuke cache you won't see it any longer. i don't see the zap on any other client that i've checked. so it looks like it's not working for either of us according to nostur, damus, primal, and cache clear amethyst. 
 😥 
 let's try round 2. I just updated to 0.5.3 🤞  
 I now see it and I have notifications in Amethyst about the zap! I forked the extensions repo and added 0.5.3 and the nwc plugin to the repo lists. 

To update your own you can simply replace the extensions.json file from your server settings with https://github.com/patrickulrich/lnbits-extensions/blob/main/extensions.json

I don't recommend doing this this though because you'll be relying on me to update for future updates to plugins and also trusting I don't feed you bad repos. Instead everyone should fork https://github.com/lnbits/lnbits-extensions and update your extensions.json to what you want included. Then replace the default extensions.json with your own address. 
 i guess this is round 3. just landed on 0.5.4 💣  
 doesn't look to be working on 0.5.4 release for me 
 Can you try and make another lightning address with the lnurlp plugin? I wanna check something. Don’t need to add it to your profile. Just let me know what the address is. Make sure to enable nostr zaps for it. 
 zaps@derekross.me 
 Everything looks fine from the outside. Prob bug with the plugin or LNbits. 
 https://github.com/lnbits/lnurlp/commit/efb2eef32371a2837c0377708d13bff915958f55

it did not in-fact fix zaps. 
 Oof reverting to 0.4.0 crashed LNBits 😂 
 My man just use your Strike lightning address to receive zaps 😂 
 Test zap plz sir. Got 0.4.0 working. 
 Zap went through, but no receipt published 
 Rage. Thank you. 
 oh it looks like that commit is from a newer release. gotta figure out how to manually get this version since it's not in the lnbits extension market yet. 
 I’d just wait cause you probably need this too

https://github.com/lnbits/lnurlp/pull/67 
 i hope this is pushed to prod soon so i can install this version via linbits. this is going to annoy me something fierce until it's fixed 😟  
 Your going to be more than annoyed if you get rugged because of the security vulns that @semisol talked about 😂 
 I wish he'd provide a writeup on that or link the existing note because its very possible it was fixed awhile ago 
 it’s more their track record; I have only explored a certain portion of their code only 

like 2 years ago, I had to annoy them for months before an SQL injection bug got fixed (it was simple also, they were passing field names from request body directly to the DB)

they also took a month of pestering to fix a bug that allowed draining Eclair nodes… with a hodl invoice (yes, you just wait 30 seconds)

their satsdice plugin had improper access control, meaning invoice keys meant to be receive only could drain wallets 
 semi 
 still using that insecure software? 😂 
 reminds me;  nevermute      .   (*semi*) 
 moistly 
 maybe this PR will fix the problem https://github.com/lnbits/lnurlp/pull/67 
 so glad, I've programmed the Nip57 myself against my own lnd 😁 
 seems like they don't send the kind 9735 to the correct relays. 
 So they're not using the zappees relays? Which ones are they using? 
 It's in the NIP57 Spec: Once the invoice is paid, the recipient's lnurl server MUST generate a zap receipt as described in Appendix E, and publish it to the relays specified in the zap request. 
 So they aren't?  
 Don't know, have no id of that missing 9735 😑  
 it was being sent to the relays, just not the correct kind. it's fixed now on v.0.5.6 
 🤝 Link pls, so I can compare notes? 
 t-y thread       collab(*_*) 
 Conceded and decided to use Strike as my Lightning wallet until the LNURLp plugin for LNBits is fixed. 
https://media.tenor.com/vZjt6-cM9bYAAAAC/rick-and-morty-rick.gif
nostr:nevent1qqsw2jjxjrh40tsr98dk0f3rn9w8ckae36pms5cuvfnffr3gx3z45jspzemhxue69uhkummnw3ex2mrfw3jhxtn0wfnj7q3q8ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqxpqqqqqqzmuakc7 
 Did you put in a bug report?  
 https://github.com/lnbits/lnbits-extensions/pull/414 
 I tested, it has same bug. Lads are looking into it now 
 I did not. I can later. Thanks. 
 DM me if you have any issues. I'll take a look tonight 👍 
 Im using... LNbits 0.12.10 with Pay Links (lnurlp) 0.5.0 since July

Its been working with zaps for me.

May be trottling and bot prevention issues with relays and if so, all you can control is the pruvkey/pubkey under which the zap receipt will be published from. 
 I'm now on 0.12.11. It was working fine with 0.12.10 and 0.4.4 previously. 
 I thought you didn't have all morning to monkey around with this? 😂 
 that's going to fixed soon! also, the zap receipt will be sent along with the payment webhook in the next release.
@talvasconcelos 
 it's already released, as of last night!! 

update the LNURL pay extension on your nostr:nprofile1qqs8u5uf0rd2p9wmdxxaznpn54tkq8wwspmljy0cjqw6jdgm5kv84dspzdmhxue69uhhqatjwpkx2urpvuhx2ue0kuktdg and all should be fixed + the receipt on webhook. 
 Thanks. Will do later today.