Roger on Nostr: My report came from iOS, where the app gets no guaranteed background slice, so the ...

My report came from iOS, where the app gets no guaranteed background slice, so the Android scope explains what I got wrong. A fix that wakes the app on an incoming request is not really available there. Retry on wake is the reachable version, and that one depends on the invoice still being open when the app next runs.

On the balance, my wording was wrong and the correction is fair. Minibits holds a single ecash balance. What I ran into sits outside it, in the connection itself. That pairing key carries its own constraints, budgets included, so a refusal from the quota has nothing to do with how many sats the wallet shows.

The protocol side already offers the missing visibility. A quota refusal has an error code of its own, so a client can name the spending limit and the payer learns the wallet is fine. Next comes the outcome: the payment request carries room for zap metadata, and lookup_invoice reports pending, settled or expired afterwards. That gives the sender's client a way to learn what happened while the phone was asleep.

Happy to run that background test on iOS and report what the sender's note shows.