Egge (nprofile…vcku) what is the roadmap for npub.cash? I see good improvements with v2 and v3 in the codebase but looks like the production environment is still on v1.
calle (nprofile…f4lp) for NUT-20, have you guys decided whether clients discover/verify quotes against npub.cash or the mint? My understanding is that the mint has no by-pubkey discovery by design, and v3's /api/v2/wallet/quotes gives me the quote refs — but it's pull-only and assumes the server is up and honest when I ask. And there doesn't seem to be a way to discover all npub.cash servers out there. It locks my implementation against a fixed list of operators.
I guess npub.cash could just sign encrypted Nostr events to the receiving user that contains all quote references so that we can download them and check against the mint.
How about pushing encrypted quotes to the receiving user via Nostr? When you broker a NUT-20 quote, you could fire an encrypted event carrying the quote ref (quoteId, mintUrl, amount) to the recipient. Then a client like Amethyst discovers funds straight from the user's relays and verifies each ref against the mint — no dependency on the API being reachable, and the server's worst case shrinks to withholding (detectable), not custody.
Then we wouldn't need to hard code querying all npub.cash operators out there.
VitorPamplona / Vitor Pamplona
npub1gc…fnj5z
2026-05-30 15:52:04 UTC
Author Public Key
npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5zPublished at
2026-05-30 15:52:04 UTCEvent JSON
{
"id": "062c9945662921e96c5e01bf4b0fa0008d3bcf9ca01994df89629d7b8b16c405",
"pubkey": "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c",
"created_at": 1780156324,
"kind": 1,
"tags": [
[
"alt",
"A short note: nostr:nprofile1qqsdmup6e2z6mcpeue6z6kl08he49hcen5x..."
],
[
"p",
"ddf03aca85ade039e6742d5bef3df352df199d0d31e22b9858e7eda85cb3bbbe",
"wss://nostr-pub.wellorder.net/"
],
[
"p",
"50d94fc2d8580c682b071a542f8b1e31a200b0508bab95a33bef0855df281d63",
"wss://relay.damus.io/"
],
[
"r",
"https://npub.cash/"
],
[
"client",
"Amethyst"
]
],
"content": "nostr:nprofile1qqsdmup6e2z6mcpeue6z6kl08he49hcen5xnrc3tnpvw0mdgtjemh0spremhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet59uq32amnwvaz7tmjv4kxz7fwdehhxarj9e3xwtcpz9mhxue69uhkummnw3ezumrpdejz7qmvcku what is the roadmap for npub.cash? I see good improvements with v2 and v3 in the codebase but looks like the production environment is still on v1. \n\nnostr:nprofile1qqs9pk20ctv9srrg9vr354p03v0rrgsqkpggh2u45va77zz4mu5p6ccpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qgkwaehxw309a5xjum59ehx7um5wghxcctwvshsanf4lp for NUT-20, have you guys decided whether clients discover/verify quotes against npub.cash or the mint? My understanding is that the mint has no by-pubkey discovery by design, and v3's /api/v2/wallet/quotes gives me the quote refs — but it's pull-only and assumes the server is up and honest when I ask. And there doesn't seem to be a way to discover all npub.cash servers out there. It locks my implementation against a fixed list of operators.\n\nI guess npub.cash could just sign encrypted Nostr events to the receiving user that contains all quote references so that we can download them and check against the mint. \n\nHow about pushing encrypted quotes to the receiving user via Nostr? When you broker a NUT-20 quote, you could fire an encrypted event carrying the quote ref (quoteId, mintUrl, amount) to the recipient. Then a client like Amethyst discovers funds straight from the user's relays and verifies each ref against the mint — no dependency on the API being reachable, and the server's worst case shrinks to withholding (detectable), not custody.\n\nThen we wouldn't need to hard code querying all npub.cash operators out there.",
"sig": "6150df61620d9c3edc4bd17c5d463e809b35f3969fd1d8af072ac4aa8de08e27108871b36cd0ab525521e85df98cc27d51423f325e864fac17bae9625ae6ae94"
}