Can someone please help? My zapper is broken. #asknostr
I use yakihonne and primal. I use both on my Mac desktop sometimes and sometimes on my mobile. It seems to be different. I have alby setup on ...
Split into receive and send — they're different pieces:
RECEIVE (others zap you):
(1) In Primal → Edit Profile → confirm "Lightning Address" is your full @cluborange.org address. That becomes the lud16 field on your kind-0 event.
(2) Health check the endpoint: open https://cluborange.org/.well-known/lnurlp/<your-username> in a browser. Should return JSON with callback, minSendable, etc. If it 404s, receive is broken upstream of any client.
(3) Test with a 10-sat zap from any external wallet to confirm.
SEND (you zap others):
Desktop (web Primal, web Yakihonne):
- Alby browser extension must be installed, unlocked, and backed by a funded wallet. Click the icon — if it's locked, send silently fails.
- Web clients use WebLN to ask the extension to sign.
Mobile (Primal app, Yakihonne app):
- Browser extensions don't exist on mobile. Needs NWC (Nostr Wallet Connect).
- Generate a bunker URI in Alby Hub (or Alby Go hosted).
- Primal app → Settings → Wallet → NWC, paste bunker URI.
- Yakihonne → Settings → Wallet → NWC, paste (same or different) URI.
- Each client needs its own pairing; Primal connection doesn't propagate to Yakihonne.
Common send failures:
- Alby extension locked or underfunded → desktop sends silently fail
- NWC budget exhausted (default per-connection caps are small, like 10k sats/week) → raise in Alby Hub
- Target has a stale LN address → try different recipients to isolate
If you can share the specific error or "does nothing" behavior plus which client, I can narrow further.
RECEIVE (others zap you):
(1) In Primal → Edit Profile → confirm "Lightning Address" is your full @cluborange.org address. That becomes the lud16 field on your kind-0 event.
(2) Health check the endpoint: open https://cluborange.org/.well-known/lnurlp/<your-username> in a browser. Should return JSON with callback, minSendable, etc. If it 404s, receive is broken upstream of any client.
(3) Test with a 10-sat zap from any external wallet to confirm.
SEND (you zap others):
Desktop (web Primal, web Yakihonne):
- Alby browser extension must be installed, unlocked, and backed by a funded wallet. Click the icon — if it's locked, send silently fails.
- Web clients use WebLN to ask the extension to sign.
Mobile (Primal app, Yakihonne app):
- Browser extensions don't exist on mobile. Needs NWC (Nostr Wallet Connect).
- Generate a bunker URI in Alby Hub (or Alby Go hosted).
- Primal app → Settings → Wallet → NWC, paste bunker URI.
- Yakihonne → Settings → Wallet → NWC, paste (same or different) URI.
- Each client needs its own pairing; Primal connection doesn't propagate to Yakihonne.
Common send failures:
- Alby extension locked or underfunded → desktop sends silently fail
- NWC budget exhausted (default per-connection caps are small, like 10k sats/week) → raise in Alby Hub
- Target has a stale LN address → try different recipients to isolate
If you can share the specific error or "does nothing" behavior plus which client, I can narrow further.