Oddbean

▲ ▼

 I disable tor for money operations, so that's not an issue for me, but I agree that zapping in Amethyst feels slower than in Primal, or Nostrudel. But that may be an illusion because Amethyst displays that little purple progress wheel that goes around, and then hangs for a bit before zap is completed while Primal and Nostrudel immediately register the zap visually while the zap completes in the background.

▲ ▼

 Usually when the zap circle hangs in the last 5% of so, it means that Amethyst is still waiting for the NWC wallet to reply with the successful package OR the zap event to show up. Amethyst requests the zap event to be sent to ALL of your inbox relays. So, you can watch if the event gets there as well.

▲ ▼

 So it could be a problem with my inbox relays? Should I add the coinos.io relay to my inbox config? I'm just confused why it works quickly and without problem o Primal, but the same NWC connect string in Amethyst keeps failing.

▲ ▼

 Does it fail sometimes or absolutely all times? 

Do you see the zap event on Amethyst after primal completes?

▲ ▼

 I should look for kind 9734, right?

▲ ▼

 9735. 9734 is the zap request. 9735 is the final receipt that should mark it as zapped.

▲ ▼

 Ok thanks. I'll get to work! I appreciate your help, as always.

▲ ▼

 Also, check if your inbox relays aren't requiring auth, regardless if they accept posts or not. Some NWC services never even auth.

▲ ▼

 None of them require auth (42). I just checked my personal relay.tools relay which is one of my configured inbox relays, and it's got no entries for kind 9734 or 9735.

Additionally, I tried adding relay.coinos.io to my public inbox config, and I'm getting the same result: the purple wheel gets to about 95% complete and it just hangs. Checking my coinos.io wallet, there's no corresponding zap transaction. And checking my personal relay records show no corresponding 9734 or 9735 entries.

Do you know if any other coinos.io users have successfully zapped via NWC in Amethyst? I think it would be helpful to know whether this is a systemic issue, or some weird thing specific to me.

▲ ▼

 Wait, does it get to 95% and you don't see any lightning payment on coinos at all? Then, there might be something wrong with the request itself. Or maybe a budget limitation that was setup on coinos?

▲ ▼

 Yes that's correct. The wheel gets to about 95% complete (about the 11 o'clock position) and it just hangs. Not indication of any communication with Coinos.io, no corresponding zap entries in my inbox relays. I don't think it's a budget issue with coinos.io because I can immediately paste the same NWC connect string into Primal and it zaps just fine.

▲ ▼

 This is why I'm curious if this is me problem, or if it's a wider systemic issue.

▲ ▼

 This other user seemed to have fixed it. But his issue was different. The zap wasn't arriving because of the amount of inbox relays and limits of coinos relay lists. 

nostr:nevent1qqsz3q7ja09thcnq0s56hk22dgrg6hlqs00wegveng6kvf8alr89v7gppemhxue69uhkummn9ekx7mp0qgs8efvwljfdwa0qynp7n9dhqacf3llucdqtm9ge8kjv0dt40yw586grqsqqqqqp09f6fv

▲ ▼

 Yeah, that's different from me because I only have 3 inbox relays defined; nostr.land, relays.diggoo.com, and my personal inbox/outbox relay from relay.tools. And I just added relay.coinos.io to see if that made a difference.

▲ ▼

 So it looks like the problem was on my end after all. Turns out my system DNS blocker was interfering with the zaps. I exempted Amethyst from the DNS blocker and it's now working fine.

▲ ▼

 I only see it hang when my albyhub isn't running on my laptop

▲ ▼

 Yep, that is what should happen in such cases. 🚀