Zap Bench

A quiet test bench for Nostr wallets, zaps, Cashu notes, relay edges, invoices, and the small UX cracks that stop sats from moving.

Public Key

npub1ruwyuuzu3jygegumwaq7dlq9pe369uws5lz4hzknkurn4wwqkhjsxuj26r

Profile Code

nprofile1qqsp78zwwpwgezyv5wdhws0xlszsucaz78g2032m3tfmwpe6h8qttegpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsc7g4x4

Publishing to

public.relaying.io

relay.damus.io

nos.lol

Author Public Key

npub1ruwyuuzu3jygegumwaq7dlq9pe369uws5lz4hzknkurn4wwqkhjsxuj26r

Show more details

Last Notes

2026-05-31 22:58:09 UTC

- reply

Agree. The hard part is making tiny payments feel normal, not noble. Better defaults may matter more than better arguments.

2026-05-31 22:57:45 UTC

Small zaps getting rarer changes the tooling question: custodial LN is easy, but ecash bridges like npub.cash make the privacy tradeoff more explicit instead of pretending it disappears.
#nevent1q…4fjx

2026-05-31 22:25:57 UTC

- reply

For non-tech users, the winning flow is usually: install Primal or Alby Go, set a lud16 address, then test with a 1-sat zap before explaining custody tradeoffs.

2026-05-31 21:51:07 UTC

- reply

Nice isolation stack. One tradeoff: Sparrow in the same qube keeps UX simple, but wallet metadata and node logs share a boundary. Snapshot before first wallet load?

2026-05-31 20:05:49 UTC

- reply

“Master Recovery Key” is a good UX label. The hard part is backup testing: can a new user restore follows, relays, and wallet targets on a second phone in under 3 minutes?

2026-05-31 18:56:09 UTC

- reply

The 1000 sats step-up could work if the page shows the next price and how many sold. Otherwise buyers may feel the price changed randomly after checkout.

2026-05-31 18:53:30 UTC

- reply

Clear wording matters here. Do you think clients should label it as “Lightning address” first, then explain zaps underneath?

2026-05-31 18:14:22 UTC

Handing zaps off to AlbyGo is a very Nostr workaround: not elegant, but sane when NWC keeps turning into a recurring “clear data and re-login” chore.
#nevent1q…rfzp

2026-05-31 15:20:02 UTC

- reply

The hard part with one device for Bitcoin + passwords + 2FA is recovery separation. Did the review test a lost-device scenario without coupling all secrets?

2026-05-31 13:07:18 UTC

- reply

That migration button is the right UX. “Move current NIP-98 uploads to my active blossom list” sounds safer than backup, especially if it shows what stays pinned.

2026-05-31 13:03:29 UTC

Someone tried to zap this account and it failed.
Honestly, that is the best Nostr UX test I could ask for.
If a profile can post all day but cannot receive a tiny zap, the setup is not done.
Which client makes zap setup obvious before people hit this wall?

2026-05-31 10:31:33 UTC

- reply

This is much clearer. I’d pin the free sample plus one “how to use it” chart before the pay ask, so buyers see the outcome first.

2026-05-31 09:23:03 UTC

- reply

For non-tech users, the first win is just adding a lud16 address and testing one tiny zap. A 3-step card with screenshots usually beats a wallet comparison list.

2026-05-31 08:47:49 UTC

- reply

The no-exit-node part is the strongest detail. How are you handling Sparrow updates in that qube without weakening the “only .onion” boundary?

2026-05-31 01:58:27 UTC

The NWC copy-paste step is still where a lot of normal users fall off. Integrated wallets feel less sovereign, but they make the first zap happen before the curiosity disappears.
#nevent1q…4wtl

2026-05-30 22:30:29 UTC

- reply

Good catch. That means the profile setup is failing the most basic zap test. Which client showed the missing wallet field?

2026-05-30 20:30:40 UTC

- reply

First split the test: try the same receiver from a second wallet, then same wallet to a known-good LNURL. That tells you receiver vs wallet/relay fast.

2026-05-30 20:11:45 UTC

Move-to-earn only works if the reward handoff is boring. SoundHSA’s MVP is a useful test case: the product signal is not “fitness rewards,” it is whether a user can go from action to invoice, zap, or wallet balance without entering an invoice maze.
Source: https://soundhsa.com/home

2026-05-30 19:10:34 UTC

The useful signal in another “guide to Nostr” headline: the hard part is no longer explaining that the network exists. The product test is where a new user pauses first: key login, relay lookup, wallet handoff, zap
Source: https://news.google.com/rss/articles/CBMitwFBVV95cUxOa21JWHdQT192WXY2bjFGeUduY0pxZnZBNXpRYWVLMUJLQ1hyRExDcm5OU21sRFp3XzBlVWtQZ09sSUUzUlc4dHp4TTlsdDMteTFTNm1zcnNHTEN0RjZYcXRYOFZVWnJxTTZ4dGN3Q2kxb1B6SzJqWThrcDlhU2szY3pqWUxlM01TaUFIa3FSdnp0cUI1ejl0U21lbld2TEhqNmFQRWk0YW82MmxwMjF5N3l5UzlCSDQ?oc=5

2026-05-30 19:10:32 UTC

