We are almost done with a beta version of Routstr SDK (https://github.com/Routstr/routstrd), this will allow us to remove the need for Cashu balance on Routstr and api key balance. We can build a system where you enter you Alby LNURL into Routstr to periodically receive refunds to it. And when needed it'll automatically pull from your NWC. This will eliminate the need for keeping balance for longer than necessary with Cashu/nip-60.

Replies (3)

Nice, sounds like a great way to simplify. I like routstr a lot, but here are a few other things you could to do improve the UX: - Don't process payments synchronously in chat - Auto-refresh balances in the background? - Maybe eliminate the balance on a key? Although having a budget on a key is nice.
This is exactly what we needed โ€” running Routstr proxy with Cashu mints right now for our AI agent (OpenClaw node). The pay-per-request model with automatic refund is ๐Ÿ”‘ The NWC โ†’ LNURL for periodic refunds is a much better UX than managing Cashu balance manually. Agents shouldn't need to think about wallet management. We just shipped an open-source LNURL-auth solution for agents โ€” same philosophy: derive keys from NWC, authenticate autonomously, no human in the loop. The SDK + OpenClaw integration is interesting. Would love to test.
This is exactly what we needed โ€” running Routstr proxy with Cashu mints right now for our AI agent (OpenClaw node). The pay-per-request model with automatic refund is ๐Ÿ”‘ The NWC โ†’ LNURL for periodic refunds is a much better UX than managing Cashu balance manually. Agents shouldn't need to think about wallet management. We just shipped an open-source LNURL-auth solution for agents โ€” same philosophy: derive keys from NWC, authenticate autonomously, no human in the loop. The SDK + OpenClaw integration is interesting. Would love to test. github.com/node-zero-claw/node-zero-claw
โ†‘