Skip to Content

Amount Limits

The Vault enforces spending limits through the Amount range condition on a policy: a minimum and a maximum for the amount of a single transfer. A policy applies only to transfers whose amount lies within its range; other transfers fall through to the next policy (and are denied if none allow them).

How Amount Limits Work

Each policy can set a Minimum amount and a Maximum amount in a fiat currency, USD or EUR. Both boundaries are included in the range, and both use the same currency.

  • Both fields are optional. An empty minimum (or 0) means any positive amount; an empty maximum means no upper limit.
  • When both are set, the maximum must be greater than the minimum.

A policy without a currency (an older policy) compares its boundary with the amount of the transfer in the units of the transferred token, for example USDT. If such a policy has Token set to Any, amounts of different tokens are compared in their own units, so scope it to a specific token.

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 up to $10,000 to whitelisted addresses with 1 approval.
  • Allow transfers from $10,000 up to $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, or by giving each tier its own range.

Fiat boundaries 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. A fiat range needs the valuation to be decided even when only a minimum is set.

The comparison uses the exact value of the transfer — the amount multiplied by the quote per unit from the wallet service — without rounding to the asset’s precision. For example, $100.009 is above a maximum of $100.

If the valuation is unavailable, policy evaluation stops: the transfer is not accepted (the request fails with a temporary 503 error) and nothing is stored. This is neither a match nor a rejection by policy; try again later.

Scoping a Limit to an Asset or Wallet

Because the amount range 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 range; other assets are unaffected by that policy.

Out-of-Range Behaviour

A transfer below a policy’s minimum or above its maximum 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.

A Reject policy can have an amount range too — for example, to block transfers below a minimum. It applies to new transfers only, and an Allow policy higher in the order still takes precedence.

There is no rolling-window / velocity limit and no per-period spend aggregation. Limits are per-transfer amount ranges evaluated at submission time. A policy’s terms cannot be changed in place: to tighten or loosen a range, withdraw the policy and create a replacement (each step is audited and confirmed on a mobile signer device).