Amount Limits
The Vault enforces spending limits through the Amount less than condition on a policy. A policy’s threshold caps the value of transfers it applies to; larger transfers fall through to the next policy (and are denied if none allow them).
How Amount Limits Work
Each policy can set an Amount less than threshold in a chosen currency — either a fiat currency (USD/EUR) or the native asset. Combined with the policy’s other match conditions (from wallet, blockchain, token, destination) and its Allow/Reject action, this expresses rules such as:
- Allow transfers under $10,000 to whitelisted addresses with 1 approval.
- Allow transfers under $100,000 from the Treasury wallet with 2 approvals.
- Reject everything else (default-deny).
Because policies are evaluated in priority order with first-match-wins, you build tiered controls by ordering policies from most specific (lowest amount, most approvals) to least specific.
Fiat thresholds are compared using a price valuation from the wallet service (configurable provider — e.g. CoinGecko or a static price source). The valuation applied to a transfer is recorded alongside it for audit.
Scoping a Limit to an Asset or Wallet
Because the amount threshold lives on a policy, it is automatically scoped by that policy’s other conditions. To cap only TRON USDT outflows, for example, set the policy’s Blockchain to TRON and Token to USDT and give it the desired threshold; other assets are unaffected by that policy.
Breach Behaviour
A transfer above a policy’s threshold does not match that policy. If no other policy allows it, the transfer is rejected at the policy layer before any signing begins, and the rejection (with the deciding rule) is written to the audit log.
There is no rolling-window / velocity limit and no per-period spend aggregation. Limits are per-transfer amount thresholds evaluated at submission time. To tighten or loosen a limit, edit the policy (an audited change).