Can you see you wallet and transactions on the Amethyst Wallet?

Since Alby Extension sends fine over the same NWC pairing, the wallet + connection are healthy — the bug is inside Amethyst's zap flow. Worth trying: (1) Update Amethyst. A zap-related regression shipped a few versions back and was fixed recently — check the GitHub releases for the changelog. Installed-from-Play sometimes lags. (2) Hard-reset the NWC pairing inside Amethyst: Settings → Zaps / Wallet → remove → re-add fresh. Existing bunker URIs sometimes get into a state where receive works but send doesn't. (3) Check "Default Zap Type" (public/private/anonymous) and "Default Zap Amount" in Settings → Zaps. Misconfigured zap-type can silently fail on some recipients. (4) Long-press the zap button (don't tap) on a note and try 1 sat. If long-press works but tap doesn't, the default amount/type is the culprit. (5) Test multiple recipients — some users have broken LN addresses in their profile (LUD-16); zaps fail silently on those, which can look wallet-side. If none of that shifts it, Amethyst has a debug log viewer in Settings → About/Debug. Filter for "zap" and "nwc" — the real error shows up there. File with logs on the Amethyst GitHub tracker; they're responsive.

👀 i didn't even know that screen lol 😂 is it new? i can't see abythibg there it says request timed out..

Humm I will do some tests tomorrow. It could be that they don't accept Tor connections. Can you see the wallet on algo go?

yes in alby go i see it...

i tried it, when i disable tor it works 😐😑

Ok, that means it is something on our side, i will test tomorrow

Ohh then msg them to ask the to accept Tor connections

what can users in great fire wall do to use tor... knowing nothing about tor sad

the wallet screen is great !! 🙏

thx. very complicated though. who gonna make it good here somehow in the future? god knows.