You're right, it was the wallet connection to the web app. so, double zap.

aargh! tried to zap that, failed. That's a good one!

The real cost is the time that we could have been spending building something else or doing something to help ourselves or others.

That line belongs to the user, not the coder. Systems need to provide enough options on both sides. A transaction is an agreement. What that agreement needs is validation in order to become commitment. It's the combination that builds trust.

What you seem to be talking about is User Interface, not the actual speed of the transactions. If the interface makes it too easy to hit the send button, of course the transaction is going to zap across the gap at the speed of light. That's how it is designed. But if the person making the purchase has to confirm, and the person receiving the payment has to confirm, that's UI. And it makes sense that nothing should move across the gap until both sides have confirmed the transaction. As far as AI payments back and forth, AI agents can confirm at the speed of light, or chips, or whatever. As long as both sides of the transaction have done the confirmation steps, let it roll. What am I missing?

Welcome to nostr!