Exactly, and the payment is push instead of pull, like in Lighting making it a lot easier to implement.
Pretty sure it could be built very easily using this lib: https://github.com/cashubtc/cashu-js
I thought about using LN for monetizing API access, but this sounds better and achieves the goal to reduce roundtrips (compared to „create invoice for every request“)!
If I understood Cashu correctly, you can „top up“ a balance with the first LN invoice (say, 1000 sats), and then send 10 requests using 10 sats worth of ecash?
https://twitter.com/mrlukelukasson/status/1529192648015331330?s=46&t=8YH8IlzSo8cWrg_G3bi8Xg
Discussion
Jesus Christ!
And you don’t even need to handle the „balance“ in the background as I would have needed to do in my thought exercise.
You already solved this via Cashu itself, right ?! 👀
There is no balance in Cashu 😘
Let's build it! Join us: https://t.me/CashuBTC
⚡️⚡️
lnbc210n1pjqpetwsp583sjrcvz8h0xzue49rc74lterymd655j07jgaev8clekxlczkc5spp5ykv73yz3g7q49uzpg898ykxcp5g52eqgyld7zhux9wl8updl2wasdqvffhkkjr0v3kqxqzjccqpjrzjqfdwgqn4luevj3s75lm94fav3ndlswq56tva93qzychaea5l68eagza5eqqqjmgqqyqqqqqqqqqqqzcq9q9qyysgq8r98mydhdh2ajkufa4gsr7uc0axk052xxfpgr7nn27jplgzh267hvj8e4cvltskjyafcc574t4z4vuyhk4ngnw20zskm39lhmv9ntfsqxfyv76
Thank me later
That’s the point 😃
The first LN invoice represents the „balance“ (if compared to my thoughts) and you send ecash as long as you have any and then get new ecash tokens with the next LN invoice.
Thank me later