Avatar
gudnuf
c67cd3e1a83daa56cff16f635db2fdb9ed9619300298d4701a58e68e84098345
I wasn't there but I'm here | prisms | plebdev | yoga | climbing | surfing | backpacking | holistic health |

in general yes, not sure about having a default though. potentially a wrapper around the existing cashu-ts api that adds storage functionality while keeping the core functions the same and accessible

my experience has been that proof management is the most bug prone aspect of a wallet... storing duplicate proofs, deleting proofs before a melt is confirmed, keeping spent proofs, not getting the change, etc.

also managing things like unpaid mint quotes is cumbersome

Replying to Avatar Kody Low

nostr:npub1nc0ynppqh37rtulr57xjqpzmfjp58xrd4ey8896ehn9j5flg33fszrz5pa's been working on and off on a better indexDB transaction abstraction that'll make doing ecash TXs from a PWA or webapp much more reliable, will also work for cashu since it's just generic KV! https://github.com/elsirion/webkv/blob/master/src/lib.rs

The default indexdb behavior is to commit the transaction as is whenever the event loop hits a network request, so for ecash transactions that might be hitting multiple mints it's probably causing the same issues we used to see in the Fedi PWA. webkv makes indexdb transactions operate the way everyone assumes they should work haha

🔥

Yes. It took a while to find all the edge cases where tokens may be lost.

It would be nice if cashu-ts had some sort of built in proof storage interface with options like browser storage or sql. With this a dev could simply initialize a wallet and call send/receive without having to worry about proofs at all.

Or relaxed nose breathing with long exhales for max relaxation

Casually eating whole lettuce leaves with a fork and knife in the background

The problem is nostr doesnt have enough posts like this