Well I imagine there will be OS level permissions and walls to break through. Bluetooth tends to ask questions like "X is trying to send you a file" which is good for security but bad for UX. Have you managed to work around all of that?

Actually one thing I noticed is that small delay in confirmation of receipt. This can give us the opportunity to get a full acceptance flow for online payments. So you send me ecash and from your end it is done, but for me, I haven't really accepted it yet. I trade it for a new ecash and if it works, I accept. If it fails, or if I don't want to trust that mint, I reject. I could also reject it maliciously of course. If I report the payment as failed, then you can trade the ecash for a new one and if it fails, then there's a problem. But in most cases you just take back the funds and payment is cancelled/rejected. The problem case is interesting. Without p2pk and a timeout, there is no atomic payment and even with, there is no proof of payment like we have on lightning afaik. Are there any protocols or flows to address them?

My understanding was that as you add trusted contacts, you can get asked less security questions. But before that, you want to accept connections etc.