a thing that makes these methods a dead end for consumer payments is cash finality and the fact that fees are paid by the buyer. if you look at how consumers pay today (credit cards, cashback, BNPL) it's clear that they don't value privacy much and being debt-based has advantages for them. UX doesn't matter if consumers don't have incentives to switch. banks already have earned people's trust and there is usually a physical space you can go to complain, mints on the other hand..

a thing that makes these methods a dead end for consumer payments is cash finality and the fact that fees are paid by the buyer. if you look at how consumers pay today (credit cards, cashback, BNPL) it's clear that they don't value privacy much and being debt-based has advantages for them. UX doesn't matter if consumers don't have incentives to switch. banks already have earned people's trust and there is usually a physical space you can go to complain, mints on the other hand..

This video is really funny 😆 Give this video to a skeptic and they will never join us ever. I’m sitting here laughing out loud as it demonstrates all the issues we see everyday separately, so you do t really feel the pain, but here in one 5:30 video 😂 I’m still a cashu skeptic, this video might have convinced me of cashu a little more, paying for tokens does seem simpler in cashu on a technical level. But the video is gold. 🤣

I'm sure the @routstr guys are happy about constructive feedback

Show me an equivalent UI that is clean and easy for users to understand

I have four wallets: - Onchain onramp (strike) - Lightning (alby) - Cashu balance in routstr - Token balance for an api key It's like 2 or 3 too many

I have probably 20+, this example was just for illustration

Mint selection is very foreign to people. I don't mind this, I personally understand it and don't have issues, however I feel that having to explain this to users is the hard part. Perhaps I need better materials or explanations.

another standard with partial support, neat

This is incredible feedback. Thank you so much for doing this and using Routstr. Yes, I get how it is confusing for people not used to Lightning/Cashu/NIP-60. We'll work on improving this UX. We have thought about NWC being the primary source of funds. But it'd mean there's more delay as every transaction is an NWC -> Cashu -> Swap and also, the way pay per request works right now requires the current set up because for any model you're sending more than what it'd cost, like 2100 sats for GPT-5.3-Chat and you'll get 1950 sats back as you just spent 150 sats. This requires a wallet. Also, the reason why you signed Nostr events there is because we use a nip-60 wallet in the chat app, which stores your cashu in Nostr relays. This makes the app/balance available on multiple devices. We'll work on abstracting away all of this complexity from the user. cc: @e47d738e…47ab1078 Sorry about such a delayed response, I'll setup my agent to check Nostr for mentions of this account (I check my personal). I've been busy these past few days working on Routstr SDK (https://github.com/Routstr/routstrd) a daemon that runs on your machine and integrates itself with OpenCode, OpenClaw, etc. The benefit is that if one node goes down it automatically switches to the next one. And also that different nodes are better for different models. With built in Nostr features. - @redshift

Yes. Will have usage history in the SDK. Just fixing the last few bugs. 🐛 OpenCode dollar amount integration in the TUI requires a custom plugin. That’s something we can add a bit later. But you’ll get usage stats very soon. As things are moving at lightning speed, it might not make sense to put in the effort of integrating ourselves into every agent framework. Soon you might not be looking at the TUI at all. Thats why we’re thinking about generic per session costs for all kinds of agents.

that's exactly the point because the world you want can't exist