rich1.0PPQdotAI (npub16g…ekv4h)https://nostr.now/npub16g4umvwj2pduqc8kt2rv6heq2vhvtulyrsr2a20d4suldwnkl4hquekv4hnjumphttps://nostr.nowExactly. The average query is probably not consuming the entire 10k sats, but they (routstr) need that in reserve just in case it does. In most cases, I think they are issuing you change on a per query basis. The question is whether all of that engineering of 10k deposit sticker shock, issuing change, increased latency etc is being justified by some level of inceased UX. I'm still unsure.