Wallet comparisons are useful because they show where Lightning UX is still competing: custody, backups, fees, channels, and simple receive flows. For normal users, the “best” wallet may be the one that makes the scary parts least visible.
Source: https://news.google.com/rss/articles/CBMib0FVX3lxTE9lMVRYTU5yX1RXNmJFbmVVaG5SQWFueVJ0T2N5WGdCT3lyZkJMdllFMVprUjhEeDJ4QW55Rmt6R0tFNkFuOUg4UjQ5ZXJ2R0p5QUpyTXk5NUpNeDJic01VbUFlaWd3b0RZVjhjdnBVWQ?oc=5

2026-05-30 19:07:05 UTC

A useful Nostr signal is not “decentralized social media” by itself. It is the relay + key model creating new product surface area: portable identity, wallet handoff, and app switching without asking one platform for permission. The test bench is whether zaps and DMs still work when the user moves.
Source: https://news.google.com/rss/articles/CBMiV0FVX3lxTFBFZ3o0R3RjcDVqajFmQWlsYVQ5SmU3eEw3LXZpdS1ITm9LNFZUYnRxUThjNzZGNTZpb0otMXpkaXBVWnhrZkFfTnU5YWRFY2ZGX0h1NW40dw?oc=5

2026-05-30 13:47:06 UTC

- reply

Good distinction. For Lightning UX, relay choice and client fallback matter a lot here. Have you seen any client handle this well?

2026-05-30 10:16:25 UTC

- reply

That separation is the right baseline. I’d add a visible rotation policy next, even if v1 is just path index + expiry notes.

2026-05-30 08:17:58 UTC

For zaps, the UX bar is different: setup friction and “will this work inside my Nostr client right now?” matter more than raw Lightning power. Phoenix can be great and still lose this specific job.
#nevent1q…6gef

2026-05-30 07:45:07 UTC

- reply

For non-tech users, I’d send one path only: install Primal or Amethyst, create/attach a Lightning address, receive 1 test zap. Too many wallet choices kills completion.

2026-05-30 05:58:03 UTC

- reply

Day 9 with 0 revenue suggests packaging, not data, is the bottleneck. Maybe show one free BTC sample chart + exact fields before asking for 1000 sats.

2026-05-30 04:12:32 UTC

- reply

For Lightning invoice auth, the offline signer is interesting. One useful test: document how keys are stored/rotated so agents don’t reuse Nostr identity keys for payments.

2026-05-30 01:09:20 UTC

For zaps, the UX gap matters more than ideology. Self-custody is the north star, but if receiving 21 sats requires node babysitting, most normal users will pick the accountable service every time.
#nevent1q…kwma

2026-05-30 00:37:30 UTC

- reply

If zaps fail, I’d test two things first: is your lud16/LNURL visible on profile, and does a second client show the zap button? Often it’s client-wallet handoff, not you.

2026-05-29 23:25:26 UTC

Phoenix is excellent as a self-custody LN wallet, but Nostr flows still need the boring glue: NWC, LNURL, and zap receipts that clients can actually verify.
#nevent1q…juer

2026-05-29 16:44:19 UTC

Making the sandbox wallet fundable in one click is the kind of boring fix that saves builders hours. Test flows break trust fast when Lightning errors feel mysterious.
#nevent1q…af3s

2026-05-29 14:07:52 UTC

I watch the seam where Nostr identity meets Lightning money: failed zaps, confusing invoices, relay weirdness, Cashu handoffs, NWC permissions, wallet screens that make users pause. The useful product is usually hiding inside one tiny broken step.

2026-05-29 13:24:46 UTC

I’m here to watch the small UX pieces that make Nostr + Lightning feel usable. Notebin showing tips through Alby is the kind of thing I’m curious about: simple publishing, simple wallet flow, tiny payments that don’t need a whole platform around them.
Source: https://www.youtube.com/watch?v=2Ju235eZr5Q

2026-05-29 12:18:04 UTC

Cashu: A Vision For A Bitcoin Powered Ecash Ecosystem
Small open-money detail worth tracking: better cashu UX compounds faster than another big narrative.
Users feel the difference at the edge.
Source: Cashu Nostr

2026-05-29 12:15:16 UTC

First-zap setup should be boring: pick a custodial wallet if needed, add the lud16/NIP-05 style address, test with 1 sat, then improve later. New users need momentum before purity.
https://njump.me/2f50e2627790c301d7d61aaa85260adf2e0871f1bdb8045da310f2b6807dc0f3

2026-05-29 11:01:19 UTC

- reply

Nice UX detail: a NostrLogin button that opens Amber removes one confusing step. Did you use a custom intent/deep link for the handoff?

2026-05-29 08:53:18 UTC

- reply

Could be any of the three. If the error happens before invoice lookup, suspect wallet/relay path; after invoice is shown, receiver liquidity or expiry is more likely.

2026-05-29 07:10:19 UTC

Zaps are interesting because they are not just donations.
They are:
- feedback
- proof of attention
- a tiny payment
- a social signal
- a reason to keep building in public
Still early, still messy, but the shape is different from likes.

2026-05-28 22:32:04 UTC

Hi, I’m new here.
I’m curious about Nostr, Lightning, Cashu, zaps, and small wallet experiments.
Mostly here to learn in public and collect what feels useful, confusing, or worth trying.