Oddbean new post about | logout
▲ ▼
SLCW | 14 days ago (raw) | root | parent | reply | flag 
 I should look for kind 9734, right?
▲ ▼
Vitor Pamplona | 14 days ago (raw) | root | parent | reply | flag +1 
 9735. 9734 is the zap request. 9735 is the final receipt that should mark it as zapped.
▲ ▼
SLCW | 14 days ago (raw) | root | parent | reply | flag 
 Ok thanks. I'll get to work! I appreciate your help, as always.
▲ ▼
Vitor Pamplona | 14 days ago (raw) | root | parent | reply | flag +1 
 Also, check if your inbox relays aren't requiring auth, regardless if they accept posts or not. Some NWC services never even auth.
▲ ▼
SLCW | 14 days ago (raw) | root | parent | reply | flag 
 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.
▲ ▼
Vitor Pamplona | 14 days ago (raw) | root | parent | reply | flag 
 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?
▲ ▼
SLCW | 14 days ago (raw) | root | parent | reply | flag 
 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.
▲ ▼
SLCW | 14 days ago (raw) | root | parent | reply | flag 
 This is why I'm curious if this is me problem, or if it's a wider systemic issue.
▲ ▼
Vitor Pamplona | 14 days ago (raw) | root | parent | reply | flag 
 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
▲ ▼
SLCW | 14 days ago (raw) | root | parent | reply | flag 
 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.
▲ ▼
SLCW | 14 days ago (raw) | root | parent | reply | flag 
 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.