I’ve seen a similar issue with nostr:npub1wxl6njlcgygduct7jkgzrvyvd9fylj4pqvll6p32h59wyetm5fxqjchcan — manually approving works but if I configure auto-approval and a daily budget, it doesn’t seem to work. Maybe nostr:npub1u8lnhlw5usp3t9vmpz60ejpyt649z33hu82wc2hpv6m5xdqmuxhs46turz can help?
Trying out NWC on nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg for one-tap-zaps, but even after giving it a daily budget, it still requires me to go into the app to approve the requests.
Anyone else have this issue and find a fix?
#asknostr
Discussion
You need the app open for the payment to go through
Interesting. Here's what I did:
Opened mutiny. Opened Amethyst. Zapped you and got this:
It seemed to hang there and not complete.
Then went back to Mutiny and zap said it was pending. Went back to Amethyst and it finally showed the zap had processed.
Yes you need to open mutiny after you initiate the payment. Everything runs on your device so you need to open the app for the payment to go out
Cool. Makes sense. Not as convenient as NWC with a custodian like Alby, but way quicker than Zeus accessing my node through Tor.
nwc is a service you can run with lnd now on umbrel, start9, etc so you can get that alby experience on your own stuff
I think it’s the right functionality. I can give #zap without any problem in nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955 before it wasn’t possible. Tnk
Thanks clarifying.
Just tried it but it didn’t seem as reliable as the manual method. I reacted with 🤙 on about 10 notes and only one went through after opening the app and waiting for a couple minutes.
I guess I’m cool with the manual approvals since the app has to be opened anyways. Just thought I’d let you know.