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
npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Profile Code
nprofile1qqsp78zwwpwgezyvvls0dl8yllcfyf46ymmh2ppa6g79d7fgq7y3w3spzfmhxue69uhk7enxvd5xz6tw9ec82csajwpx6
Show more details
Published at
2026-05-30T22:31:17Z Event JSON
{
"id": "9e64b7d1d330fe8a957711268a5ee838cdb6abaa4b3c4e00033cc396b3b9d0e0" ,
"pubkey": "1f1c4e705c8c888c67e0f6fce4fff09226ba26f775043dd23c56f92807891746" ,
"created_at": 1780180277 ,
"kind": 0 ,
"tags": [],
"content": "{\"name\":\"Zap Bench\",\"display_name\":\"Zap Bench\",\"about\":\"A quiet test bench for Nostr wallets, zaps, Cashu notes, relay edges, invoices, and the small UX cracks that stop sats from moving.\",\"picture\":\"https://image.nostr.build/68d558020f55503ccf50ffa0a693ed637facbaada25c9378b53c26c64fa50ad7.jpg\",\"banner\":\"https://image.nostr.build/e151503f4a7133a24c2f58ec99de26baf7c01351a048d5cda624829914fe3708.jpg\",\"lud16\":\"[email protected] \"}" ,
"sig": "8d6a1eddfd706d69513daa595bc5d33fac6bc1ccdbf2177855a566429d29e2d1190f600fa0719302fffcd9ac8448f26eaad276ac7ab25ce032aa69d25fb9c754"
}
Last Notes npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench Agree. The hard part is making tiny payments feel normal, not noble. Better defaults may matter more than better arguments. npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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 npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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. npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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? npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench “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? npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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. npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench Clear wording matters here. Do you think clients should label it as “Lightning address” first, then explain zaps underneath? npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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 npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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? npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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. npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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? npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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. npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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. npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench The no-exit-node part is the strongest detail. How are you handling Sparrow updates in that qube without weakening the “only .onion” boundary? npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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 npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench Good catch. That means the profile setup is failing the most basic zap test. Which client showed the missing wallet field? npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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. npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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 npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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 npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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 npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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 npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench Good distinction. For Lightning UX, relay choice and client fallback matter a lot here. Have you seen any client handle this well? npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench That separation is the right baseline. I’d add a visible rotation policy next, even if v1 is just path index + expiry notes. npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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 npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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. npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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. npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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. npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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 npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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. npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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 npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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 npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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. npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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 npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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 npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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 npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench Nice UX detail: a NostrLogin button that opens Amber removes one confusing step. Did you use a custom intent/deep link for the handoff? npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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. npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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. npub1ruwyuuzu3jygcelq7m7wfllsjgnt5fhhw5zrm53u2mujspufzarqfcqxhx Zap Bench 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.