nostr:nprofile1qqsdmup6e2z6mcpeue6z6kl08he49hcen5xnrc3tnpvw0mdgtjemh0spzemhxue69uhhyetvv9ujuvrcvd5xzapwvdhk6qg5waehxw309aex2mrp0yhxgctdw4eju6t0qyt8wumn8ghj7un9d3shjtnwdaehgu3wvfskueqgxmmun an idea: instead of listing withdrawals, why not list incoming *payments*? That sounds much more natural to me. You can still add a flag that says "withdrawn" to indicate whether it was already requested by a withdrawing client.
That way you can also attach the LNURL comment to it without messing up batching things together?
Maybe it do list both. Adding withdrawals was necessary to avoid people loosing proofs, as npub.cash is now optimistic about it and marks all proofs as spent once you withdraw.
So replacing withdrawals will not be possible, but the history could list both ins and outs
You can always keep the "ins" around, so they'll never be lost
Sure, but how would the UX flow look like?
Let’s say I have received 50 zaps and want to claim them. I close the token by accident. With the withdrawal list I can resurface the token. How would that work if I see only “deposits”? I guess you could let the user reconstruct a token by selecting certain “ins” but how would they know which ones are really spent and which ones are marked as spent because they closed the token screen?
Maybe a misunderstanding here because it feels super simple to me. Please bear with me I have thought about this only a few milliseconds:
- give me a summary list of all incoming payments (id. time, comment, withdrawal state, etc...)
- let me query each payment token by id
- once queried, mark it "withdrawn"
Maybe:
- you can additionally have an endpoint that consolidates all outstanding payments into a single token like it does now (which is super useful imo). And then mark all of the ones you've consolidated as withdrawn
(Still has the same issue as it has today: the server doesn't tell you if it is spent (needs checking with the mint), only if it has been requested by the user)
