Thanks man, Iโll maybe roll with storing the private key for now and if one hasnโt been set then follow in zapplepay footsteps (backend creates it with its own key pair) and add the users handle to the event.
Iโm confident the private key never leaves the users device but allowing for both options would mean anyone that is cautious isnโt completely missing out
Whoops yes, 26. Oh thanks for the heads up Iโll try do some digging to see what was broke ๐ค
Negative, at the minute Iโm signing the pay request with the users own private key whilst Iโm in development. Iโve pretty much got NIP27 (delegate signing) done but no UI around it just yet so working on that at the moment ๐จ๐ปโ๐ป
Itโs come along way since last nights prototype.
๐๐ป yeah Iโm thinking the same, I need a default list of relays for this zap picker when first installed wasnโt sure if it was worth adding paid relays to the default list if they wouldn't accept the payment receipts.
Or are relay providers just manually adding wallet pubkeys to their accept list?
Anyone know if paid relays accept zap receipt events when signed by a key pair that hasnโt paid to publish to it?
Thank you to everyone that gave up a moment of their time tonight to help me test out the zap picker, I had 3 accounts that produced invalid invoices from around 30ish zaps sent, Iโll trail the logs tomorrow to get to the bottom of that, much appreciated ๐ซ
GN All
Your profile is missing a lightning address, once you add it let me know ๐ค
The bulk of the work is running on a web server, the shortcut makes a POST request to this server sending up the event, zap amount, relays etcโฆ the backend responds with the payment request and the shortcut picks up again by appending that PR to the wallet prefix config variable defined I the shortcut
Thereโs a few things needed before this could go out (unless self hosting) and itโs certainly not as snappy as just hitting the reaction button like zapplepay provides but I do miss the zap amount picker from earlier Damus releases so it scratches that itch
Once itโs stable, this is my first test run it seems to be going ok so far, Iโll need to tidy up some lud06/lud16 code I just smashed in over the last hour and then Iโll most likely build a quick web Ui for signing and publishing a delegate event so users wonโt need to expose their private key, the alternative might be nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s can look to implementing a shortcut intent which can sign events I could then hook into that in the shortcut rather than posting to what I call the zlap service
I had issues running Damus 1.5 on iOS 17 so forced to use 1.6 (no zaps) so I built an iOS shortcut which I will share soon which lets me create nostr zap requests without zapplepay or NWC. It isnโt tied to any specific client/app so long as I have a nostr event id at hand I can zap it
๐๐๐ Zap amount picker now up and running
Straight up zap requests โก๏ธ
Not using NWC or zapplepay/reaction events.
โ ๏ธ Iโm very likely to zap replies to test it further. 
Pretty bad video, doesnโt do it much justice when playing it back but the plan is to bring back the ability to select the amount of sats to #zap
See replies for full shortcuts script 
nostr:note1dl00kg9lmyhczrv8czxcqn8s4vtn880qz7xsv422fhjs0hfgjqyqvxr7cr
Built with apples tools (shortcuts and accessibility features) I would say thatโs a #zlap in the face, are they going to remove their own apps features now? I can double tap the back of my phone to #zap any nostr event (json) on my clipboard. I will likely add support for working with event ids and weburls soon too, the last little issue I have to solve is why Iโm not seeing the zap receipt published and shown in the client ๐ค any zap experts available with any #help or suggestions on what I may be missing? When generating the payment request Iโm including the nostr query param (uri encoded < json encoded < zap request) and the payment goes through successfully. http://nostr.build/av/fefe9e2f5594a0f73732d4f4494eef6d6afe242e7f0e3761b84c57e8307dba7b.mov
I have a dilemma, running 1.5 (4) for note zaps but Iโm suffering from the relay connection stability on iOS 17 that was fixed in (5) but also removes zaps. I may have to do another custom build at some point ๐ค
#zapathon โก๏ธโก๏ธโก๏ธ 
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s Iโve been having issues with relay connectivity again in Damus, same as last night. Iโm connecting to 8 relays, after about 2 minutes usage the connections drop and donโt reconnect, having to close and re-open every few minutes, is this a known issue?
Great to see an increase in adoption here! The flatlining on the zap receivers dataset is a bit of a worry though, I may be wrong here but it appears to me that more people are sending zaps week on week but most likely a large portion of the zaps are being sent to a smaller subset of nostr accounts, or I could be reading this chart wrong.
I think everyone needs to witness receiving a zap, itโs a wonderful feeling receiving value but also demonstrates the true power of bitcoin and L2 as something we can use today.
Maybe a community funded service running that listens for accounts with a lighting url set posting their first note we can zap them a sat or two, the community could fund the balance that would be used to send the welcome sats ๐ค