Sub-account spending limits via proxy: pin-less UX with bounded risk

Has anyone explored adding a daily (or per-epoch) spending limit to a proxy account — effectively creating a “hot wallet tier” that doesn’t require signing for every small transaction?

The idea

Polkadot’s proxy pallet already supports delegating specific call types to a sub-account. The missing piece is a value-bounded proxy: one that can submit balances::transfer calls autonomously up to a configured limit per time window, without prompting the parent account for a signature each time.

The parent account configures the limit and window once. After that, the sub-account spends freely within the allowance — any call exceeding the remaining balance is rejected at the proxy layer, not by the parent key.

Why this matters

For mobile and dapp use cases, requiring a signature on every micro-payment causes friction — but exposing the full account key to a less-secure environment isn’t acceptable either. A spending-limited proxy splits the difference: the parent key stays cold, the proxy key lives in browser storage or in mobile wallet app which could skip the pin prompt for it’s usage, and the worst-case exposure is bounded by the daily limit.

This can be built with Smart Contracts on the Hub now. At least for exploring designs and stabilizing it.
If we directly amend the Proxy pallet, not only is that a very slow process, but it also has a high chance of not meeting what users want in the end.