Hey hivemind, I need your opinion on something:
If someone sends you a payment on npubcash v2 the server will hold the respective mint quote in its database for you to retrieve it at any time. There is no concept of "spent", the server will always return these quotes again at any time.
This simplifies server-side state management massively, because the server does not need to keep track of a quotes issuance-state. At the same time quotes can never be lost that way (even if clients loose them).
To avoid redundant traffic clients can specify a "since" param, essentially letting the server know "hey, the last claim you gave me is timestamp X, I am only interested in stuff that happened since then".
I wonder if I should add a "spent" endpoint for a client to let the server know "I have redeemed this quote, you can now safely mark it as spent". This would be only a convenience feature for clients to reduce the amount of redundant data.
Egge /
npub1mh…uc226
2025-05-12 06:45:45
Author Public Key
npub1mhcr4j594hsrnen594d7700n2t03n8gdx83zhxzculk6sh9nhwlq7uc226Published at
2025-05-12 06:45:45Event JSON
{
"id": "95849d7647959dcccdcf5715f58a7f1921d204fd3a035ea3272e84688171c2ce",
"pubkey": "ddf03aca85ade039e6742d5bef3df352df199d0d31e22b9858e7eda85cb3bbbe",
"created_at": 1747032345,
"kind": 1,
"tags": [
[
"r",
"wss://e.nos.lol/"
],
[
"r",
"wss://nos.lol/"
],
[
"r",
"wss://nostr-pub.wellorder.net/"
],
[
"r",
"wss://nostr-verified.wellorder.net/"
],
[
"r",
"wss://nostr.bitcoiner.social/"
],
[
"r",
"wss://nostr.cercatrova.me/"
],
[
"r",
"wss://nostr.einundzwanzig.space/"
],
[
"r",
"wss://nostr.land/"
],
[
"r",
"wss://nostr.mom/"
],
[
"r",
"wss://nostr.wine/"
],
[
"r",
"wss://nostr21.com/"
],
[
"r",
"wss://relay.damus.io/"
],
[
"r",
"wss://relay.primal.net/"
]
],
"content": "Hey hivemind, I need your opinion on something:\n\nIf someone sends you a payment on npubcash v2 the server will hold the respective mint quote in its database for you to retrieve it at any time. There is no concept of \"spent\", the server will always return these quotes again at any time. \n\nThis simplifies server-side state management massively, because the server does not need to keep track of a quotes issuance-state. At the same time quotes can never be lost that way (even if clients loose them).\n\nTo avoid redundant traffic clients can specify a \"since\" param, essentially letting the server know \"hey, the last claim you gave me is timestamp X, I am only interested in stuff that happened since then\".\n\nI wonder if I should add a \"spent\" endpoint for a client to let the server know \"I have redeemed this quote, you can now safely mark it as spent\". This would be only a convenience feature for clients to reduce the amount of redundant data. \n\n",
"sig": "54ac544cc26dd7a10f0d6979ee124398fe68e5b1897f8e8ba9a54aa8bf31dbc2d7def45f97a90734d39baecaff14137b5b890213266186cdc6fd29885efc9a77"
}